linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>
To: David Brown <david@westcontrol.com>
Cc: Piergiorgio Sartor <piergiorgio.sartor@nexgo.de>,
	linux-raid@vger.kernel.org
Subject: Re: Is this enough for us to have triple-parity RAID?
Date: Wed, 18 Apr 2012 22:39:42 +0200	[thread overview]
Message-ID: <20120418203942.GA7731@lazy.lzy> (raw)
In-Reply-To: <4F8F21F3.5060108@westcontrol.com>

Hi David,

> I know that 8 is not a generator, and therefore you cannot expect to
> get a full set of (256 - noOfParities) disks.  But picking another
> generator (such as 16) is not enough to guarantee you the full range
> - it is a requirement, but not sufficient.  The generators need to
> be independent of each other, in the sense that all the simultaneous
> equations for all the combinations of failed disks need to be
> soluble.

uhm, than how can RS(255,223) or the equivalent RS(160,128) work?

In all the papers I saw, it was never mentioned the "indepence"
of the GF generators, do you have any reference I can look into?
 
> It turns out that if you pick 16 as the forth parity generator here
> (1, 2, 4, 16), then you can only have 5 data disks.  In fact, there
> are no other values for g3 that give significantly more than 21 data
> disks in combination with (1, 2, 4), whether or not they happen to
> be a generator for all of GF(2⁸).

That's really interesting, but, again, I fail to see how
this could be, given that there are larger range codes.

Maybe they do not use the polynomial 285, in fact AES uses
283, but the first generator is 3 and not 2, actually no
powers of two appears, if I remember correctly.

> When I started out with this, I thought it was as simple as you are
> suggesting.  But it is not - picking a set of generators for GF(2⁸)
> is not enough.  You have to check that all the solution matrices are
> invertible for all combinations of failed disks.

Check or prove? How do you do that?
And what do you mean exactly?
I mean with "all combination of failed disks".

As already wrote, par2 implements a generic RS
parity generator, and it works with very little
limitations. Do they something different?
 
> In fact, it is a little surprising that (1, 2, 4) works so well for
> triple parity.  I don't know whether it is just luck, or genius in
> Peter Anvin's choice of the multiply operation.

The GF(256) with polynomial 285 seems quite a
structure of choice, I wonder if the polynomial
must fullfill specific conditions in order to
allow a wider range of parities...

bye,

-- 

piergiorgio
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2012-04-18 20:39 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-17  6:11 Is this enough for us to have triple-parity RAID? Alex
2012-04-17  7:58 ` David Brown
2012-04-17 16:37   ` Stefan /*St0fF*/ Hübner
2012-04-18 14:15     ` Alex
2012-04-18 14:11       ` David Brown
2012-04-17 17:16   ` Piergiorgio Sartor
2012-04-17 20:18     ` David Brown
2012-04-17 20:54       ` Piergiorgio Sartor
2012-04-18 18:22       ` Piergiorgio Sartor
2012-04-18 20:20         ` David Brown
2012-04-18 20:39           ` Piergiorgio Sartor [this message]
2012-04-19 18:16       ` H. Peter Anvin
2012-04-20  2:27         ` Alex
2012-04-20  3:00           ` H. Peter Anvin
2012-04-20  3:32             ` Alex
2012-04-20 18:58               ` David Brown
2012-04-20 19:39                 ` H. Peter Anvin
2012-04-20 21:04                   ` Piergiorgio Sartor
2012-04-20 21:01                 ` Piergiorgio Sartor
2012-04-20 21:29                   ` Peter Grandi
2012-04-20 22:31                     ` Piergiorgio Sartor
2012-04-21  9:51                       ` Peter Grandi
2012-04-21 11:18                         ` Piergiorgio Sartor
2012-04-22  3:14                           ` Alex
2012-04-22  8:57                             ` Piergiorgio Sartor
2012-04-20  7:45 ` Stan Hoeppner
2012-04-23 15:26   ` Alex
2012-04-25  1:20     ` Stan Hoeppner
2012-04-25  2:45       ` Alex
2012-04-25 16:59         ` Emmanuel Noobadmin
2012-04-25 19:29           ` David Brown
2012-04-26  2:30           ` Alex
2012-04-27 15:15             ` Emmanuel Noobadmin
2012-05-01 16:38               ` Alex
2012-04-26  4:24           ` Alex

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=20120418203942.GA7731@lazy.lzy \
    --to=piergiorgio.sartor@nexgo.de \
    --cc=david@westcontrol.com \
    --cc=linux-raid@vger.kernel.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).