Lines Matching refs:layer

14 These are some notes describing some aspects of the 2.5 block layer in the
26 Many aspects of the generic block layer redesign were driven by and evolved
56    (instead of using buffer heads at the i/o layer)
75   6.1 Partition re-mapping handled by the generic block layer
86 block layer are addressed.
90 The block layer design supports adaptable abstractions to handle common
107 used at the generic block layer to take the right decisions on
114 i. Per-queue limits/values exported to the generic layer by the driver
171 The generic bounce buffer logic, present in 2.4, where the block layer would
254 What kind of support exists at the generic block layer for this ?
286 it possible to perform bottom up validation of the i/o path, layer by
287 layer, starting from the media.
305 bio segments or uses the block layer end*request* functions for i/o
311 request->current_nr_sectors fields itself rather than using the block layer
348 block layer would invoke to pre-build device commands for a given request,
370 layer, and the low level request structure was associated with a chain of
374 on to the generic block layer, only to be merged by the i/o scheduler
405 The solution was to define a new structure (bio)  for the block layer,
408 is uniformly used for all i/o at the block layer ; it forms a part of the
429  * main unit of I/O for the block layer and lower layers (ie drivers)
487 become possible. The pagebuf abstraction layer from SGI also uses multi-page
495 drivers. The block layer make_request function builds up a request structure,
497 use of block layer helper routine elv_next_request to pull the next request
557 available. Some bits are used by the block layer or i/o scheduler.
569 driver should not modify these values. The block layer sets up the
580 a driver needs to be careful about interoperation with the block layer helper
593 subsystem makes use of the block layer to writeout dirty pages in order to be
690 The existing generic block layer helper routines end_request,
705 transfer in one go unless it interprets segments), and rely on the block layer
752 completion of the request to the block layer. This means ending tag
878   from higher level code should not be modified by the block layer in the course
879   of its request processing, since that would make it hard for the higher layer
890 Block layer implements generic dispatch queue in block/*.c.
901 A block layer call to the i/o scheduler follows the convention elv_xxx(). This
922 elevator_allow_merge_fn		called whenever the block layer determines
945 				block layer to find merge possibilities.
999 This arrangement is not a generic block layer characteristic however, so
1041 be used in I/O schedulers, and in the block layer (could be used for IO statis,
1055 necessary (e.g the scsi layer sets the queue lock pointers to the
1058 still imposed by the block layer, grabbing the lock before
1076 6.1 Partition re-mapping handled by the generic block layer
1079 Now the generic block layer performs partition-remapping early and thus
1093 may not need much change.  The generic layer will automatically handle
1123 correct absolute location anymore, this is done by the block layer, so