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 15:12:20 +0900 [thread overview]
Message-ID: <48F43844.9080603@kernel.org> (raw)
In-Reply-To: <20081014080304.65445c51@mjolnir.drzeus.cx>
Pierre Ossman wrote:
> On Tue, 14 Oct 2008 14:37:41 +0900
> Tejun Heo <tj@kernel.org> wrote:
>
>> Pierre Ossman wrote:
>>> 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.
>>
>
> The optimist in me was hoping that this could be a problem that can be
> sidestepped with a clever enough implementation. :)
>
>>>> 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.
>>
>
> Do you remember if that's a new chip designation, or 3132 (rev 02)?
> Just so I know what to keep an eye out for.
Yeah, it had a new designation. Something like 3132-2 (don't confuse it
with 3132 2 ports or 3132 2 ports SATA 2, yeah a lot of 2s there).
--
tejun
next prev parent reply other threads:[~2008-10-14 6:15 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
2008-10-14 6:03 ` Pierre Ossman
2008-10-14 6:12 ` Tejun Heo [this message]
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=48F43844.9080603@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.