From: Linda Walsh <lkml@tlinx.org>
To: Grant Grundler <grundler@google.com>
Cc: linux-ide@vger.kernel.org
Subject: Re: Port Multiplier access with Sil 3124
Date: Mon, 09 Feb 2009 14:01:37 -0800 [thread overview]
Message-ID: <4990A7C1.5060904@tlinx.org> (raw)
In-Reply-To: <da824cf30902090126p5e031e09q5b93da7a296bc849@mail.gmail.com>
Grant Grundler wrote:
> Linda,
> Please tell us which kernel version you have and include the dmesg
> output. Port multiplier support is generally working in 2.6.26 (and later
> releases) for several drivers. PM support was added after 2.6.20.
---
Sorry. I'm a bit behind the edge at 2.6.27.3 --
but I tried a boot w/2.6.28.3 and didn't see a difference (had to return
to 27.3 as I accidently disabled a different driver and haven't regened it.
>
> Where did you find 350MB/s theoretical?
> Link is 8b10b encoded. So it's 10:1 of bits to bytes conversion of link rate.
> 3Gb/s --> 300MB/s in theory.
---
Yep. Forgot about that... was forgetting about the 2-bits of overhead,
so was using 3Gb/8/(1024*1024) -> 357.6, which I rounded down to 350...
but forgot about the 10/8 encoding (just as I get rid of that conversion
habit from modem days, now I have to remember it as a special case for
SATA...:-) ).
>
> For MB/s, it depends on the SATA controller. Don't expect more then
> 225-235 MB/s per port. At least one sata_sil3124 chip (3126?) is buggy
> and won't do more than 120MB/s read for all ports (170 MB/s write).
> See linux-ide archives for discussion on this.
---
That's horrible! I'd definitely call that a bug. Right now,
the fastest I'm getting on my single ATA's is 70-80MB/s. I could
get that per/ATA port. So 120MB read for 4 SATA ports would be
a giant step backwards (170MB/s write? write faster than read?)
next prev parent reply other threads:[~2009-02-09 22:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-08 20:38 Port Multiplier access with Sil 3124 Linda Walsh
2009-02-09 9:26 ` Grant Grundler
2009-02-09 22:01 ` Linda Walsh [this message]
2009-02-09 14:35 ` Greg Freemyer
2009-02-09 20:09 ` Mark Lord
2009-02-09 22:22 ` Linda Walsh
2009-02-09 23:01 ` Greg Freemyer
2009-02-10 0:15 ` Jeff Garzik
2009-02-10 1:07 ` Linda Walsh
2009-02-10 3:48 ` Jeff Garzik
2009-02-11 2:09 ` Tejun Heo
2009-02-12 4:16 ` Robert Hancock
2009-02-10 3:25 ` Greg Freemyer
2009-02-11 2:12 ` Tejun Heo
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=4990A7C1.5060904@tlinx.org \
--to=lkml@tlinx.org \
--cc=grundler@google.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.