From: Chris Mason <chris.mason@oracle.com>
To: David Woodhouse <dwmw2@infradead.org>
Cc: jim owens <jowens@hp.com>, linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: [PATCH] don't OOPs when we are not raid56
Date: Tue, 8 Sep 2009 09:48:29 -0400 [thread overview]
Message-ID: <20090908134829.GA32545@think> (raw)
In-Reply-To: <1252401329.4483.579.camel@macbook.infradead.org>
On Tue, Sep 08, 2009 at 10:15:29AM +0100, David Woodhouse wrote:
> On Wed, 2009-09-02 at 12:32 -0400, jim owens wrote:
> > @@ -2895,7 +2895,7 @@ again:
> > multi->num_stripes = num_stripes;
> > multi->max_errors = max_errors;
> > }
> > - if (raid_map_ret) {
> > + if (raid_map) {
> > sort_parity_stripes(multi, raid_map);
> > *raid_map_ret = raid_map;
> > }
>
> Applied (manually, because I think your mail was whitespace-damaged).
> Thanks.
>
> Chris, where do we stand with getting this merged? You were going to
> sort out the upper layers to handle the minimum write size, weren't you?
Yes, I'm working on sorting that out. Jens distracted me with some
depressing benchmarks, but now that those are fixed I can move on ;)
>
> I'm also going to do RAID50/60 support, and with hpa's help I'll extend
> it to do RAID7/70 too -- but you're not waiting for that, are you?
Great news, no I'm not waiting for that.
-chris
next prev parent reply other threads:[~2009-09-08 13:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-06 10:17 RAID[56] status David Woodhouse
2009-08-07 9:43 ` Roy Sigurd Karlsbakk
2009-08-07 15:22 ` David Woodhouse
2009-09-02 16:32 ` [PATCH] don't OOPs when we are not raid56 jim owens
2009-09-08 9:15 ` David Woodhouse
2009-09-08 13:48 ` Chris Mason [this message]
2009-11-10 19:51 ` RAID[56] status Dan Williams
2009-11-10 20:05 ` Tomasz Torcz
2009-11-10 20:11 ` Chris Mason
2009-11-10 21:06 ` tsuraan
2009-11-10 21:20 ` Gregory Maxwell
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=20090908134829.GA32545@think \
--to=chris.mason@oracle.com \
--cc=dwmw2@infradead.org \
--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