From: "Andrew Lyon" <andrew.lyon@gmail.com>
To: linux-kernel@vger.kernel.org
Subject: JMicron 20360/20363 AHCI Controller much slower with 2.6.18
Date: Thu, 21 Sep 2006 09:04:05 +0100 [thread overview]
Message-ID: <f4527be0609210104p3c6c4933ke77d8372f6dd3848@mail.gmail.com> (raw)
Hi,
I have a Gigabyte GA_965P_DS3 with Core 2 Duo CPU, wd raptor connected
to onboard JMicron 20360/20363 AHCI Controller, with 2.6.18 the drive
is very slow:
beast ~ # uname -a
Linux beast 2.6.18 #1 SMP Wed Sep 20 15:04:24 BST 2006 i686 Intel(R) Core(TM)2 C
PU 6600 @ 2.40GHz GNU/Linux
beast ~ # hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 100 MB in 3.02 seconds = 33.10 MB/sec
beast ~ # dmesg | grep sda
SCSI device sda: 145223999 512-byte hdwr sectors (74355 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 145223999 512-byte hdwr sectors (74355 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 >
sd 0:0:0:0: Attached scsi disk sda
EXT3 FS on sda2, internal journal
EXT3 FS on sda5, internal journal
EXT3 FS on sda6, internal journal
EXT3 FS on sda7, internal journal
EXT3 FS on sda8, internal journal
Adding 4000176k swap on /dev/sda3. Priority:-1 extents:1 across:4000176k
beast ~ # dmesg | grep ata1
ata1: SATA max UDMA/133 cmd 0xF8CD4100 ctl 0x0 bmdma 0x0 irq 17
ata1: SATA link up 1.5 Gbps (SStatus 113 SControl 300)
ata1.00: ATA-7, max UDMA/133, 145223999 sectors: LBA48 NCQ (depth 31/32)
ata1.00: ata1: dev 0 multi count 16
ata1.00: configured for UDMA/133
with 2.6.17 the drive is more than twice as fast:
beast ~ # uname -a
Linux beast 2.6.17 #6 SMP Sat Sep 2 11:39:53 GMT 2006 i686 Intel(R)
Core(TM)2 CPU 6600 @ 2.40GHz GNU/Linux
beast ~ # hdparm -t /dev/sda
/dev/sda:
Timing buffered disk reads: 250 MB in 3.01 seconds = 82.95 MB/sec
beast ~ # dmesg | grep sda
SCSI device sda: 145223999 512-byte hdwr sectors (74355 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
SCSI device sda: 145223999 512-byte hdwr sectors (74355 MB)
sda: Write Protect is off
sda: Mode Sense: 00 3a 00 00
SCSI device sda: drive cache: write back
sda: sda1 sda2 sda3 sda4 < sda5 sda6 sda7 sda8 sda9 >
sd 0:0:0:0: Attached scsi disk sda
EXT3 FS on sda2, internal journal
EXT3 FS on sda5, internal journal
EXT3 FS on sda6, internal journal
EXT3 FS on sda7, internal journal
EXT3 FS on sda8, internal journal
Adding 4000176k swap on /dev/sda3. Priority:-1 extents:1 across:4000176k
beast ~ # dmesg | grep ata1
ata1: SATA max UDMA/133 cmd 0xF8CD8100 ctl 0x0 bmdma 0x0 irq 17
ata1: SATA link up 1.5 Gbps (SStatus 113)
ata1: dev 0 cfg 49:2f00 82:746b 83:7f61 84:4023 85:7468 86:3e41 87:4023 88:407f
ata1: dev 0 ATA-7, max UDMA/133, 145223999 sectors: LBA48
ata1: dev 0 configured for UDMA/133
I have other drives connected to onboard piix sata, they perform the
same with 2.6.18 as with 2.6.17, only the jmicron controller is
slower..
I notice that there are messages about NCQ in 2.6.18 dmesg that were
not there with previous versions.
Andy
next reply other threads:[~2006-09-21 8:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-09-21 8:04 Andrew Lyon [this message]
2006-09-21 17:00 ` Tejun Heo
2006-09-21 17:43 ` Jens Axboe
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=f4527be0609210104p3c6c4933ke77d8372f6dd3848@mail.gmail.com \
--to=andrew.lyon@gmail.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®