Re: [dm-devel] [PATCH 1/2] blkdev: fix merge_bvec_fn return valuechecks
From: Jens Axboe
Date: Fri Mar 05 2010 - 02:31:10 EST
On Thu, Mar 04 2010, Mikulas Patocka wrote:
> > > I think it should be redesigned in this way:
> > > * the bio should be allowed to have arbitrary size, up to BIO_MAX_PAGES
> > > * the code for splitting bios should be just at one place --- in the
> > > generic block layer and it should work with all drivers. I.e.
> > > q->make_request_fn will return that the request is too big for the given
> > > driver and the generic code will allocate few another bios from
> > > per-request_queue mempool and split the bio.
> > > * then, we would fix the raid1 bug and we would also simplify md and dm
> > > --- remove the splitting code.
> > The design certainly isn't perfect, but neither is the one that you
> > suggest. For instance, what would the point of building bigger bios just
> > to split them _everytime_ be? That's not good design, and it's certainly
> > not helping performance much.
> The point for building a big bio and splitting it is code size reduction.
> You must realize that you need to split the request anyway. If the caller
> needs to read/write M sectors and the device can process at most N
> sectors, where N<M, then the i/o must be split. You can't get rid of that
If we consider the basic (and mosted used) file system IO path, then
those 'M' sectors will usually be submitted in units that are smaller
than 'N' anyway. It would be silly to allocate a bio for 'N' sectors
(those get big), only to split it up again shortly.
The point is not to build it too big to begin with, and keep the
splitting as the slow path. That's how it was originally designed, and
it'll surely stay that way. Doing the split handling in generic code is
a good idea, it definitely should be. But I'm never going to make
splitting a normal part of IO operations just because we allow
arbitrarily large bios, sorry but that's insane.
> Now, the question is, where this splitting happens. Currently, the
> splitting happens in the issuers of the bio (for example dm-io, which is a
> big chunk of code written just to work around the uncertain bio size
> limits) as well as in the consumers of the bio (md, dm and request-based
> drivers, if their maximum transfer size < PAGE_SIZE).
> What I'm proposing is to put that bio splitting just in one place and
> remove it from both the issuers and the consumers of the bio.
Agree on that, we can make that generic (and should).
> There is just one case, where it is not desirable to create larger
> requests than the physical transfer size because of performance --- that
> is page cache readahead. That could use the current approach of querying
> the queue for limits and not stuffing more data than the device can
> In all the other (non-readahead) cases, the caller is waiting for all the
> data anyway, there is no performance problem with creating a larger
> requests and splitting them.
But this I still think is crazy, sorry.
> > Alasdair had an idea for doing a map/unmap like interface instead, which
> > I think is a lot better. I don't think he ever coded it up, though.
> > Perhaps talk to him, if you want to improve our situation in this area.
> It would increase code size, not reduce it.
What kind of answer is that?
> BTW. see fs/bio.c:bio_split --- it uses a shared mempool. It can deadlock
> if the devices depend on each other. You need to use per-queue mempool.
Only if you need to split the same original bio twice on the same IO
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/