Lines Matching refs:direct

182 modified to accomplish a direct page -> bus translation, without requiring
279 There are situations where high-level code needs to have direct access to
284 capabilities for certain kinds of fitness tests. Having direct interfaces at
318 handling direct requests easier for such drivers; Also for drivers that
343 in such cases (REQ_PC: direct packet command passed to driver, REQ_BLOCK_PC:
384     avoid cache related fields which are irrelevant in the direct/page i/o path,
409 bh structure for buffered i/o, and in the case of raw/direct i/o kiobufs are
485 which in turn means that only raw I/O uses it (direct i/o may not work
710 direct access requests which only specify rq->buffer without a valid rq->bio)
821 (b) Kiobuf i/o (for raw/direct i/o):
828 blocks array as well, but it's currently in there to kludge around direct i/o.]
835  So right now it wouldn't work for direct i/o on non-contiguous blocks.
839  Badari Pulavarty has a patch to implement direct i/o correctly using
1149 - direct kiobuf based i/o to devices (no intermediate bh's)