From: Rene Rebe <rene.rebe@gmx.net>
To: kernel@nn7.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: choice of raid5 checksumming algorithm wrong ?
Date: Sat, 11 Jan 2003 21:20:56 +0100 (CET) [thread overview]
Message-ID: <20030111.212056.607951684.rene.rebe@gmx.net> (raw)
In-Reply-To: <1042314720.1225.4.camel@sun>
Hi.
In the case s.o. wants to pull the patch:
http://www.rocklinux.org/sources/package/base/linux24/82-raid5-niceer-output.patch
It is only a one-liner. It is not really nice since I print the
"writing arround L2 cache" text when XOR_SELECT_TEMPLATE is defined -
this might also be the case for an later AlitVec version for PowerPC
or so. So we might want a more generic text - or a text in the
appropriated .h file whetre XOR_SELECT_TEMPLATE is defined ...
On: 11 Jan 2003 20:52:00 +0100,
Soeren Sonnenburg <kernel@nn7.de> wrote:
> On Sat, 2003-01-11 at 20:39, Rene Rebe wrote:
> > 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 ...
>
> I would vote for such a cosmetic patch to be included...
>
> Soeren.
>
> > 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.
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
next prev parent reply other threads:[~2003-01-11 20:15 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
2003-01-11 19:52 ` Soeren Sonnenburg
2003-01-11 20:20 ` Rene Rebe [this message]
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.212056.607951684.rene.rebe@gmx.net \
--to=rene.rebe@gmx.net \
--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®