From: Chris Boot <bootc@bootc.net>
To: Linux Kernel <linux-kernel@vger.kernel.org>
Subject: MD Raid 6: poor algorithm choice?
Date: Thu, 23 Feb 2006 18:00:10 +0000 [thread overview]
Message-ID: <43FDF82A.5050201@bootc.net> (raw)
Hi all,
[4295106.360000] raid6: int32x1 714 MB/s
[4295106.381000] raid6: int32x2 742 MB/s
[4295106.403000] raid6: int32x4 632 MB/s
[4295106.429000] raid6: int32x8 523 MB/s
[4295106.453000] raid6: mmxx1 1476 MB/s
[4295106.474000] raid6: mmxx2 2500 MB/s
[4295106.500000] raid6: sse1x1 1375 MB/s
[4295106.521000] raid6: sse1x2 2339 MB/s
[4295106.524000] raid6: using algorithm sse1x2 (2339 MB/s)
[4295106.531000] md: raid6 personality registered for level 6
I just loaded the raid6 module for fun (might end up using it one day), and I
was surprised at its choice of algorithm. By the messages above, I would have
assumed it would choose the mmxx2 algorithm at 2500 MB/s instead of sse1x2 at
the slightly slower 2339 MB/s. This is probably entirely expected behaviour, but
why?
Cheers,
Chris
--
Chris Boot
bootc@bootc.net
http://www.bootc.net/
next reply other threads:[~2006-02-23 18:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-23 18:00 Chris Boot [this message]
2006-02-23 21:09 ` MD Raid 6: poor algorithm choice? thunder7
2006-02-23 21:31 ` Chris Boot
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=43FDF82A.5050201@bootc.net \
--to=bootc@bootc.net \
--cc=linux-kernel@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