From: Tejun Heo <tj@kernel.org>
To: Pierre Ossman <drzeus-list@drzeus.cx>
Cc: Jeff Garzik <jgarzik@pobox.com>, linux-ide@vger.kernel.org
Subject: Re: How to determine performance bottleneck?
Date: Tue, 14 Oct 2008 14:37:41 +0900 [thread overview]
Message-ID: <48F43025.8050705@kernel.org> (raw)
In-Reply-To: <20081014070728.386a9cf2@mjolnir.drzeus.cx>
Pierre Ossman wrote:
> On Tue, 14 Oct 2008 08:25:22 +0900
> Tejun Heo <tj@kernel.org> wrote:
>
>> Pierre Ossman wrote:
>>> When I'm accessing a single disk, the bandwidth is 70 - 80 MiB/s. When
>>> I access a second disk, the bandwidth is about 50 MiB/s/disk, and all
>>> five results in 25 MiB/s/disk. In other words, something is limiting
>>> things to about 100 MiB/s. Now the question is what that limiting
>>> factor is.
>>>
>> That's the limit of sil3124/3132. Dunno why but you can't go over that.
>
> Bummer. Is this per port, or is it the PCIe side of the chip that is
> limited to this speed?
I think it's on the host bus side.
> What do the silicon image guys have to say about it?
ISTR they confirmed the problem but I don't remember talking too much
about it.
>> There's 3132-2 chip on the market. Maybe it's worth a try?
>
> Now that model number was not something that was easily found on
> google, nor on silicon image's website. Know of any boards with that
> chip?
Somebody wrote me an email about it. Looking up... eh.. can't find. Sorry.
--
tejun
next prev parent reply other threads:[~2008-10-14 5:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-13 18:28 How to determine performance bottleneck? Pierre Ossman
2008-10-13 20:12 ` Alan Cox
2008-10-14 5:22 ` Pierre Ossman
2008-10-13 23:25 ` Tejun Heo
2008-10-14 5:07 ` Pierre Ossman
2008-10-14 5:37 ` Tejun Heo [this message]
2008-10-14 6:03 ` Pierre Ossman
2008-10-14 6:12 ` Tejun Heo
2008-10-14 6:59 ` Pierre Ossman
2008-10-14 7:00 ` Tejun Heo
2008-10-14 16:29 ` Grant Grundler
2008-10-14 17:19 ` Tejun Heo
2008-10-14 17:43 ` 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=48F43025.8050705@kernel.org \
--to=tj@kernel.org \
--cc=drzeus-list@drzeus.cx \
--cc=jgarzik@pobox.com \
--cc=linux-ide@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).