.\" This manpage has been automatically generated by docbook2man .\" from a DocBook document. This tool can be found at: .\" .\" Please send any bug reports, improvements, comments, patches, .\" etc. to Steve Cheng . .TH "NFS_DIRECT_WRITE" "9" "09 October 2005" "" "" .SH NAME nfs_direct_write \- For each iov segment, map the user's buffer .SH SYNOPSIS "SYNOPSIS" .sp \fB .sp ssize_t nfs_direct_write (struct inode * \fIinode\fB, struct nfs_open_context * \fIctx\fB, const struct iovec * \fIiov\fB, loff_t \fIfile_offset\fB, unsigned long \fInr_segs\fB); \fR .SH "ARGUMENTS" .TP \fB\fIinode\fB\fR target inode .TP \fB\fIctx\fB\fR target file open context .TP \fB\fIiov\fB\fR array of vectors that define I/O buffer .TP \fB\fIfile_offset\fB\fR -- undescribed -- .TP \fB\fInr_segs\fB\fR -- undescribed -- .SH "DESCRIPTION" .PP then generate write and commit RPCs. .SH "FILE_OFFSET" .PP offset in file to begin the operation .SH "NR_SEGS" .PP size of iovec array .PP Upon return, generic_file_direct_IO invalidates any cached pages that non-direct readers might access, so they will pick up these writes immediately.