From: "H. Peter Anvin" <hpa@zytor.com>
To: Dan Williams <dan.j.williams@intel.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
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: Thu, 16 Jul 2009 13:38:24 -0400 [thread overview]
Message-ID: <4A5F6590.9000006@zytor.com> (raw)
In-Reply-To: <e9c3a7c20907151223j1d976ea9gdd224c9e6c2c36e3@mail.gmail.com>
Dan Williams wrote:
> On Mon, Jul 13, 2009 at 7:11 AM, David Woodhouse<dwmw2@infradead.org> wrote:
>> We'll want to use these in btrfs too.
>>
>> Signed-off-by: David Woodhouse <David.Woodhouse@intel.com>
>
> Do you suspect that btrfs will also want to perform these operations
> asynchronously? I am preparing an updated release of the raid6
> offload patch kit, but the previous WIP release can be browsed at:
>
> http://git.kernel.org/?p=linux/kernel/git/djbw/async_tx.git;a=shortlog;h=raid6
>
> The routines are housed in crypto/async_tx/async_pq.c and
> crypto/async_tx/async_raid6_recov.c.
>
> I also wonder if the raid6 algos are a better fit under crypto/ alongside xor?
>
I am also sitting on a set of synchronous (CPU) acceleration patches for
RAID-6 recovery, just waiting for the APIs to stabilize.
-hpa
next prev parent reply other threads:[~2009-07-16 17:38 UTC|newest]
Thread overview: 34+ 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-15 22:11 ` Dan Williams
2009-07-16 17:38 ` H. Peter Anvin [this message]
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-17 19:12 ` Gregory Maxwell
2009-07-18 11:53 ` David Woodhouse
2009-07-18 11:53 ` David Woodhouse
2009-07-18 12:45 ` H. Peter Anvin
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 12:49 ` Ric Wheeler
2009-07-18 16:26 ` Dan Williams
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
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=4A5F6590.9000006@zytor.com \
--to=hpa@zytor.com \
--cc=chris.mason@oracle.com \
--cc=dan.j.williams@intel.com \
--cc=dwmw2@infradead.org \
--cc=linux-btrfs@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 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.