From: Rene Rebe <rene.rebe@gmx.net>
To: Lionel.Bouton@inet6.fr
Cc: kernel@nn7.de, linux-kernel@vger.kernel.org
Subject: Re: choice of raid5 checksumming algorithm wrong ?
Date: Sat, 11 Jan 2003 20:39:13 +0100 (CET) [thread overview]
Message-ID: <20030111.203913.846936097.rene.rebe@gmx.net> (raw)
In-Reply-To: <3E203C00.5060403@inet6.fr>
Hi.
I also consider the kprint message a useability bug - and this is why
I posted a patch that prints out that the algorithm is choosen to
write "arround" the L2 cache ... - We patch this in our ROCK Linux
standard patches ...
On: Sat, 11 Jan 2003 16:45:04 +0100,
Lionel Bouton <Lionel.Bouton@inet6.fr> wrote:
> Soeren Sonnenburg wrote:
>
> >Hi!
> >
> >I really do wonder whether the displayed message is wrong or why it
> >always chooses the slowest checksumming function (happens with 2.4.19 -
> >21pre3)
> >
> >
> SSE is always preferred because unlike other checksumming code it
> doesn't use the processor caches when reading/writing data/checksum.
> This is slower (if several GB/s can be considered slow) for the
> checksumming but far better for the overall system performance.
>
> LB.
- René
--
René Rebe - Europe/Germany/Berlin
e-mail: rene.rebe@gmx.net, rene@rocklinux.org
web: www.rocklinux.org, drocklinux.dyndns.org/rene/
Anyone sending unwanted advertising e-mail to this address will be
charged $25 for network traffic and computing time. By extracting my
address from this message or its header, you agree to these terms.
next prev parent reply other threads:[~2003-01-11 19:33 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-11 6:26 Soeren Sonnenburg
2003-01-11 15:45 ` Lionel Bouton
2003-01-11 19:39 ` Rene Rebe [this message]
2003-01-11 19:52 ` Soeren Sonnenburg
2003-01-11 20:20 ` Rene Rebe
2003-01-12 14:44 ` Mr. James W. Laferriere
2003-01-12 16:14 ` Rene Rebe
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=20030111.203913.846936097.rene.rebe@gmx.net \
--to=rene.rebe@gmx.net \
--cc=Lionel.Bouton@inet6.fr \
--cc=kernel@nn7.de \
--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
all inboxes | Powered by JetHome®