Lines Matching refs:scheduler

49 	- I/O scheduler modularization
70 4. The I/O scheduler
116 Various parameters that the generic i/o scheduler logic uses are set at
224 iii. The i/o scheduler algorithm itself can be replaced/set as appropriate
226 As in 2.4, it is possible to plugin a brand new i/o scheduler for a particular
229 of the i/o scheduler. There are more pluggable callbacks, e.g for init,
233 the i/o scheduler from block drivers.
235 I/O scheduler wrappers are to be used instead of accessing the queue directly.
236 See section 4. The I/O scheduler for details.
374 on to the generic block layer, only to be merged by the i/o scheduler
557 available. Some bits are used by the block layer or i/o scheduler.
885 4. The I/O scheduler
886 I/O scheduler, a.k.a. elevator, is implemented in two layers.  Generic dispatch
888 to refer to both parts and I/O scheduler to specific I/O schedulers.
901 A block layer call to the i/o scheduler follows the convention elv_xxx(). This
907 4.1. I/O scheduler API
914 				never seen by I/O scheduler again. IOW, after
917 elevator_merged_fn		called when a request in the scheduler has been
919 				scheduler for example, to reposition the request
924 				request safely. The io scheduler may still
929 				time. Currently the io scheduler has no way to
940 elevator_add_req_fn*		called to add a new request into the scheduler
949 elevator_may_queue_fn		returns true if the scheduler wants to allow the
982 4.3 I/O scheduler implementation
983 The generic i/o scheduler algorithm attempts to sort/merge/batch requests for
1043 for an example of usage in an i/o scheduler.
1084 so the i/o scheduler also gets to operate on whole disk sector numbers. This
1167 8.13  Priority based i/o scheduler - prepatches (Arjan van de Ven)