Lines Matching refs:biovec

2 Immutable biovecs and biovec iterators
8 Instead, we have a new struct bvec_iter which represents a range of a biovec -
9 the iterator will be modified as the bio is completed, not the biovec.
12 update bi_sector and bi_size, and advance bi_idx to the next biovec. If it
13 ended up partway through a biovec, it would increment bv_offset and decrement
14 bv_len by the number of bytes completed in that biovec.
41    a pointer to a biovec, not a bio; this is used by the bio integrity code.
56    and offset into the current biovec for each.
63  * Before, any code that might need to use the biovec after the bio had been
69    arbitrary range of an existing biovec, both starting and ending midway
77    size bios - because the new bio can share the old bio's biovec.
79    Care must be taken to ensure the biovec isn't freed while the split bio is
103    literal struct bio_vec - constructed on the fly from the raw biovec but
110    biovec, in order to calculate bi_vcnt for the new bio we'd have to iterate