linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "H. Peter Anvin" <hpa@zytor.com>
To: Yuri Tikhonov <yur@emcraft.com>
Cc: "Williams, Dan J" <dan.j.williams@intel.com>,
	Neil Brown <neilb@suse.de>, Wolfgang Denk <wd@denx.de>,
	Detlev Zundel <dzu@denx.de>,
	linux-raid@vger.kernel.org
Subject: Re: [md-raid6-accel PATCH 02/12] async_tx: RAID-6 recovery implementation
Date: Thu, 27 Dec 2007 18:29:31 -0800	[thread overview]
Message-ID: <47745F8B.8070805@zytor.com> (raw)
In-Reply-To: <200712041428.12094.yur@emcraft.com>

Yuri Tikhonov wrote:
>  This patch adds support for asynchronous RAID-6 recovery operations.
> 
>  An asynchronous implementation using async_tx API is provided to compute
> two missing data blocks (async_r6_dd_recov) and to compute one missing data
> block and one missing parity_block (async_r6_dp_recov).
> 
>  In general, the RAID-6 recovery API is the wrappers which organize the
> calculations algorithms using async_pqxor().
> 
>  Please refer to the "The mathematics of RAID-6" wtite-paper written by
> H.Peter Anvin available at www.kernel.org/pub/linux/kernel/people/hpa/raid6.pdf
> for the theoretical basement of the algorithms implemented here.
> 
>  Signed-off-by: Yuri Tikhonov <yur@emcraft.com>
>  Signed-off-by: Mikhail Cherkashin <mike@emcraft.com>
> --

I really, *really*, don't like the name "pqxor", because it is actively 
misleading.  The P syndrome is an XOR, but the Q syndrome is not, and in 
particular, does not exhibit the same properties as one would expect 
from an XOR, in particular commutativity.

	-hpa

      reply	other threads:[~2007-12-28  2:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-04 11:28 [md-raid6-accel PATCH 02/12] async_tx: RAID-6 recovery implementation Yuri Tikhonov
2007-12-28  2:29 ` H. Peter Anvin [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=47745F8B.8070805@zytor.com \
    --to=hpa@zytor.com \
    --cc=dan.j.williams@intel.com \
    --cc=dzu@denx.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    --cc=wd@denx.de \
    --cc=yur@emcraft.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).