public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dave Jones <davej@redhat.com>
To: Evaldo Gardenali <evaldo@gardenali.biz>
Cc: linux-kernel@vger.kernel.org
Subject: Re: buggy raid checksumming selection?
Date: Fri, 23 Jan 2004 14:13:53 +0000	[thread overview]
Message-ID: <20040123141352.GA19002@redhat.com> (raw)
In-Reply-To: <40112465.8040801@gardenali.biz>

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 ?

	Dave


  parent reply	other threads:[~2004-01-23 14:15 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 [this message]
2004-01-23 14:22   ` Nick Piggin
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=20040123141352.GA19002@redhat.com \
    --to=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