mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Daniel J Blueman" <daniel.blueman@gmail.com>
To: "Justin Piszcz" <jpiszcz@lucidpixels.com>
Cc: "Linux Kernel" <linux-kernel@vger.kernel.org>
Subject: Re: Limits of the 965 chipset & 3 PCI-e cards/southbridge? ~774MiB/s peak for read, ~650MiB/s peak for write?
Date: Sun, 1 Jun 2008 22:23:04 +0100	[thread overview]
Message-ID: <6278d2220806011423o22e98f27qfd72fbd152d19d9f@mail.gmail.com> (raw)

On 1 Jun, 10:50, Justin Piszcz <jpis...@lucidpixels.com> wrote:
> I have 12 enterprise-class seagate 1TiB disks on a 965 desktop board and
> it appears I have hit the limit, if I were able to get the maximum speed
> of all drives, ~70MiB/avg * 12 = 840MiB/s but it seems to stop aound 774
> MiB/s (currently running badblocks on all drives)..

Nice test. The Seagate 7200.11 drives deliver 120MB/s (outer zone,
raw) each, and there is an issue with CFQ dispatching requests; see:

http://groups.google.co.uk/group/linux.kernel/browse_thread/thread/b88264b084a2dfe0/a1bc0f67837bad00

A quick workaround tweak is:

# echo 0 >/sys/block/sda/queue/iosched/slice_idle

Does this help any? This gives the difference of ~68MB/s vs ~120MB/s
on my 7200.11 ;-) .

That said, the i965 chipset is fairly contemporary, but if that 2GB/s
DMI connection is the bidirectional bandwidth (likely), then maybe
you're hitting that limit: Intel's DMI bus is based on PCIe, thus will
use 128 byte PCI-e Max Payload packets (as in the rest of the
chipset), which IIRC theoretically maxes you out near 800MB/s.

The X48 chipset may allow you to crank the Max Payload to 256 (setpci
and the Intel chipset docs), if it doesn't default to 256, like in
5400 server chipsets. This chipset is where the fun really starts eg
hdparm -T giving >10GB/s, like in Itanium2s ;-) .

Thanks,
  Daniel
-- 
Daniel J Blueman

             reply	other threads:[~2008-06-01 21:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-01 21:23 Daniel J Blueman [this message]
2008-06-01 21:26 ` Justin Piszcz
2008-06-01 23:43 ` Justin Piszcz
  -- strict thread matches above, loose matches on Subject: below --
2008-06-01 13:52 David Lethe
2008-06-01  9:45 Justin Piszcz
2008-06-01 11:01 ` Justin Piszcz
2008-06-01 11:26   ` Justin Piszcz
2008-06-01 12:20     ` Willy Tarreau
2008-06-03 18:44 ` Bryan Mesich

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=6278d2220806011423o22e98f27qfd72fbd152d19d9f@mail.gmail.com \
    --to=daniel.blueman@gmail.com \
    --cc=jpiszcz@lucidpixels.com \
    --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

all inboxes | Powered by JetHome®