From: Paolo Ornati <ornati@lycos.it>
To: Ed Sweetman <ed.sweetman@wmich.edu>
Cc: William Lee Irwin III <wli@holomorphy.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.6.1-rc1 [resend]
Date: Wed, 31 Dec 2003 19:03:56 +0100 [thread overview]
Message-ID: <200312311903.56832.ornati@lycos.it> (raw)
In-Reply-To: <3FF2F9FE.2000403@wmich.edu>
On Wednesday 31 December 2003 17:31, Ed Sweetman wrote:
> Paolo Ornati wrote:
> > On Wednesday 31 December 2003 16:20, you wrote:
> >>On Wednesday 31 December 2003 16:06, you wrote:
> >>>>What io scheduler are you using? Or, could you post /var/log/dmesg?
> >>
> >>On Wed, Dec 31, 2003 at 04:19:27PM +0100, Paolo Ornati wrote:
> >>>"dmesg" and "config" attached.
> >>
> >>Could you try this with elevator=deadline?
> >
> > ok, I have just tried...
> > I don't see any big difference.
>
> Wasn't it mentioned in another thread related to a drop in ide
> performance that there is possibly some bug in the ide code that ends up
> requiring you to set the readahead on all your devices to see the max
> performance of any one?
>
> set all the readaheads of all your ide devices to 8192 You should see
> the best peformance doing this.
No, I have just try it but I don't see any changes.
My question is about a strange change of "behaviour" in IDE performance
changing readahead.
Here I report a new thing that I've noticed today:
Kernel 2.6.0:
o readahead up to 224:
when I run "hdparm -t /dev/hda" the HD LED light up... and after a while
light down
o readahead > 224:
running "hdparm" the HD LED starts blinking... and then light down
The best performance are riched with values between 128 and 224 --> IOW when
the HD led starts blinking the performance diminish...
Kernel 2.6.1-rc1:
the HD LED starts to blink with readahead = 16 !!!
Why?
BYE
--
Paolo Ornati
Linux v2.6.0
next prev parent reply other threads:[~2003-12-31 18:04 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-12-31 8:36 2.6.1-rc1 Linus Torvalds
2003-12-31 8:47 ` 2.6.1-rc1 Mike Fedyk
2003-12-31 10:05 ` 2.6.1-rc1 Tomas Szepe
2003-12-31 12:12 ` 2.6.1-rc1 Jeff Garzik
2003-12-31 15:00 ` 2.6.1-rc1 [resend] Paolo Ornati
2003-12-31 15:06 ` William Lee Irwin III
2003-12-31 15:19 ` Paolo Ornati
2003-12-31 15:20 ` William Lee Irwin III
2003-12-31 15:45 ` Paolo Ornati
2003-12-31 16:31 ` Ed Sweetman
2003-12-31 18:03 ` Paolo Ornati [this message]
2004-01-01 9:12 ` 2.6.1-rc1 Andreas Unterkircher
2004-01-01 18:12 ` 2.6.1-rc1 Paolo Ornati
2004-01-02 4:51 ` 2.6.1-rc1 with JP106 keyboard Go Taniguchi
2004-01-02 5:46 ` Go Taniguchi
2004-01-02 13:20 ` Vojtech Pavlik
2004-01-02 13:17 ` Vojtech Pavlik
2004-01-02 19:01 ` Go Taniguchi
2004-01-02 20:10 ` Vojtech Pavlik
2004-01-03 5:54 ` Go Taniguchi
2004-01-06 18:33 ` 2.6.1-rc1: SCSI: `TIMEOUT' redefined Adrian Bunk
2004-01-06 22:40 ` [PATCH] " Patrick Mansfield
2004-01-06 22:40 ` Andrew Morton
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=200312311903.56832.ornati@lycos.it \
--to=ornati@lycos.it \
--cc=ed.sweetman@wmich.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=wli@holomorphy.com \
/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.