From: Sergei Shtylyov <sshtylyov@ru.mvista.com>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-kernel@vger.kernel.org, linux-ide@vger.kernel.org
Subject: Re: Question with AHCI and (UDMA/100 vs. UDMA/133)
Date: Wed, 31 Dec 2008 14:40:59 +0300 [thread overview]
Message-ID: <495B5A4B.5030205@ru.mvista.com> (raw)
In-Reply-To: <alpine.DEB.1.10.0812300651190.11356@p34.internal.lan>
Hello.
Justin Piszcz wrote:
> Do some chipsets (SiI 3132 vs. Intel ICH9) run certain drives at
> UDMA/100 vs. UDMA/133?
Intel ICH chipsets never supported UDMA/133.
> I have several 750GB WD drives (exact make/model) and the ones on the
> intel chipset show up as:
>
> [ 1.407321] ata3.00: ATA-7: WDC WD7500AAKS-00RBA0, 30.04G30, max
> UDMA/133
> [ 1.407409] ata3.00: 1465149168 sectors, multi 0: LBA48 NCQ (depth
> 31/32)
> [ 1.408300] ata3.00: configured for UDMA/133
I'm *very* surprised to see that on ICH9. Oh wait, that's SATA
controller, not PATA! Then I don't know...
> The ones on the SiI 3132 chipset show up as:
>
> [ 9.604413] ata11: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> [ 9.619024] ata11.00: ATA-7: WDC WD7500AAKS-00RBA0, 30.04G30, max
> UDMA/133
> [ 9.619111] ata11.00: 1465149168 sectors, multi 16: LBA48 NCQ
> (depth 31/32)
> [ 9.620029] ata11.00: configured for UDMA/100
>
> If they are both 3.0 Gbps, are they both the same speed even though
> one is configured for a slower speed than the other?
I'd think so.
> Or is it the case that the SiI 3132 does not support AHCI and that is
> the reason for the difference? Does it make any difference in
> performance?
Hardly -- if these are true SATA controllers.
MBR, Sergei
prev parent reply other threads:[~2008-12-31 11:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-30 12:25 Question with AHCI and (UDMA/100 vs. UDMA/133) Justin Piszcz
2008-12-30 17:34 ` Robert Hancock
2008-12-30 17:34 ` Robert Hancock
2008-12-31 11:40 ` Sergei Shtylyov [this message]
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=495B5A4B.5030205@ru.mvista.com \
--to=sshtylyov@ru.mvista.com \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@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.