From: Boaz Harrosh <bharrosh@panasas.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
linux-fsdevel <linux-fsdevel@vger.kernel.org>,
NFS list <linux-nfs@vger.kernel.org>,
open-osd <osd-dev@open-osd.org>
Cc: Elizabeth Ellenbogen Ziph <elizabeth@linuxbox.com>
Subject: [GIT PULL] exofs: raid6 support for the 3.16 merge window
Date: Fri, 6 Jun 2014 11:33:55 +0300 [thread overview]
Message-ID: <53917CF3.3010209@panasas.com> (raw)
Hi Linus
The following changes since commit:
[d6d211db] Linux 3.15-rc5 (2014-05-09 13:10:52 -0700)
are available in the git repository at:
git://git.open-osd.org/linux-open-osd.git for-linus
for you to fetch changes up to:
[ce5d36aa] ore: Support for raid 6 (2014-05-22 14:48:15 +0300)
proud to present support for raid6 in ORE.
These simple patches will enable raid6 using the Kernel's raid6_pq engine
for support under exofs and pnfs-objects. There is nothing needed to do
at exofs and pnfs-obj. Just fire your mkfs.exofs with --raid=6 (that was
already supported before) and off you go as usual. The ORE will pick up
the new map and will start writing two devices of redundancy bits.
The patches are so simple because most of the ORE was already for the
general raid case, only a few bug fixes were needed and the actual wiring
into the raid6_pq engine.
Thanks
Boaz
----------------------------------------------------------------
Boaz Harrosh (3):
ore: (trivial) reformat some code
ore: Remove redundant dev_order(), more cleanups
ore: Support for raid 6
fs/exofs/Kconfig.ore | 2 ++
fs/exofs/ore.c | 100 ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++------------------------------------
fs/exofs/ore_raid.c | 56 ++++++++++++++++++++++++++++++--------------------------
fs/exofs/ore_raid.h | 21 ++-------------------
4 files changed, 98 insertions(+), 81 deletions(-)
reply other threads:[~2014-06-06 8:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=53917CF3.3010209@panasas.com \
--to=bharrosh@panasas.com \
--cc=elizabeth@linuxbox.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-nfs@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 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.