From: Chris Mason <clm@fb.com>
To: "amadvance@gmail.com" <amadvance@gmail.com>
Cc: Josef Bacik <jbacik@fb.com>, "neilb@suse.de" <neilb@suse.de>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>,
"linux-btrfs@vger.kernel.org" <linux-btrfs@vger.kernel.org>
Subject: Re: [RFC v2 2/2] fs: btrfs: Extends btrfs/raid56 to support up to six parities
Date: Mon, 6 Jan 2014 14:12:56 +0000 [thread overview]
Message-ID: <1389017609.23310.0.camel@ret.masoncoding.com> (raw)
In-Reply-To: <1389000716-3274-3-git-send-email-amadvance@gmail.com>
On Mon, 2014-01-06 at 10:31 +0100, Andrea Mazzoleni wrote:
> This patch changes btrfs/raid56.c to use the new raid interface and
> extends its support to an arbitrary number of parities.
>
> More in details, the two faila/failb failure indexes are now replaced
> with a fail[] vector that keeps track of up to six failures, and now
> the new raid_par() and raid_rec() functions are used to handle with
> parity instead of the old xor/raid6 ones.
>
Neat. The faila/failb were always my least favorite part of the btrfs
code ;) Did you test just raid5/6 or also the higher parity counts?
-chris
next prev parent reply other threads:[~2014-01-06 14:13 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 9:31 [RFC v2 0/2] New RAID library supporting up to six parities Andrea Mazzoleni
2014-01-06 9:31 ` [RFC v2 1/2] lib: raid: " Andrea Mazzoleni
2014-01-06 9:31 ` [RFC v2 2/2] fs: btrfs: Extends btrfs/raid56 to support " Andrea Mazzoleni
2014-01-06 14:12 ` Chris Mason [this message]
2014-01-07 10:35 ` Andrea Mazzoleni
2014-01-06 11:59 ` [RFC v2 0/2] New RAID library supporting " joystick
2014-01-06 13:11 ` Alex Elsayed
2014-01-06 15:49 ` joystick
2014-01-06 16:08 ` Alex Elsayed
2014-01-06 16:08 ` Alex Elsayed
2014-01-06 16:08 ` Alex Elsayed
2014-01-07 11:06 ` Andrea Mazzoleni
2014-01-06 17:02 ` Phil Turmel
2014-01-06 17:27 ` David Sterba
2014-01-06 18:13 ` Mark Knecht
2014-01-07 11:15 ` Andrea Mazzoleni
2014-01-14 9:25 ` David Brown
2014-01-14 14:41 ` Mark Knecht
2014-01-07 11:19 ` Andrea Mazzoleni
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=1389017609.23310.0.camel@ret.masoncoding.com \
--to=clm@fb.com \
--cc=amadvance@gmail.com \
--cc=jbacik@fb.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
/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.