From: Alasdair G Kergon <agk@redhat.com>
To: Neil Brown <neilb@suse.de>
Cc: device-mapper development <dm-devel@redhat.com>,
Dmitry Monakhov <dmonakhov@openvz.org>,
Mikulas Patocka <mpatocka@redhat.com>,
linux-kernel@vger.kernel.org, Mike Snitzer <snitzer@redhat.com>,
jens.axboe@oracle.com
Subject: Re: [dm-devel] [PATCH 1/2] blkdev: fix merge_bvec_fn return value checks
Date: Sat, 6 Mar 2010 02:20:15 +0000 [thread overview]
Message-ID: <20100306022015.GU27852@agk-dp.fab.redhat.com> (raw)
In-Reply-To: <20100306105237.0a8621ed@notabene.brown>
On Sat, Mar 06, 2010 at 10:52:37AM +1100, Neil Brown wrote:
> But my first suggestion, that splitting could be made easier, still stands.
In full agreement we should try to make it easier.
> And do you honour merge_bvec_fn's of underlying devices? A quick grep
> suggests you do only for dm-linear and dm-crypt.
We implemented it to address some specific performance problems reported by
people using those targets. So far there hasn't been any pressing need to
implement it for other targets.
> This suggests to me that it
> is actually a hard interface to support completely in a stacked device, so we
> might be better off without it.
All this code is hard - but very useful. The direction I want to explore when
I finally get some time to work on this is one which will probably make more
use of, and extend, merge_bvec.
> that it makes sense to only require that the lowest level does the
> splitting, as that is where the specifics on what might be required exists.
We have a hybrid model at the moment - some stuff dealt with top-down, other
stuff bottom-up. This thread describes just one of several problems related to
this. In the next incarnation of device-mapper I hope we'll find a way to
eliminate all of them together. Maybe I'll finally get time later this year to
start working on these ideas properly.
Alasdair
next prev parent reply other threads:[~2010-03-06 2:20 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-27 17:35 Dmitry Monakhov
2010-02-27 17:35 ` [PATCH 2/2] blktrace: perform cleanup after setup error Dmitry Monakhov
2010-02-28 18:46 ` Jens Axboe
2010-02-28 18:46 ` [PATCH 1/2] blkdev: fix merge_bvec_fn return value checks Jens Axboe
2010-03-03 3:49 ` Dmitry Monakhov
2010-03-03 7:30 ` Jens Axboe
2010-03-03 8:39 ` Dmitry Monakhov
2010-03-03 12:21 ` Jens Axboe
2010-03-03 18:20 ` Mike Snitzer
2010-03-03 18:45 ` Dmitry Monakhov
2010-03-03 19:16 ` Mike Snitzer
2010-03-03 19:42 ` Dmitry Monakhov
2010-03-03 20:07 ` Jens Axboe
2010-03-04 11:47 ` [dm-devel] " Mikulas Patocka
2010-03-04 12:19 ` Jens Axboe
2010-03-04 21:55 ` Mikulas Patocka
2010-03-05 7:30 ` Jens Axboe
2010-03-05 21:56 ` Neil Brown
2010-03-05 22:27 ` Alasdair G Kergon
2010-03-05 23:52 ` Neil Brown
2010-03-06 2:20 ` Alasdair G Kergon [this message]
2010-03-08 9:01 ` Mikulas Patocka
2010-03-04 17:59 ` Lars Ellenberg
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100306022015.GU27852@agk-dp.fab.redhat.com \
--to=agk@redhat.com \
--cc=dm-devel@redhat.com \
--cc=dmonakhov@openvz.org \
--cc=jens.axboe@oracle.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mpatocka@redhat.com \
--cc=neilb@suse.de \
--cc=snitzer@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome