From: Stan Hoeppner <stan@hardwarefreak.com>
To: "Huang, Shane" <Shane.Huang@amd.com>
Cc: James Cloos <cloos@jhcloos.com>,
linux-ide@vger.kernel.org, "Xu, Andiry" <Andiry.Xu@amd.com>,
"Petkov, Borislav" <Borislav.Petkov@amd.com>
Subject: Re: AMD 890GX vs 6Gbps SATA?
Date: Tue, 16 Nov 2010 18:31:12 -0600 [thread overview]
Message-ID: <4CE32250.8050401@hardwarefreak.com> (raw)
In-Reply-To: <1E8B869C0C6913418421A406C094DF7C82DC6C@sshaexmb1.amd.com>
Huang, Shane put forth on 11/16/2010 4:04 AM:
> Since your CAP.ISS is set to 0010(3Gbps), most likely you'll
> have to ask your BIOS vendor to enable 6Gbps in one release.
> Some BIOS vendors may set the max speed to Gen2 to save power.
Unless you have a PMP on the other end of that SATA link with a bunch of
striped drives, or an expensive SSD, you won't notice a performance
difference between 3 Gb/s and 6 Gb/s link speed anyway: no single mech
drive on the planet can come close to pushing 300 MB/s let alone 600.
The fastest 15k SAS drives are peaking at around 200 MB/s IIRC. And
there are few [affordable] SSDs that will saturate a SATA II link, let
alone a SATA III link.
My advice, FWIW, is to simply ignore this, unless you plan on attaching
a device in the near future that can actually exceed 300 MB/s.
Currently the only way to do this is with striped mech drives on a PMP,
or with a $500+ SSD.
--
Stan
next prev parent reply other threads:[~2010-11-17 0:31 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2DEEA3AB13739D45A22ADDB5086AEA0B915107@sshaexmb1.amd.com>
2010-11-15 7:45 ` AMD 890GX vs 6Gbps SATA? Huang, Shane
2010-11-15 16:31 ` James Cloos
2010-11-15 17:02 ` Huang, Shane
2010-11-15 17:11 ` James Cloos
[not found] ` <4CE179B4.4090404@hardwarefreak.com>
[not found] ` <m3fwv2ju9y.fsf@jhcloos.com>
2010-11-15 19:33 ` Stan Hoeppner
2010-11-15 19:40 ` James Cloos
2010-11-16 14:31 ` Mark Lord
2010-11-16 10:04 ` Huang, Shane
2010-11-17 0:31 ` Stan Hoeppner [this message]
2010-11-17 0:38 ` Stan Hoeppner
2010-11-17 2:48 ` Huang, Shane
2010-11-14 17:50 James Cloos
2010-11-15 4:08 ` Jeff Garzik
2010-11-15 16:39 ` James Cloos
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=4CE32250.8050401@hardwarefreak.com \
--to=stan@hardwarefreak.com \
--cc=Andiry.Xu@amd.com \
--cc=Borislav.Petkov@amd.com \
--cc=Shane.Huang@amd.com \
--cc=cloos@jhcloos.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.