.\" This manpage has been automatically generated by docbook2man 
.\" from a DocBook document.  This tool can be found at:
.\" <http://shell.ipoline.com/~elmert/comp/docbook2X/> 
.\" Please send any bug reports, improvements, comments, patches, 
.\" etc. to Steve Cheng <steve@ggi-project.org>.
.TH "NFS_DIRECT_READ" "" "06 October 2005" "" ""

.SH NAME
nfs_direct_read \- For each iov segment, map the user's buffer
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
int nfs_direct_read  (struct inode * \fIinode\fB, struct file * \fIfile\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\fIfile\fB\fR
target file (may be NULL)
.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 read RPCs.
.SH "FILE_OFFSET"
.PP
offset in file to begin the operation
.SH "NR_SEGS"
.PP
size of iovec array
.PP
generic_file_direct_IO has already pushed out any non-direct
writes so that this read will see them when we read from the
server.