From: Jurriaan <thunder7@xs4all.nl>
To: "J. Ryan Earl" <heretic@clanhk.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: AMD64 and RAID6
Date: Sat, 8 May 2004 20:52:29 +0200 [thread overview]
Message-ID: <20040508185229.GA869@middle.of.nowhere> (raw)
In-Reply-To: <409D1D86.6050907@clanhk.org>
From: J. Ryan Earl <heretic@clanhk.org>
Date: Sat, May 08, 2004 at 12:48:54PM -0500
> Why doesn't RAID6 use the int64x4 algorithm in this situation? What is
> the motivation of setting the 'prefer field' on the sse algorithms and
> not on the integer based algorithms?
>
IIRC, the sse variants have better cache-behaviour, and are thus almost
always selected.
Try googling for exact answers, this has come up before.
HTH,
Jurriaan
--
Spock: "Logic, logic, logic... Logic is the beginning of wisdom,
Valeris, not the end."
"STVI:TUC", Stardate 9522.6
Debian (Unstable) GNU/Linux 2.6.6-rc3-mm1 2x6062 bogomips 0.06 0.16
next prev parent reply other threads:[~2004-05-08 18:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-08 17:48 AMD64 and RAID6 J. Ryan Earl
2004-05-08 18:52 ` Jurriaan [this message]
2004-05-11 2:13 ` 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=20040508185229.GA869@middle.of.nowhere \
--to=thunder7@xs4all.nl \
--cc=heretic@clanhk.org \
--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