linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Brad Campbell <brad@wasp.net.au>
To: Neil Brown <neilb@suse.de>
Cc: RAID Linux <linux-raid@vger.kernel.org>
Subject: Re: RAID-6 check slow..
Date: Tue, 22 Aug 2006 12:07:16 +0400	[thread overview]
Message-ID: <44EABB34.60603@wasp.net.au> (raw)
In-Reply-To: <17642.47012.109307.542850@cse.unsw.edu.au>

Neil Brown wrote:

> Hmm....  nothing obvious.
> Have you tried increasing 
>   /proc/sys/dev/raid/speed_limit_min:1000
> just in case that makes a difference (it shouldn't but you seem to be
> down close to that speed).

No difference..

> What speed in the raid6 algorithm used - as reported at boot time?
> Again, I doubt that is the problem - if should be about 1000 times
> speed you are seeing.

raid6: int32x1    739 MB/s
raid6: int32x2    991 MB/s
raid6: int32x4    636 MB/s
raid6: int32x8    587 MB/s
raid6: mmxx1     1556 MB/s
raid6: mmxx2     2701 MB/s
raid6: sse1x1    1432 MB/s
raid6: sse1x2    2398 MB/s
raid6: using algorithm sse1x2 (2398 MB/s)
md: raid6 personality registered for level 6
raid5: automatically using best checksumming function: pIII_sse
    pIII_sse  :  2345.000 MB/sec
raid5: using function: pIII_sse (2345.000 MB/sec)
md: md driver 0.90.3 MAX_MD_DEVS=256, MD_SB_DISKS=27
md: bitmap version 4.39


> What if you try increasing /sys/block/md0/md/stripe_cache_size ?

I already have this at 8192 (which appears to be HUGE for 15 drives, but I've got 1.5GB of ram and 
nothing else using it)

> That's all I can think of for now.
> 

Oh well, no stress.. Just thought I'd ask anyway :)

Brad
-- 
"Human beings, who are almost unique in having the ability
to learn from the experience of others, are also remarkable
for their apparent disinclination to do so." -- Douglas Adams

      reply	other threads:[~2006-08-22  8:07 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-22  7:26 RAID-6 check slow Brad Campbell
2006-08-22  7:52 ` Neil Brown
2006-08-22  8:07   ` Brad Campbell [this message]

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=44EABB34.60603@wasp.net.au \
    --to=brad@wasp.net.au \
    --cc=linux-raid@vger.kernel.org \
    --cc=neilb@suse.de \
    /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).