From: Andrea Mazzoleni <amadvance@gmail.com>
To: Chris Mason <clm@fb.com>
Cc: "amadvance@gmail.com" <amadvance@gmail.com>,
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: Tue, 7 Jan 2014 11:35:43 +0100 [thread overview]
Message-ID: <20140107103543.GB16044@gmail.com> (raw)
In-Reply-To: <1389017609.23310.0.camel@ret.masoncoding.com>
Hi Chris,
On 01/06, Chris Mason wrote:
> 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?
At this stage no real testing was made with btrfs.
The intention of this btrfs patch is mainly to get feedback on the new raid
inteface, and see if it matches the needs of btrfs, and if it results in
cleaner code than before.
And besides the removal of the faila/failb variables, something other that
likely you can appreciate is the removal of all the P/Q logic from btrfs,
that it's now replaced with a single raid_rec() call.
After the raid interface stabilizes, this patch can be used as starting
point for a real btrfs patch. But at now it's just to show
some example code of what kind of modification btrfs will need.
Ciao,
Andrea
next prev parent reply other threads:[~2014-01-07 10:35 UTC|newest]
Thread overview: 11+ 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 2/2] fs: btrfs: Extends btrfs/raid56 to support " Andrea Mazzoleni
2014-01-06 14:12 ` Chris Mason
2014-01-07 10:35 ` Andrea Mazzoleni [this message]
2014-01-06 11:59 ` [RFC v2 0/2] New RAID library supporting " joystick
[not found] ` <laea0q$d0g$2@ger.gmane.org>
2014-01-06 15:49 ` joystick
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-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=20140107103543.GB16044@gmail.com \
--to=amadvance@gmail.com \
--cc=clm@fb.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).