Lines Matching refs:segments
63 3.2.1 Traversing segments and completion units in a request
67 multiple segments)
117 a per-queue level (e.g maximum request size, maximum number of segments in
148 Maximum physical segments you can handle in a request. 128
152 Maximum dma segments the hardware can handle in a request. 128
305 bio segments or uses the block layer end*request* functions for i/o
394 v. Ability to represent an i/o involving multiple physical memory segments
441 unsigned short bi_phys_segments; /* segments after physaddr coalesce*/
442 unsigned short bi_hw_segments; /* segments after DMA remapping */
461 - Code that traverses the req list can find all the segments of a bio
463 has multiple bios, each of which can have multiple segments.
562 be one of the many segments in the current bio (i.e i/o completion unit).
642 3.2.1 Traversing segments and completion units in a request
655 which don't make a distinction between segments and completion units would
668 things like collapsing physically contiguous segments (if QUEUE_FLAG_CLUSTER
673 - Avoids building segments that would exceed the number of physical
674 memory segments that the driver can handle (phys_segments) and the
681 hw data segments in a request (i.e. the maximum number of address/length
685 of physical data segments in a request (i.e. the largest sized scatter list
698 multiple segments)
701 segments and do not support i/o into high memory addresses (require bounce
705 transfer in one go unless it interprets segments), and rely on the block layer