Lines Matching refs:bios

60 3. Using bios
66     3.2.4 Implications for drivers that do not interpret bios (don't handle
319 expect bios, a helper function could be provided for setting up a bio
459 - A linked list of bios is used as before for unrelated merges (*) - this
463   has multiple bios, each of which can have multiple segments.
470 (*) unrelated merges -- a request ends up containing two or more bios that
475 At a lower level, drivers build a scatter gather list from the merged bios.
484 Note: Right now the only user of bios with more than one page is ll_rw_kio,
488 bios, but that is currently not included in the stock development kernels.
560 except that since we have multi-segment bios, current_nr_sectors refers
583 3. Using bios
588 freeing of bios (bio_alloc, bio_get, bio_put).
644 The macro rq_for_each_segment() should be used for traversing the bios
656 need to be reorganized to support multi-segment bios.
697 3.2.4 Implications for drivers that do not interpret bios (don't handle
700 Drivers that do not interpret bios e.g those which do not handle multiple
823 maps the array to one or more multi-page bios, issuing submit_bio() to
827 preallocation of bios is done for kiobufs. [The intent is to remove the
848  large bios for submission completely bypassing the usage of buffer
851  Christoph Hellwig had some code that uses bios for page-io (rather than
859 Direct access requests that do not contain bios would be submitted differently
877   bios are handled today. The values of the tuples in such a vector passed in
1036   multi-page bios being queued in one shot, we may not need to wait to merge
1086 to invoke its own partition sector offset calculations since all bios
1094 clustered requests, multi-page bios, etc for the driver.