From: Asias He <asias@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: Jens Axboe <axboe@kernel.dk>,
kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Shaohua Li <shli@kernel.org>, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH RFC 1/2] block: Add blk_bio_map_sg() helper
Date: Thu, 14 Jun 2012 10:57:21 +0800 [thread overview]
Message-ID: <4FD95311.6020507@redhat.com> (raw)
In-Reply-To: <20120614023156.GB3766@dhcp-172-17-108-109.mtv.corp.google.com>
On 06/14/2012 10:31 AM, Tejun Heo wrote:
> On Wed, Jun 13, 2012 at 03:41:46PM +0800, Asias He wrote:
>> Add a helper to map a bio to a scatterlist, modelled after
>> blk_rq_map_sg.
>>
>> This helper is useful for any driver that wants to create
>> a scatterlist from its ->make_request_fn method.
>
> This may not be possible but I really wanna avoid having two copies of
> that complex logic. Any chance blk_rq_map_bio() can be implemented in
> a way that allows blk_rq_map_sg() can be built on top of it? Also,
> please include proper docbook style function comment on new public API
> functions.
OK. Will do. I guess you mean building blk_rq_map_sg() on top of
blk_bio_map_sg().
--
Asias
WARNING: multiple messages have this Message-ID (diff)
From: Asias He <asias@redhat.com>
To: Tejun Heo <tj@kernel.org>
Cc: kvm@vger.kernel.org, linux-kernel@vger.kernel.org,
virtualization@lists.linux-foundation.org,
Jens Axboe <axboe@kernel.dk>, Shaohua Li <shli@kernel.org>,
Christoph Hellwig <hch@lst.de>,
Minchan Kim <minchan.kim@gmail.com>
Subject: Re: [PATCH RFC 1/2] block: Add blk_bio_map_sg() helper
Date: Thu, 14 Jun 2012 10:57:21 +0800 [thread overview]
Message-ID: <4FD95311.6020507@redhat.com> (raw)
In-Reply-To: <20120614023156.GB3766@dhcp-172-17-108-109.mtv.corp.google.com>
On 06/14/2012 10:31 AM, Tejun Heo wrote:
> On Wed, Jun 13, 2012 at 03:41:46PM +0800, Asias He wrote:
>> Add a helper to map a bio to a scatterlist, modelled after
>> blk_rq_map_sg.
>>
>> This helper is useful for any driver that wants to create
>> a scatterlist from its ->make_request_fn method.
>
> This may not be possible but I really wanna avoid having two copies of
> that complex logic. Any chance blk_rq_map_bio() can be implemented in
> a way that allows blk_rq_map_sg() can be built on top of it? Also,
> please include proper docbook style function comment on new public API
> functions.
OK. Will do. I guess you mean building blk_rq_map_sg() on top of
blk_bio_map_sg().
--
Asias
next prev parent reply other threads:[~2012-06-14 2:57 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-13 7:41 [PATCH RFC 0/2] Improve virtio-blk performance Asias He
2012-06-13 7:41 ` [PATCH RFC 1/2] block: Add blk_bio_map_sg() helper Asias He
2012-06-13 7:41 ` Asias He
2012-06-14 2:31 ` Tejun Heo
2012-06-14 2:31 ` Tejun Heo
2012-06-14 2:57 ` Asias He [this message]
2012-06-14 2:57 ` Asias He
2012-06-14 7:29 ` Jens Axboe
2012-06-14 7:29 ` Jens Axboe
2012-06-14 8:19 ` Asias He
2012-06-14 8:19 ` Asias He
2012-06-13 7:41 ` [PATCH RFC 2/2] virtio-blk: Add bio-based IO path for virtio-blk Asias He
2012-06-13 7:41 ` Asias He
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=4FD95311.6020507@redhat.com \
--to=asias@redhat.com \
--cc=axboe@kernel.dk \
--cc=hch@lst.de \
--cc=kvm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=shli@kernel.org \
--cc=tj@kernel.org \
--cc=virtualization@lists.linux-foundation.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.