Lines Matching refs:requests

172 by default copyin/out i/o requests on high-memory buffers to low-memory buffers
221 routine on its own to bounce highmem i/o to low memory for specific requests
267   requests in the queue. For example it allows reads for bringing in an
269   requests which haven't aged too much on the queue. Potentially this priority
272   requests. Some bits in the bi_rw flags field in the bio structure are
290 for specially crafted requests which such ioctl or diagnostics
292 can instead be used to directly insert such requests in the queue or preferably
318 handling direct requests easier for such drivers; Also for drivers that
346 It can help to pre-build device commands for requests in advance.
351 (The prepare function would not be called for requests that have REQ_DONTPREP
372 when it came to large i/o requests and readv/writev style operations, as it
373 forced such requests to be broken up into small chunks before being passed
637 same bio_vec_list). This would typically be used for splitting i/o requests
710 direct access requests which only specify rq->buffer without a valid rq->bio)
759 all the outstanding requests. There's a third helper to do that:
763 	Clear the internal block tag queue and re-add all the pending requests
808 but in the event of any barrier requests in the tag queue we need to ensure
809 that requests are restarted in the order they were queue. This may happen
859 Direct access requests that do not contain bios would be submitted differently
892 requests and all other subtleties.
895 requests.  They can also choose to delay certain requests to improve
910 elevator_merge_fn		called to query requests for merge with a bio
912 elevator_merge_req_fn		called when two requests get merged. the one
928 				that two *requests* can still be merged at later
933 elevator_dispatch_fn*		fills the dispatch queue with ready requests.
934 				I/O schedulers are free to postpone requests by
937 				are not allowed to manipulate the requests -
970 All requests seen by I/O schedulers strictly follow one of the following three
983 The generic i/o scheduler algorithm attempts to sort/merge/batch requests for
1011 iii. Plugging the queue to batch requests in anticipation of opportunities for
1015 that it collects up enough requests in the queue to be able to take
1019 till it fills up with a few more requests, before starting to service
1020 the requests. This provides an opportunity to merge/sort the requests before
1092 Old-style drivers that just use CURRENT and ignores clustered requests,
1094 clustered requests, multi-page bios, etc for the driver.
1102 Drivers should use elv_next_request to pick up requests and are no longer