From: Nick Piggin <piggin@cyberone.com.au>
To: Dave Jones <davej@redhat.com>
Cc: Evaldo Gardenali <evaldo@gardenali.biz>, linux-kernel@vger.kernel.org
Subject: Re: buggy raid checksumming selection?
Date: Sat, 24 Jan 2004 01:22:33 +1100 [thread overview]
Message-ID: <40112E29.4060800@cyberone.com.au> (raw)
In-Reply-To: <20040123141352.GA19002@redhat.com>
Dave Jones wrote:
>On Fri, Jan 23, 2004 at 11:40:53AM -0200, Evaldo Gardenali wrote:
>
> > Uhh. correct me if I am wrong, but shouldnt it select the fastest algorithm?
>
>No, if it can choose a function which avoids polluting the cache over
>one that doesn't, it will. Even if that means slightly less raw throughput
>
>This comes up time after time, maybe we need a printk in that case ?
>
How about removing the entire output? Is it really needed?
next prev parent reply other threads:[~2004-01-23 14:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-01-23 13:40 buggy raid checksumming selection? Evaldo Gardenali
2004-01-23 13:58 ` John Bradford
2004-01-23 14:13 ` Dave Jones
2004-01-23 14:22 ` Nick Piggin [this message]
2004-01-23 14:38 ` Dave Jones
2004-01-23 15:16 ` Ed Tomlinson
-- strict thread matches above, loose matches on Subject: below --
2004-01-23 14:27 Randal, Phil
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=40112E29.4060800@cyberone.com.au \
--to=piggin@cyberone.com.au \
--cc=davej@redhat.com \
--cc=evaldo@gardenali.biz \
--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