From: Andre Tomt <andre@tomt.net>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: Mark Lord <liml@rtr.ca>, Jeff Garzik <jeff@garzik.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-raid@vger.kernel.org
Subject: Re: Marvell 88SX7042 [4 Port SATA PCI-Express x4] Support/Questions
Date: Sun, 25 May 2008 21:43:28 +0200 [thread overview]
Message-ID: <4839C160.6010409@tomt.net> (raw)
In-Reply-To: <4839A63E.4050409@rtr.ca>
Mark Lord wrote:
> Justin Piszcz wrote:
>> If one bought enough of these, one could possibly achieve speeds in
>> excess(!) of 1 gigabyte/second with enough drives and SW RAID in Linux.
>> Does anyone have such a card? I would be interested if it could
>> sustain the maximum rate from each disk without any contention.
> ..
>
> Sure, if the bus and memory are fast enough. You'll hit the Linux/libata
> transactions/sec limit at some point, but I don't know what that is.
I'm seeing 800MB/s on ICH8/9R class chipsets on concurrent non-raid I/O,
however that's the limit of the PCIe bus used between the ICH (south,
IO) and the MCH (north, memory/cpu/video-pcie hub). ICH10 is supposed to
double that by moving up to PCI-e 2.0 on that link AFAIK.
> Eg. Here's a 4X (I think) card in my PCIe video slot:
Ah, of course making use of the video PCIe slot by putting as many ports
as you can on it will improve the situation somewhat as its generally
connected to the MCH directly. (mm, any plain/non-raid 88SX7xxx PCIe
cards with 8 ports available?)
next prev parent reply other threads:[~2008-05-25 19:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-25 12:03 Marvell 88SX7042 [4 Port SATA PCI-Express x4] Support/Questions Justin Piszcz
2008-05-25 17:47 ` Mark Lord
2008-05-25 19:43 ` Andre Tomt [this message]
2008-05-27 0:34 ` Grant Grundler
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=4839C160.6010409@tomt.net \
--to=andre@tomt.net \
--cc=jeff@garzik.org \
--cc=jpiszcz@lucidpixels.com \
--cc=liml@rtr.ca \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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;
as well as URLs for NNTP newsgroup(s).