Lines Matching refs:O

9 September 2003: Updated I/O Scheduler portions
48 	- Highmem I/O support
49 	- I/O scheduler modularization
65     3.2.3 I/O completion
69   3.3 I/O submission
70 4. The I/O scheduler
130 		Enable I/O to highmem pages, dma_address being the
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.
429  * main unit of I/O for the block layer and lower layers (ie drivers)
485 which in turn means that only raw I/O uses it (direct i/o may not work
653 I/O completion callbacks are per-bio rather than per-segment, so drivers
688 3.2.3 I/O completion
812 3.3 I/O Submission
885 4. The I/O scheduler
886 I/O scheduler, a.k.a. elevator, is implemented in two layers.  Generic dispatch
887 queue and specific I/O schedulers.  Unless stated otherwise, elevator is used
888 to refer to both parts and I/O scheduler to specific I/O schedulers.
894 Specific I/O schedulers are responsible for ordering normal filesystem
897 multiple I/O schedulers.  They can be built as modules but at least one should
907 4.1. I/O scheduler API
914 				never seen by I/O scheduler again. IOW, after
934 				I/O schedulers are free to postpone requests by
936 				is non-zero.  Once dispatched, I/O schedulers
959 				I/O schedulers can use this callback to
969 4.2 Request flows seen by I/O schedulers
970 All requests seen by I/O schedulers strictly follow one of the following three
982 4.3 I/O scheduler implementation
1005 multiple I/O streams are being performed at once on one disk.
1008 are far less common than "back merges" due to the nature of most I/O patterns.
1039 4.4 I/O contexts
1040 I/O contexts provide a dynamically allocated per process data area. They may
1041 be used in I/O schedulers, and in the block layer (could be used for IO statis,
1140 transfer a virtual mapping is needed. If the driver supports highmem I/O,
1174 9.1 The Splice I/O Model - Larry McVoy (and subsequent discussions on lkml,