From: "David Lethe" <david@santools.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>,
linux-kernel@vger.kernel.org, linux-raid@vger.kernel.org,
xfs@oss.sgi.com
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 8:52:00 -0500 [thread overview]
Message-ID: <13c501c8c3ee$c6a31318$330ef40a@exchange.rackspace.com> (raw)
-----Original Message-----
From: "Justin Piszcz" <jpiszcz@lucidpixels.com>
Subj: Re: Limits of the 965 chipset & 3 PCI-e cards/southbridge? ~774MiB/s peak for read, ~650MiB/s peak for write?
Date: Sun Jun 1, 2008 6:02 am
Size: 793 bytes
To: "linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>; "linux-raid@vger.kernel.org" <linux-raid@vger.kernel.org>; "xfs@oss.sgi.com" <xfs@oss.sgi.com>
On Sun, 1 Jun 2008, Justin Piszcz 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)..
Small correction, they are 7200.11 Seagate Desktop Drives (ST31000340AS),
not enterprise drives:
http://www.seagate.com/ww/v/index.jsp?vgnextoid=0732f141e7f43110VgnVCM100000f5ee0a0aRCRD
http://www.newegg.com/Product/Product.aspx?Item=N82E16822148274
--
To unsubscribe from this list: send the line "unsubscribe linux-raid" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2008-06-01 13:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-01 13:52 David Lethe [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-01 9:45 Limits of the 965 chipset & 3 PCI-e cards/southbridge? ~774MiB/s peak for read, ~650MiB/s peak for write? 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='13c501c8c3ee$c6a31318$330ef40a@exchange.rackspace.com' \
--to=david@santools.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@vger.kernel.org \
--cc=xfs@oss.sgi.com \
/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).