linux-raid.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bernd Schubert <bs@q-leap.de>
To: Peter Rabbitson <rabbit+list@rabbit.us>
Cc: linux-raid@vger.kernel.org
Subject: Re: Raid6 write performance
Date: Mon, 19 Jan 2009 11:58:43 +0100	[thread overview]
Message-ID: <200901191158.44822.bs@q-leap.de> (raw)
In-Reply-To: <497457D7.90101@rabbit.us>

Hello Peter,

On Monday 19 January 2009 11:37:11 Peter Rabbitson wrote:
> Peter Rabbitson wrote:
> > Hi,
> >
> > I am experimenting with raid6 on 4 drives on 2.6.27.11. The problem I am
> > having is that no matter what chunk size I use, the write benchmark
> > always comes out at single drive speed, although I should be seeing
> > double drive speed (read speed is at near 4x as expected).
>
> Please disregard this, I appear to be having some sort of weird hardware
> congestion. Can someone explain what could be going on?

I don't know what it is going on, but:


> Combined read speed - limited by the width of a 32bit 66mhz PCI (dev
> 02:04.0 below)

No! You you do have PCI-X, so 64bit with 66MHz. Maybe you are even luckily and 
it is as 133MHz, depends on how many other devices are connected to this bus. 
lspci will always say it is running at 66MHz, though, it also might run at 
100 or 133 MHz,

>
> 02:03.0 Mass storage controller: Silicon Image, Inc. SiI 3124 PCI-X
> Serial ATA Controller (rev 02)  <----- where the 4 drives are attached to
> 	Subsystem: Silicon Image, Inc. SiI 3124 PCI-X Serial ATA Controller
> 	Flags: bus master, stepping, 66MHz, medium devsel, latency 64, IRQ 25
> 	Memory at fc5fd800 (64-bit, non-prefetchable) [size=128]
> 	Memory at fc5f0000 (64-bit, non-prefetchable) [size=32K]
> 	I/O ports at bc00 [size=16]
> 	Expansion ROM at fc480000 [disabled] [size=512K]
> 	Capabilities: [64] Power Management version 2
> 	Capabilities: [40] PCI-X non-bridge device
> 	Capabilities: [54] Message Signalled Interrupts: Mask- 64bit+ Queue=0/0


Cheers,
Bernd

-- 
Bernd Schubert
Q-Leap Networks GmbH

  reply	other threads:[~2009-01-19 10:58 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-19  7:40 Raid6 write performance Peter Rabbitson
2009-01-19  8:10 ` thomas62186218
2009-01-19  9:07   ` NiftyFedora Mitch
2009-01-26 18:47     ` Bill Davidsen
2009-01-19 12:48   ` Keld Jørn Simonsen
2009-01-19 12:50     ` Peter Rabbitson
2009-01-19 10:37 ` Peter Rabbitson
2009-01-19 10:58   ` Bernd Schubert [this message]
2009-01-19 11:01     ` Peter Rabbitson
2009-01-19 11:08       ` Bernd Schubert
2009-02-28  1:04 ` H. Peter Anvin
2009-03-01 19:12   ` Michał Przyłuski
2009-03-01 20:35     ` H. Peter Anvin
2009-03-01 19:19   ` Peter Rabbitson
2009-03-13 17:11     ` Bill Davidsen

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=200901191158.44822.bs@q-leap.de \
    --to=bs@q-leap.de \
    --cc=linux-raid@vger.kernel.org \
    --cc=rabbit+list@rabbit.us \
    /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).