From: David Woodhouse <dwmw2@infradead.org>
To: Dan Williams <dan.j.williams@intel.com>
Cc: "H. Peter Anvin" <hpa@zytor.com>,
Ric Wheeler <rwheeler@redhat.com>,
chris.mason@oracle.com, linux-btrfs@vger.kernel.org,
neilb@suse.de, linux-raid@vger.kernel.org
Subject: Re: [PATCH 1/4] md: Factor out RAID6 algorithms into lib/
Date: Sun, 19 Jul 2009 19:04:07 +0100 [thread overview]
Message-ID: <1248026647.5646.36.camel@macbook.infradead.org> (raw)
In-Reply-To: <e9c3a7c20907181304w18738febn4e5ab380d10bef4b@mail.gmail.com>
On Sat, 2009-07-18 at 13:04 -0700, Dan Williams wrote:
> On Sat, Jul 18, 2009 at 11:42 AM, David Woodhouse<dwmw2@infradead.org> wrote:
> > On Sat, 18 Jul 2009, Dan Williams wrote:
> >> I was under the impression that btrfs wanted to leverage md's stripe
> >> handling logic as well, seems that is not the case?
> >
> > No. We do a bunch of the stuff you mention above, but entirely within the
> > file system so we don't have to invent a bunch of layering violations just
> > to work around a broken design.
>
> Sure, a layering violation for an existing filesystem. For btrfs, at
> LSF'09, we briefly talked about breaking out more than just the
> erasure codes from software-raid into a "libraid". At some point in
> the i/o path a btrfs stripe operation becomes indistinguishable from a
> raid5,6 operation so at first glance there appears to be room to share
> common infrastructure like portions of handle_stripe for example.
At this point we've actually implemented the fundamental parts of
RAID[56] support in btrfs, and it's looking like all we really want is
the arithmetic routines.
Perhaps that's because I'm insufficiently familiar with the
handle_stripe() function to which you refer. Would you like to take to
take a look at http://git.infradead.org/users/dwmw2/btrfs-raid56.git and
attempt to convince me that I should be reusing more?
Criticism in 'diff -up' form is always welcome... :)
--
David Woodhouse Open Source Technology Centre
David.Woodhouse@intel.com Intel Corporation
next prev parent reply other threads:[~2009-07-19 18:04 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-13 14:11 [PATCH 1/4] md: Factor out RAID6 algorithms into lib/ David Woodhouse
2009-07-15 19:23 ` Dan Williams
2009-07-15 20:16 ` Chris Mason
2009-07-15 22:11 ` Dan Williams
2009-07-16 17:38 ` H. Peter Anvin
2009-07-17 14:22 ` Ric Wheeler
2009-07-17 15:20 ` H. Peter Anvin
2009-07-17 15:35 ` Ric Wheeler
2009-07-17 15:40 ` H. Peter Anvin
2009-07-17 15:47 ` Ric Wheeler
2009-07-17 15:49 ` H. Peter Anvin
2009-07-17 15:58 ` Ric Wheeler
2009-07-17 18:59 ` Alex Elsayed
2009-07-17 19:02 ` Alex Elsayed
2009-07-29 18:16 ` H. Peter Anvin
2009-07-17 19:12 ` Gregory Maxwell
2009-07-18 11:53 ` David Woodhouse
2009-07-18 12:45 ` H. Peter Anvin
2009-07-18 18:50 ` Alex Elsayed
2009-07-18 18:52 ` Alex Elsayed
2009-07-29 18:20 ` H. Peter Anvin
2009-07-18 12:49 ` Ric Wheeler
2009-07-18 16:26 ` Dan Williams
2009-07-18 18:42 ` David Woodhouse
2009-07-18 20:04 ` Dan Williams
2009-07-19 18:04 ` David Woodhouse [this message]
2009-07-20 5:21 ` H. Peter Anvin
2009-07-17 15:51 ` H. Peter Anvin
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=1248026647.5646.36.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=chris.mason@oracle.com \
--cc=dan.j.williams@intel.com \
--cc=hpa@zytor.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=neilb@suse.de \
--cc=rwheeler@redhat.com \
/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).