From: Hannes Reinecke <hare@suse.de>
To: Kiyoshi Ueda <k-ueda@ct.jp.nec.com>
Cc: jens.axboe@oracle.com, linux-kernel@vger.kernel.org,
linux-scsi@vger.kernel.org, dm-devel@redhat.com,
j-nomura@ce.jp.nec.com, michaelc@cs.wisc.edu
Subject: Re: [RFC PATCH 1/3] block: add rq->complete_io hook for request stacking
Date: Tue, 04 Mar 2008 09:10:06 +0100 [thread overview]
Message-ID: <47CD03DE.3010703@suse.de> (raw)
In-Reply-To: <20080303.140427.39152329.k-ueda@ct.jp.nec.com>
Hi Kiyoshi,
Kiyoshi Ueda wrote:
> Hi Hannes,
>
> On Mon, 03 Mar 2008 17:24:50 +0100, Hannes Reinecke wrote:
>> Hi Kiyoshi,
>>
>> Kiyoshi Ueda wrote:
>>> This patch adds ->complete_io() hook for request stacking.
>>> Request stacking drivers (such as request-based dm) can set
>>> a callback for completion.
>>> (The hook is not called in blk_end_io(), since request-based dm uses
>>> it for clone completion in the following appendix patches.)
>>>
>> [ .. ]
>> I would rather have rq->complete_io() to be pointing to blk_end_io in the
>> default case, this way rq->complete_io() would always be valid and we
>> would be saving us the if() clause.
>
> Thank you for the comment.
>
> I'm thinking about an idea come from Mike and Jens after the session
> at LSF'08:
> o stacking driver clones both bio and request and uses
> bio->bi_end_io and rq->end_io
> o stacking driver uses blk_complete_request() in rq->end_io
> so that stacking driver can work without queue lock
> With this idea, we don't need to add the new hook to request,
> and we can use request stacking on drivers using __blk_end_request().
>
Huh? I can't really imagine how this should work. If you start using
bio->bi_end_io() for stacking usage you'll end up with doing weird thing
with the bios ... Can you elaborate a bit more here?
> Currently, I'm trying to convert request-based dm to use the idea above.
> I'll post the new version as a RFC in the near future.
>
Oh, cool. Looking forward to it.
Cheers,
Hannes
--
Dr. Hannes Reinecke zSeries & Storage
hare@suse.de +49 911 74053 688
SUSE LINUX Products GmbH, Maxfeldstr. 5, 90409 Nürnberg
GF: Markus Rex, HRB 16746 (AG Nürnberg)
next prev parent reply other threads:[~2008-03-04 8:10 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-02-15 22:27 Kiyoshi Ueda
2008-03-03 16:24 ` Hannes Reinecke
2008-03-03 17:33 ` Grant Grundler
2008-03-03 17:49 ` Jens Axboe
2008-03-03 19:04 ` Kiyoshi Ueda
2008-03-04 8:10 ` Hannes Reinecke [this message]
2008-03-04 20:02 ` Jun'ichi Nomura
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=47CD03DE.3010703@suse.de \
--to=hare@suse.de \
--cc=dm-devel@redhat.com \
--cc=j-nomura@ce.jp.nec.com \
--cc=jens.axboe@oracle.com \
--cc=k-ueda@ct.jp.nec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=michaelc@cs.wisc.edu \
/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