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 12:08:12 +0100 [thread overview]
Message-ID: <200901191208.13591.bs@q-leap.de> (raw)
In-Reply-To: <49745D91.8010802@rabbit.us>
On Monday 19 January 2009 12:01:37 Peter Rabbitson wrote:
> Bernd Schubert wrote:
> > 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,
>
> And on the same bus (the last lspci) I have:
>
> 02:04.0 Ethernet controller: Intel Corporation 82541PI Gigabit Ethernet
> Controller (rev 05)
> Subsystem: Intel Corporation PRO/1000 GT Desktop Adapter
> Flags: bus master, 66MHz, medium devsel, latency 64, IRQ 26
> Memory at fc5a0000 (32-bit, non-prefetchable) [size=128K]
> Memory at fc580000 (32-bit, non-prefetchable) [size=128K]
> I/O ports at b000 [size=64]
> Expansion ROM at fc460000 [disabled] [size=128K]
> Capabilities: [dc] Power Management version 2
> Capabilities: [e4] PCI-X non-bridge device
> Kernel driver in use: e1000
>
> which afaik brings everything to 32bits no?
Hmm, I don't know what happens if a 32-bit card is in a 64bit PCI-X bus.
Wouldn't it only use half of the available lines for this card and all lines
for the 64bit cards? Hmm, on the other hand your maximum combined rate seems
to be at around 240 MB/s, which is close to 32bit x 66 MHz.Any chance you can
remove this NIC and retest?
Cheers,
Bernd
--
Bernd Schubert
Q-Leap Networks GmbH
next prev parent reply other threads:[~2009-01-19 11:08 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
2009-01-19 11:01 ` Peter Rabbitson
2009-01-19 11:08 ` Bernd Schubert [this message]
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=200901191208.13591.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).