Theo Baumgartner wrote: > Hello > > I've got a sil3124 card which doesn't seem to use the full speed of my drives. > > ------------------------------------------------------------------------------------------------------------------- > ata1: SATA max UDMA/100 cmd 0xe0850000 ctl 0x00000000 bmdma 0x00000000 irq 17 > ata2: SATA max UDMA/100 cmd 0xe0852000 ctl 0x00000000 bmdma 0x00000000 irq 17 > ata3: SATA max UDMA/100 cmd 0xe0854000 ctl 0x00000000 bmdma 0x00000000 irq 17 > ata4: SATA max UDMA/100 cmd 0xe0856000 ctl 0x00000000 bmdma 0x00000000 irq 17 > scsi0 : sata_sil24 > ata1: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > ata1.00: ATA-7: WDC WD3200YS-01PGB0, 21.00M21, max UDMA/133 > ata1.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 1) > ata1.00: configured for UDMA/100 > scsi1 : sata_sil24 > ata2: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > ata2.00: ATA-7: WDC WD3200YS-01PGB0, 21.00M21, max UDMA/133 > ata2.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 1) > ata2.00: configured for UDMA/100 > scsi2 : sata_sil24 > ata3: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > ata3.00: ATA-7: WDC WD3200YS-01PGB0, 21.00M21, max UDMA/133 > ata3.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 1) > ata3.00: configured for UDMA/100 > scsi3 : sata_sil24 > ata4: SATA link up 3.0 Gbps (SStatus 123 SControl 300) > ata4.00: ATA-7: WDC WD3200YS-01PGB0, 21.00M21, max UDMA/133 > ata4.00: 625142448 sectors, multi 16: LBA48 NCQ (depth 1) > ata4.00: configured for UDMA/100 > ------------------------------------------------------------------------------------------------------------------- > > Why does it tell "max UDMA/133" but then just uses UDMA/100? That's the controller mask being applied. UDMA mode doesn't matter for native SATA devices at all, so just ignore it. > and what about the NCQ depth 1? That's the harddrive reporting NCQ max depth of 1. Interesting. Care to post the result of "hdparm -I /dev/sda"? -- tejun - To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
