From: Jeff Garzik <jeff@garzik.org>
To: Justin Piszcz <jpiszcz@lucidpixels.com>
Cc: linux-raid@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: Veliciraptor HDD 3.0gbps but UDMA/100 on PCI-e controller?
Date: Thu, 03 Jul 2008 08:50:26 -0400 [thread overview]
Message-ID: <486CCB12.7040205@garzik.org> (raw)
In-Reply-To: <alpine.DEB.1.10.0807030447040.12072@p34.internal.lan>
Justin Piszcz wrote:
> On the motherboard itself (all drives configured for AHCI)
>
> [ 2.360648] ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300)
> [ 2.678244] ata1.00: ATA-8: WDC WD3000GLFS-01F8U0, 03.03V01, max
> UDMA/133
> [ 2.678594] ata1.00: 586072368 sectors, multi 0: LBA48 NCQ (depth 31/32)
> [ 2.684566] ata1.00: configured for UDMA/133
>
> On the PCI-e cards:
>
> [ 16.136568] ata11: SATA link up 3.0 Gbps (SStatus 123 SControl 0)
> [ 16.155682] ata11.00: ATA-8: WDC WD3000GLFS-01F8U0, 03.03V01, max
> UDMA/133
> [ 16.156545] ata11.00: 586072368 sectors, multi 16: LBA48 NCQ (depth
> 31/32)
> [ 16.162949] ata11.00: configured for UDMA/100
>
> How come the PCI-e card configured the drive for UDMA/100 and not UDMA/133?
>
> Perhaps the PCI-e card/driver does not configure/have AHCI
> functionality, or?
>
> The mobo: Intel DG965WH
> The card: 03:00.0 RAID bus controller: Silicon Image, Inc. SiI 3132
> Serial ATA Raid II Controller (rev 01)
You need to show us the full dmesg. We cannot see which controller is
applying limits here.
You need to look at the controller's maximum, as that controls the drive
maximum (pasted from my personal workstation):
scsi0 : ahci
scsi1 : ahci
scsi2 : ahci
scsi3 : ahci
ata1: SATA max UDMA/133 abar m1024@0x90404000 port 0x90404100 irq 507
ata2: SATA max UDMA/133 abar m1024@0x90404000 port 0x90404180 irq 507
ata3: SATA max UDMA/133 abar m1024@0x90404000 port 0x90404200 irq 507
ata4: SATA max UDMA/133 abar m1024@0x90404000 port 0x90404280 irq 507
scsi4 : sata_sil
scsi5 : sata_sil
scsi6 : sata_sil
scsi7 : sata_sil
ata5: SATA max UDMA/100 mmio m1024@0x9000c800 tf 0x9000c880 irq 17
ata6: SATA max UDMA/100 mmio m1024@0x9000c800 tf 0x9000c8c0 irq 17
ata7: SATA max UDMA/100 mmio m1024@0x9000c800 tf 0x9000ca80 irq 17
ata8: SATA max UDMA/100 mmio m1024@0x9000c800 tf 0x9000cac0 irq 17
See the UDMA difference?
Jeff
next prev parent reply other threads:[~2008-07-03 12:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-03 8:51 Veliciraptor HDD 3.0gbps but UDMA/100 on PCI-e controller? Justin Piszcz
2008-07-03 12:50 ` Jeff Garzik [this message]
2008-07-03 13:48 ` Justin Piszcz
2008-07-03 16:19 ` Roger Heflin
2008-07-03 17:02 ` Justin Piszcz
[not found] <fa.Rv78KGguIBjNqcR6d0heXxceZEM@ifi.uio.no>
2008-07-04 4:35 ` Robert Hancock
2008-07-09 14:48 ` Lennart Sorensen
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=486CCB12.7040205@garzik.org \
--to=jeff@garzik.org \
--cc=jpiszcz@lucidpixels.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-raid@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 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).