From: Mike Dresser <mdresser_l@windsormachine.com>
To: linux-kernel@vger.kernel.org
Subject: Re: Disk performance degradation
Date: Wed, 30 Jul 2003 17:02:47 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.56.0307301658030.30842@router.windsormachine.com> (raw)
In-Reply-To: <3F26A5E2.4070701@aros.net>
On Tue, 29 Jul 2003, Lou Langholtz wrote:
> Anyone want to field why we aren't we just setting the default to 512 so
> users don't need to adjust this? I'm sure there's a good reason... I'd
> just like to know what it is ;-)
mike:~# hdparm -a 512 /dev/hda
/dev/hda:
setting fs readahead to 512
BLKRASET failed: Invalid argument
readahead = 8 (on)
mike:~# hdparm -a 255 /dev/hda
/dev/hda:
setting fs readahead to 255
readahead = 255 (on)
mike:~# hdparm -a 256 /dev/hda
/dev/hda:
setting fs readahead to 256
BLKRASET failed: Invalid argument
readahead = 255 (on)
Probably for reasons like that. For some reason, I can't set my ICH4
based controller(ASUS P4B533) and Quantum Fireball AS40.0 to more than
255. Kernel is 2.4.21
Or I'm missing more of this thread than I thought and I'm completely off
topic here!
(i'm guessing the latter)
Mike
next prev parent reply other threads:[~2003-07-30 21:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-29 16:21 Disk performance degradation Voluspa
2003-07-29 16:50 ` Lou Langholtz
2003-07-30 4:17 ` Voicu Liviu
2003-07-30 21:02 ` Mike Dresser [this message]
2003-07-31 8:35 ` Måns Rullgård
2003-07-31 14:00 ` Mike Dresser
2003-07-31 21:15 ` Andrew Morton
2003-07-31 22:17 ` Bartlomiej Zolnierkiewicz
2003-07-30 8:50 ` Stefano Rivoir
2003-07-30 10:55 ` Andrew Morton
2003-07-30 16:06 ` Stefano Rivoir
2003-07-30 18:44 ` Andrew Morton
2003-07-31 0:21 ` Rahul Karnik
2003-07-31 6:59 ` Stefano Rivoir
2003-07-31 7:16 ` Andrew Morton
-- strict thread matches above, loose matches on Subject: below --
2003-07-30 11:43 Frederick, Fabian
2003-07-29 12:00 Stefano Rivoir
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=Pine.LNX.4.56.0307301658030.30842@router.windsormachine.com \
--to=mdresser_l@windsormachine.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;
as well as URLs for NNTP newsgroup(s).