From: Shaun Savage <savages@savages.net>
To: linux-kernel@vger.kernel.org
Subject: kernel 2.6t9 SATA slower than 2.4.20
Date: Mon, 27 Oct 2003 05:11:08 -0800 [thread overview]
Message-ID: <3F9D196C.9080301@savages.net> (raw)
I have just compiled and installed kernel 2.6t9 on my RH9 / Asus A7N8X
Deluxe. I find the disk access is slower using the 2.6 kernel than the
2.4.20 kernel.
To get it to work for 2.4.20 kernel I have to use
# hdparm -d1 -X88 /dev/hde
then the buffered disk read goes from 1.5M to 55M
On the 2.6 kernel the buffered disk read is only 16M
What do I have to do to increase the disk speed for kernel 2.6t9?
Shaun Savage
next reply other threads:[~2003-10-27 13:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-27 13:11 Shaun Savage [this message]
2003-10-27 13:33 ` kernel 2.6t9 SATA slower than 2.4.20 Ed Tomlinson
2003-10-27 13:43 ` Nuno Silva
2003-10-27 13:53 ` Jeff Garzik
2003-10-27 14:48 ` Arve Knudsen
-- strict thread matches above, loose matches on Subject: below --
2003-10-27 15:56 Shaun Savage
2003-10-27 16:59 ` Jeff Garzik
2003-10-27 17:36 ` Arve Knudsen
2003-10-27 18:15 ` Jeff Garzik
2003-10-27 21:15 ` Arve Knudsen
2003-10-27 22:09 ` Jeff Garzik
2003-10-27 18:08 ` Bob Johnson
2003-10-27 18:17 ` Jeff Garzik
2003-10-28 4:14 ` Shaun Savage
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=3F9D196C.9080301@savages.net \
--to=savages@savages.net \
--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.