linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Tim Moore <linux-raid@nsr500.net>
To: linux-raid@vger.kernel.org
Subject: Re: raid5 performance - 2.4.28
Date: Tue, 11 Jan 2005 21:18:44 -0800	[thread overview]
Message-ID: <41E4B334.2020104@nsr500.net> (raw)
In-Reply-To: <Pine.LNX.4.44.0501101600250.28809-100000@coffee.psychology.mcmaster.ca>

Mark Hahn wrote:
...
>>I'm also experimenting with this patch to see if the xor hardwire for 
>>modern intel/AMD architectures is still valid.  With the old processor 
>>p5_mmx was always picked and always within a few MB/s.  The new XP is all 
>>over the map.
> 
> 
> this choice (using pIII_sse even if there's a faster alternative)
> is made because it doesn't dirty the cache.  are you suggesting that 
> whole-system performance is better with p5_mmx, even though or *because*
> the blocks are then in cache?  seems unlikley to me, since the checksum
> is only used on writes or degraded mode.  having written blocks in cache
> seems worthless, almost...

I'm an experimentor, not a theorist.  I am running a series of experiments 
to determine if, and by how much, the xor algorithm in 
include/asm-<arch>/xor.h influences RAID5 write performance and reconstruction.

I'll post results.

-- 

       reply	other threads:[~2005-01-12  5:18 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <Pine.LNX.4.44.0501101600250.28809-100000@coffee.psychology.mcmaster.ca>
2005-01-12  5:18 ` Tim Moore [this message]
2005-01-12  6:17   ` raid5 performance after upgrade to 2.4.28 Guy
2005-01-12  7:44     ` Guy
2005-01-13 16:24       ` Tim Moore
     [not found] <Pine.LNX.4.44.0501091639260.13461-100000@coffee.psychology.mcmaster.ca>
2005-01-10 16:26 ` raid5 performance - 2.4.28 Tim Moore
2005-01-09  5:28 Tim Moore

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=41E4B334.2020104@nsr500.net \
    --to=linux-raid@nsr500.net \
    --cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).