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

.SH NAME
blk_queue_make_request \- define an alternate make_request function for a device
.SH SYNOPSIS
"SYNOPSIS"
.sp
\fB
.sp
void blk_queue_make_request  (request_queue_t * \fIq\fB, make_request_fn * \fImfn\fB);
\fR
.SH "ARGUMENTS"
.TP
\fB\fIq\fB\fR
the request queue for the device to be affected
.TP
\fB\fImfn\fB\fR
the alternate make_request function
.SH "DESCRIPTION"
.PP
The normal way for &struct bios to be passed to a device
driver is for them to be collected into requests on a request
queue, and then to allow the device driver to select requests
off that queue when it is ready.  This works well for many block
devices. However some block devices (typically virtual devices
such as md or lvm) do not benefit from the processing on the
request queue, and are served best by having the requests passed
directly to them.  This can be achieved by providing a function
to \fBblk_queue_make_request\fR\&.
.SH "CAVEAT"
.PP
The driver that does this *must* be able to deal appropriately
with buffers in ``highmemory''\&. This can be accomplished by either calling
\fB__bio_kmap_atomic\fR to get a temporary kernel mapping, or by calling
\fBblk_queue_bounce\fR to create a buffer in normal memory.