From: Chris Mason <chris.mason@oracle.com>
To: jim owens <jowens@hp.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: PATCH] Do not limit RAID1 and DUP transfer length to one stripe
Date: Fri, 18 Dec 2009 09:23:24 -0500 [thread overview]
Message-ID: <20091218142324.GC3202@think> (raw)
In-Reply-To: <4B2A80AB.9080401@hp.com>
On Thu, Dec 17, 2009 at 02:04:11PM -0500, jim owens wrote:
>
> The 65k stripe length should be ignored as the stripes are
> physically contiguous on disk so transfers can span stripes.
>
> Signed-off-by: jim owens <jowens@hp.com>
> ---
> fs/btrfs/volumes.c | 6 +++---
> 1 files changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/fs/btrfs/volumes.c b/fs/btrfs/volumes.c
> index 20cbd2e..4a0c8e5 100644
> --- a/fs/btrfs/volumes.c
> +++ b/fs/btrfs/volumes.c
> @@ -2697,13 +2697,13 @@ again:
> /* stripe_offset is the offset of this block in its stripe*/
> stripe_offset = offset - stripe_offset;
>
> - if (map->type & (BTRFS_BLOCK_GROUP_RAID0 | BTRFS_BLOCK_GROUP_RAID1 |
> - BTRFS_BLOCK_GROUP_RAID10 |
> - BTRFS_BLOCK_GROUP_DUP)) {
> + if (map->type & (BTRFS_BLOCK_GROUP_RAID0 |
> + BTRFS_BLOCK_GROUP_RAID10)) {
> /* we limit the length of each bio to what fits in a stripe */
> *length = min_t(u64, em->len - offset,
> map->stripe_len - stripe_offset);
> } else {
> + /* RAID1, DUP, and simple disk stripes are all contiguous */
> *length = em->len - offset;
> }
We do need to make sure the bio doesn't try to span a chunk. The
mapping code can't handle that.
-chris
next prev parent reply other threads:[~2009-12-18 14:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-17 19:04 PATCH] Do not limit RAID1 and DUP transfer length to one stripe jim owens
2009-12-18 14:23 ` Chris Mason [this message]
2009-12-18 15:43 ` jim owens
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=20091218142324.GC3202@think \
--to=chris.mason@oracle.com \
--cc=jowens@hp.com \
--cc=linux-btrfs@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