Re: Is this enough for us to have triple-parity RAID?

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]


Hi Alex,

> Just being curious, any mathematical improvement in Reed-Solomon's
> code like the
> RS(96,64) you mentioned? The calculation of RS involves arbitrary
> multiplication in a
> Galois field and table look-up has to be used. Has that already changed?

AFAIK (details are not public) it uses the stardard
RS with LUT operations.

Considering that this is for network disks, I suppose
there is no performance problem.

The RS(255,223) or RS(160,128) are very old encoding
schemes, we talk about Voyager space probe here.

What I know about improvement, is the decoding using
the Berlekamp–Massey algorithm.
This is quite hard, since it also find *where* error
are, but it seems there is some work out there on
how to implement it very efficiently.

My personal opinion is that the first thing to do is
to have a working system, later it could be possible
to improve performance by different optimizations.

For example LUT multiplication might or might not be
the best way, but at first it is the easy way to do it.

bye,

-- 

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


[ATA RAID]     [Linux SCSI Target Infrastructure]     [Managing RAID on Linux]     [Linux IDE]     [Linux SCSI]     [Linux Hams]     [Device-Mapper]     [Kernel]     [Linux Books]     [Linux Admin]     [Linux Net]     [GFS]     [RPM]     [git]     [Photos]     [Yosemite Photos]     [Yosemite News]     [AMD 64]     [Linux Networking]

Add to Google Powered by Linux