From: Jeff Garzik <jgarzik@pobox.com>
To: Sebastian Slota <sebastian@sslota.de>
Cc: linux-raid@vger.kernel.org
Subject: Re: SATA Performance
Date: Fri, 08 Oct 2004 10:48:30 -0400 [thread overview]
Message-ID: <4166A8BE.4060902@pobox.com> (raw)
In-Reply-To: <200410081335.37325.sebastian@sslota.de>
Sebastian Slota wrote:
> libata version 1.02 loaded.
> sata_sil version 0.54
> ACPI: PCI interrupt 0000:03:03.0[A] -> GSI 19 (level, low) -> IRQ 19
> ata1: SATA max UDMA/100 cmd 0xF8B09080 ctl 0xF8B0908A bmdma 0xF8B09000 irq 19
> ata2: SATA max UDMA/100 cmd 0xF8B090C0 ctl 0xF8B090CA bmdma 0xF8B09008 irq 19
> ata3: SATA max UDMA/100 cmd 0xF8B09280 ctl 0xF8B0928A bmdma 0xF8B09200 irq 19
> ata4: SATA max UDMA/100 cmd 0xF8B092C0 ctl 0xF8B092CA bmdma 0xF8B09208 irq 19
> ata1: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003
> 88:207f
> ata1: dev 0 ATA, max UDMA/133, 312581808 sectors: lba48
> ata1(0): applying Seagate errata fix
> ata1: dev 0 configured for UDMA/100
> scsi0 : sata_sil
> ata2: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003
> 88:207f
> ata2: dev 0 ATA, max UDMA/133, 312581808 sectors: lba48
> ata2(0): applying Seagate errata fix
> ata2: dev 0 configured for UDMA/100
> scsi1 : sata_sil
> ata3: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003
> 88:207f
> ata3: dev 0 ATA, max UDMA/133, 312581808 sectors: lba48
> ata3(0): applying Seagate errata fix
> ata3: dev 0 configured for UDMA/100
> scsi2 : sata_sil
> ata4: dev 0 cfg 49:2f00 82:346b 83:7d01 84:4003 85:3469 86:3c01 87:4003
> 88:207f
> ata4: dev 0 ATA, max UDMA/133, 312581808 sectors: lba48
> ata4(0): applying Seagate errata fix
> ata4: dev 0 configured for UDMA/100
The "applying Seagate errata fix" locks each request to a small size,
which kills performance basically.
Jeff
prev parent reply other threads:[~2004-10-08 14:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-08 11:35 SATA Performance Sebastian Slota
2004-10-08 14:48 ` Jeff Garzik [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=4166A8BE.4060902@pobox.com \
--to=jgarzik@pobox.com \
--cc=linux-raid@vger.kernel.org \
--cc=sebastian@sslota.de \
/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.