Re: [PATCH V10 09/19] block: introduce bio_bvecs()

[Sagi Grimberg]

> > Yeah, that is the most common example, given merge is enabled
> > in most of cases. If the driver or device doesn't care merge,
> > you can disable it and always get single bio request, then the
> > bio's bvec table can be reused for send().
>
> Does bvec_iter span bvecs with your patches? I didn't see that change?

Wait, I see that the bvec is still a single array per bio. When you said
a table I thought you meant a 2-dimentional array...

Unless I'm not mistaken, I think that the change is pretty simple then.
However, nvme-tcp still needs to be bio aware unless we have some
abstraction in place.. Which will mean that nvme-tcp will need to
open-code bio_bvecs.