.\" 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 "LL_RW_BLOCK" "" "06 October 2005" "" ""

.SH NAME
ll_rw_block \- level access to block devices (DEPRECATED)
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void ll_rw_block  (int \fIrw\fB, int \fInr\fB, struct buffer_head * * \fIbhs\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIrw\fB\fR
whether to READ or WRITE or maybe READA (readahead)
.TP
\fB\fInr\fB\fR
number of &struct buffer_heads in the array
.TP
\fB\fIbhs\fB\fR
array of pointers to &struct buffer_head
.SH "DESCRIPTION"
.PP
\fBll_rw_block\fR takes an array of pointers to &struct buffer_heads,
and requests an I/O operation on them, either a READ or a WRITE\&.
The third READA option is described in the documentation for
\fBgeneric_make_request\fR which \fBll_rw_block\fR calls.
.PP
This function drops any buffer that it cannot get a lock on (with the
BH_Lock state bit), any buffer that appears to be clean when doing a
write request, and any buffer that appears to be up-to-date when doing
read request.  Further it marks as clean buffers that are processed for
writing (the buffer cache won't assume that they are actually clean until
the buffer gets unlocked).
.PP
ll_rw_block sets b_end_io to simple completion handler that marks
the buffer up-to-date (if approriate), unlocks the buffer and wakes
any waiters. 
.PP
All of the buffers must be for the same device, and must also be a
multiple of the current approved size for the device.