Home
last modified time | relevance | path

Searched refs:bi_idx (Results 1 – 7 of 7) sorted by relevance

/linux-6.1.9/include/linux/
Dbvec.h43 unsigned int bi_idx; /* current index into bvl_vec */ member
59 #define __bvec_iter_bvec(bvec, iter) (&(bvec)[(iter).bi_idx])
104 unsigned int idx = iter->bi_idx; in bvec_iter_advance()
120 iter->bi_idx = idx; in bvec_iter_advance()
134 if (done == bv[iter->bi_idx].bv_len) { in bvec_iter_advance_single()
136 iter->bi_idx++; in bvec_iter_advance_single()
153 .bi_idx = 0, \
/linux-6.1.9/drivers/md/
Ddm-io-rewind.c25 idx = iter->bi_idx - 1; in dm_bvec_iter_rewind()
36 iter->bi_idx = 0; in dm_bvec_iter_rewind()
40 iter->bi_idx = idx; in dm_bvec_iter_rewind()
Draid10.c2415 fbio->bi_iter.bi_idx = 0; in sync_request_write()
/linux-6.1.9/Documentation/block/
Dbiovecs.rst12 update bi_sector and bi_size, and advance bi_idx to the next biovec. If it
18 bi_size and bi_idx have been moved there; and instead of modifying bv_offset
32 instead of an integer (that corresponded to bi_idx); for a lot of code the
55 it had to walk two different bios at the same time, keeping both bi_idx and
89 norm, not all drivers would respect bi_idx and those would break. Now,
97 * Almost all usage of bi_idx is now incorrect and has been removed; instead,
98 where previously you would have used bi_idx you'd now use a bvec_iter,
101 I.e. instead of using bio_iovec_idx() (or bio->bi_iovec[bio->bi_idx]), you
/linux-6.1.9/block/
Dblk-merge.c38 idx = iter.bi_idx - 1; in bio_get_last_bvec()
40 idx = iter.bi_idx; in bio_get_last_bvec()
Dbio.c252 bio->bi_iter.bi_idx = 0; in bio_init()
/linux-6.1.9/io_uring/
Dnet.c1026 bi.bi_idx = 0; in io_sg_from_iter()
1041 from->bvec += bi.bi_idx; in io_sg_from_iter()
1042 from->nr_segs -= bi.bi_idx; in io_sg_from_iter()