From: Mark Lord <liml@rtr.ca>
To: Krzysztof Oledzki <olel@ans.pl>
Cc: Mark Lord <lkml@rtr.ca>, Jeff Garzik <jgarzik@pobox.com>,
linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: SATA speed. Should be 150 or 133?
Date: Fri, 24 Jun 2005 11:35:42 -0400 [thread overview]
Message-ID: <42BC284E.7050202@rtr.ca> (raw)
In-Reply-To: <Pine.LNX.4.62.0506241127210.3016@bizon.gios.gov.pl>
>> True SATA drives ignore the "transfer speed",
>> as it really is meaningless and does not apply.
>
> So, am I the the only person confused by this message? ;)
> There is "SATA max UDMA/133" not "PATA max UDMA/133".
No, it really is as confusing as it sounds!
The drive is SATA, but the transfer speed gunk only
applies to the internal "PATA" portion of the drive,
which communicates to the built-in SATA bridge chip
of the same drive, which in turn presents a pure SATA
interface to the host computer.
> Oh, so how to check true (current) speed?
Same as always: hdparm -I /dev/sd?
(requires the libata-dev "passthru" patch
recently reposted here by Jeff Garzik).
cheers
next prev parent reply other threads:[~2005-06-24 15:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-23 23:47 SATA speed. Should be 150 or 133? Krzysztof Oledzki
2005-06-24 3:08 ` Mark Lord
2005-06-24 9:33 ` Krzysztof Oledzki
2005-06-24 15:35 ` Mark Lord [this message]
2005-06-24 18:35 ` Krzysztof Oledzki
2005-06-26 1:57 ` Mark Lord
2005-06-26 10:31 ` Krzysztof Oledzki
2005-06-26 13:59 ` Jeff Garzik
2005-06-26 14:14 ` Krzysztof Oledzki
2005-06-26 17:08 ` Jeff Garzik
2005-06-26 18:44 ` Stefan Smietanowski
2005-06-27 20:53 ` Mark Lord
2005-06-27 20:50 ` Mark Lord
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=42BC284E.7050202@rtr.ca \
--to=liml@rtr.ca \
--cc=jgarzik@pobox.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkml@rtr.ca \
--cc=olel@ans.pl \
/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).