On Mon, Oct 31, 2016 at 11:39 PM, Christoph Hellwig <hch@xxxxxxxxxxxxx> wrote: > On Sat, Oct 29, 2016 at 04:08:27PM +0800, Ming Lei wrote: >> Some drivers(such as dm) should be capable of dealing with multipage >> bvec, but the incoming bio may be too big, such as, a new singlepage bvec >> bio can't be cloned from the bio, or can't be allocated to singlepage >> bvec with same size. >> >> At least crypt dm, log writes and bcache have this kind of issue. > > We already have the segment_size limitation for request based drivers. > I'd rather extent it to bio drivers if really needed. Yeah, just found dm actually don't need the flag, and it has its own way for limitting bio size. For bcache, there is only place which need the flag, so we can use max sectors limit to address it or use multiple bio to read & check ony by one. > > But then again we should look into not having this limitation. E.g. > for bcache I'd be really surprised if it's that limited, given that > Kent came up with this whole multipage bvec scheme. As far as I find, the only one which need the flag is bch_data_verify(). Thanks, Ming Lei -- To unsubscribe from this list: send the line "unsubscribe linux-block" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
