From: Jens Axboe <axboe@suse.de>
To: Andrew Morton <akpm@osdl.org>,
linux-kernel@vger.kernel.org, dm-devel@redhat.com
Subject: Re: dm: bio split bvec fix
Date: Wed, 22 Mar 2006 12:32:35 +0100 [thread overview]
Message-ID: <20060322113235.GC4285@suse.de> (raw)
In-Reply-To: <20060320192155.GU4724@agk.surrey.redhat.com>
On Mon, Mar 20 2006, Alasdair G Kergon wrote:
> The code that handles bios that span table target boundaries by breaking
> them up into smaller bios will not split an individual struct bio_vec
> into more than two pieces. Sometimes more than that are required.
>
> This patch adds a loop to break the second piece up into as many
> pieces as are necessary.
Why isn't this just handled in the merge callback? Can a single page bio
span > 2 targets?
--
Jens Axboe
next prev parent reply other threads:[~2006-03-22 11:32 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-20 19:21 dm: bio split bvec fix Alasdair G Kergon
2006-03-20 22:05 ` Andrew Morton
2006-03-22 11:32 ` Jens Axboe [this message]
2006-03-22 12:19 ` [dm-devel] " Alasdair G Kergon
2006-03-22 12:56 ` Jens Axboe
2006-03-22 13:08 ` Jens Axboe
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=20060322113235.GC4285@suse.de \
--to=axboe@suse.de \
--cc=akpm@osdl.org \
--cc=dm-devel@redhat.com \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox