From: "H. Peter Anvin" <hpa@zytor.com>
To: Jakob Oestergaard <jakob@unthought.net>
Cc: linux-raid@vger.kernel.org
Subject: Re: RAID-6
Date: Tue, 12 Nov 2002 08:30:27 -0800 [thread overview]
Message-ID: <3DD12CA3.5090105@zytor.com> (raw)
In-Reply-To: 20021112162205.GB22407@unthought.net
Jakob Oestergaard wrote:
>>
>>a) write performance will be worse than RAID-5, but I believe it can
>> be kept to within a factor of 1.5-2.0 on machines with suitable
>> SIMD instruction sets (e.g. MMX or SSE-2);
>
> Please note that raw CPU power is usually *not* a limiting (or even
> significantly contributing) factor, on modern systems.
>
> Limitations are disk reads/writes/seeks, bus bandwidth, etc.
>
> You will probably cause more bus activity with RAID-6, and that might
> degrade performance. But I don't think you need to worry about
> MMX/SSE/... If you can do as well as the current RAID-5 code, then you
> will be in the clear until people have 1GB/sec disk transfer-rates on
> 500MHz PIII systems ;)
>
RAID-6 will, obviously, never do as well as RAID-5 -- you are doing more
work (both computational and data-pushing.) The RAID-6 syndrome
computation is actually extrememly expensive if you can't do it in
parallel. Fortunately there is a way to do it in parallel using MMX or
SSE-2, although it seems to exist by pure dumb luck -- certainly not by
design. I've tried to figure out how to generalize to using regular
32-bit or 64-bit integer registers, but it doesn't seem to work there.
Again, my initial analysis seems to indicate performance within about a
factor of 2.
>>b) read performance in normal and single failure degraded mode will be
>> comparable to RAID-5;
>
> Which again is like a RAID-0 with some extra seeks... Eg. not too bad
> with huge chunk sizes.
>
> You might want to consider using huge chunk-sizes when reading, but
> making sure that writes can be made on "sub-chunks" - so that one could
> run a RAID-6 with a 128k chunk size, yet have writes performed on 4k
> chunks. This is important for performance on both read and write, but
> it is an optimization the current RAID-5 code lacks.
That's an issue for the common framework, I'll leave that to Neil. It's
functionally equivalent between RAID-5 and -6.
>>c) read performance in dual failure degraded mode will be quite bad.
>>
>>I'm curious how much interest there would be in this, since I
>>certainly have enough projects without it, and I'm probably going to
>>need some of Neil's time to integrate it into the md driver and the
>>tools.
>
> I've seen quite some people ask for it. You might find a friend in "Roy
> Sigurd Karlsbach" - he for one has been asking (loudly) for it ;)
:) Enough people have responded that I think I have a project...
-hpa
next prev parent reply other threads:[~2002-11-12 16:30 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-11 18:52 RAID-6 H. Peter Anvin
2002-11-11 21:06 ` RAID-6 Derek Vadala
2002-11-11 22:44 ` RAID-6 Mr. James W. Laferriere
2002-11-11 23:05 ` RAID-6 H. Peter Anvin
2002-11-12 16:22 ` RAID-6 Jakob Oestergaard
2002-11-12 16:30 ` H. Peter Anvin [this message]
2002-11-12 19:01 ` RAID-6 H. Peter Anvin
2002-11-12 19:37 ` RAID-6 Neil Brown
2002-11-13 2:13 ` RAID-6 Jakob Oestergaard
2002-11-13 3:33 ` RAID-6 Neil Brown
2002-11-13 12:29 ` RAID-6 Jakob Oestergaard
2002-11-13 17:33 ` RAID-6 H. Peter Anvin
2002-11-13 18:07 ` RAID-6 Peter L. Ashford
2002-11-13 22:50 ` RAID-6 Neil Brown
2002-11-13 18:42 ` RAID-6 Peter L. Ashford
2002-11-13 22:48 ` RAID-6 Neil Brown
[not found] <Pine.GSO.4.30.0211111138080.15590-100000@multivac.sdsc.edu>
2002-11-11 19:47 ` RAID-6 H. Peter Anvin
-- strict thread matches above, loose matches on Subject: below --
2005-11-13 9:05 Raid-6 Rebuild question Brad Campbell
2005-11-13 10:05 ` Neil Brown
2005-11-16 17:54 ` RAID-6 Bill Davidsen
2005-11-16 20:39 ` RAID-6 Dan Stromberg
2005-12-29 18:29 ` RAID-6 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=3DD12CA3.5090105@zytor.com \
--to=hpa@zytor.com \
--cc=jakob@unthought.net \
--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).