From: Benny Halevy <benny@tonian.com>
To: Boaz Harrosh <bharrosh@panasas.com>
Cc: bhalevy@tonian.com, "Welch, Brent" <welch@panasas.com>,
open-osd <osd-dev@open-osd.org>,
NFS list <linux-nfs@vger.kernel.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>
Subject: Re: [PATCHSET 0/1 0/6] ore: RAID5 Support
Date: Sun, 16 Oct 2011 18:27:15 -0700 [thread overview]
Message-ID: <CAFcxaFstfSu4n4eoS3tiwziCEEarxr7UnoVt=Q8wsDiMgiriNA@mail.gmail.com> (raw)
In-Reply-To: <4E98B8F2.7090804@panasas.com>
Sure. Monday it is.
Benny
On Fri, Oct 14, 2011 at 3:34 PM, Boaz Harrosh <bharrosh@panasas.com> wrote:
> Thanks Benny.
>
> Is it OK if we merge, pnfs tree and open-osd, on Monday in BAT first thing?
> Tonight it's to late, and tomorrow I'm already flying. So Monday.
>
> Have a safe trip
> Boaz
>
> On 10/14/2011 07:50 PM, Benny Halevy wrote:
>> Awesome!
>>
>> Benny
>> -----Original Message-----
>> From: Boaz Harrosh <bharrosh@panasas.com>
>> Sender: linux-nfs-owner@vger.kernel.org
>> Date: Fri, 14 Oct 2011 19:24:14
>> To: Welch, Brent<welch@panasas.com>; open-osd<osd-dev@open-osd.org>; NFS list<linux-nfs@vger.kernel.org>; linux-fsdevel<linux-fsdevel@vger.kernel.org>
>> Subject: [PATCHSET 0/1 0/6] ore: RAID5 Support
>>
>>
>> I'm proud to present RAID5 support to ORE. Which enables raid5 for both
>> exofs and pnfs-objects-layout driver.
>>
>> The ORE with raid0/1/5 and soon 6 support has become a compact and abstract
>> library, that with not a lot of effort, can support not only OSD but any
>> type of devices. For example BTRFS, does it have a RAID5 support yet? if
>> not it could use ORE. The ORE gets a bunch of pages at the top and produces
>> bios for each device at the bottom. The libosd API can be easily abstracted
>> and be used for block devices, just the same. The RAID layout supported by
>> ORE is very rich, multi layered striping/mirroring/raid. even reacher then
>> stacked MD. You can read about this layout here:
>> http://git.open-osd.org/gitweb.cgi?p=ietf-rfc5664.git;a=blob_plain;f=draft-ietf-nfsv4-rfc5664bis.html;hb=boaz2
>> Start at: 5.3. "Data Mapping Schemes" up to:
>> 5.4.5. "RAID Usage and Implementation Notes"
>>
>> There where some problems with the previous patchset here are
>> the differences I squashed it to a new patchset at osd/linux-next.
>>
>> [PATCH 1/1] SQUASHME: into: ore: Only IO one group at a time (API change)
>>
>> And without farther ado Here is the RAID5 support. This is highly complicated
>> stuff, for humble me at least, and I would appreciate any review and/or comments
>> you guys can give it. Thanks in advance. (Pretty Please? :-))
>>
>> [PATCH 1/6] ore: Make ore_calc_stripe_info EXPORT_SYMBOL
>> [PATCH 2/6] ore: RAID5 read
>> [PATCH 3/6] ore: RAID5 Write
>> [PATCH 4/6] exofs: Support for RAID5 read-4-write interface.
>> [PATCH 5/6] pnfs-obj: Support for RAID5 read-4-write interface.
>> [PATCH 6/6] ore: Enable RAID5 mounts
>>
>> A tree with above plus all prerequisites is at:
>> $ git clone git://open-osd.org/linux-open-osd linux-next
>> [http://git.open-osd.org/gitweb.cgi?p=linux-open-osd.git;a=shortlog;h=refs/heads/merge_and_compile]
>>
>> The code passes my tests, the highlight of which is git-clone linux and compare to
>> and identical clone on ext4. But there must be month of farther testing done on this
>> to get it better. For example. Aligned on stripe IO write back should be improved on
>> all the way down to the VFS layer.
>>
>> Thanks
>> Boaz
>> --
>> To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
>> the body of a message to majordomo@vger.kernel.org
>> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
--
To unsubscribe from this list: send the line "unsubscribe linux-fsdevel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2011-10-17 1:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 17:24 [PATCHSET 0/1 0/6] ore: RAID5 Support Boaz Harrosh
2011-10-14 17:27 ` [PATCH 1/6] ore: Make ore_calc_stripe_info EXPORT_SYMBOL Boaz Harrosh
[not found] ` <4E98703E.7040605-C4P08NqkoRlBDgjK7y7TUQ@public.gmane.org>
2011-10-14 17:26 ` [PATCH] SQUASHME: into: ore: Only IO one group at a time (API change) Boaz Harrosh
2011-10-14 17:34 ` [PATCH 2/6] ore: RAID5 read Boaz Harrosh
2011-10-14 17:35 ` [PATCH 3/6] ore: RAID5 Write Boaz Harrosh
2011-10-14 17:36 ` [PATCH 5/6] pnfs-obj: Support for RAID5 read-4-write interface Boaz Harrosh
2011-10-14 17:37 ` [PATCH 6/6] ore: Enable RAID5 mounts Boaz Harrosh
2011-10-14 17:35 ` [PATCH 4/6] exofs: Support for RAID5 read-4-write interface Boaz Harrosh
2011-10-14 17:50 ` [PATCHSET 0/1 0/6] ore: RAID5 Support Benny Halevy
2011-10-14 22:34 ` Boaz Harrosh
2011-10-17 1:27 ` Benny Halevy [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='CAFcxaFstfSu4n4eoS3tiwziCEEarxr7UnoVt=Q8wsDiMgiriNA@mail.gmail.com' \
--to=benny@tonian.com \
--cc=bhalevy@tonian.com \
--cc=bharrosh@panasas.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@vger.kernel.org \
--cc=osd-dev@open-osd.org \
--cc=welch@panasas.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).