All of lore.kernel.org
 help / color / mirror / Atom feed
From: jim owens <jowens@hp.com>
To: Chris Mason <chris.mason@oracle.com>, jim owens <jowens@hp.com>,
	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 10:43:16 -0500	[thread overview]
Message-ID: <4B2BA314.9040508@hp.com> (raw)
In-Reply-To: <20091218142324.GC3202@think>

Chris Mason wrote:
> 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.
>>
>> +		/* 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.

I don't understand what code can't handle it, the em is limited
to a chunk so em->start to em->start + em->len will be reachable
as a single physical disk region for raid1 and dup... right?

      reply	other threads:[~2009-12-18 15:43 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
2009-12-18 15:43   ` jim owens [this message]

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=4B2BA314.9040508@hp.com \
    --to=jowens@hp.com \
    --cc=chris.mason@oracle.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 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.