From: Boaz Harrosh <bharrosh@panasas.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
open-osd <osd-dev@open-osd.org>
Subject: Re: [GIT PULL] exofs changes for 2.6.34
Date: Sun, 07 Mar 2010 10:32:31 +0200 [thread overview]
Message-ID: <4B93649F.10303@panasas.com> (raw)
In-Reply-To: <20100304140004.GA10838@infradead.org>
On 03/04/2010 04:00 PM, Christoph Hellwig wrote:
> On Thu, Mar 04, 2010 at 02:10:57PM +0200, Boaz Harrosh wrote:
>> Next changes will be support for raid5 and raid6
>
> Err, you're not pushing another bloody copy of raid algorithms in, are
> you?
>
No of course not. You should know me by now. I intend to fully reuse both
linux/raid/pq.h and linux/async_tx.h.
[What? lose all these CPU/HW optimizations people have done ?-)]
I'm struggling with re-factoring some of drivers/md/raid* as I'm using
bios just as they do, and bio_lists are fine, but currently the code
is very md/dm structure specific, there is no abstract bio_list API
but I hope I can extract one with minimum risk. I have not yet looked
into btrfs, they do raid5 as well right?
But all this is far down the road, off course I'll send RFCs first. The
above push is just for that unique objects groups/striping/mirroring, which
is very small code, a couple of functions actually, over the basic IO.
Thanks for asking, though.
Boaz
prev parent reply other threads:[~2010-03-07 8:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-04 12:10 [GIT PULL] exofs changes for 2.6.34 Boaz Harrosh
2010-03-04 14:00 ` Christoph Hellwig
2010-03-07 8:32 ` Boaz Harrosh [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=4B93649F.10303@panasas.com \
--to=bharrosh@panasas.com \
--cc=hch@infradead.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=osd-dev@open-osd.org \
--cc=torvalds@linux-foundation.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;
as well as URLs for NNTP newsgroup(s).