From: Samuel Flory <sflory@rackable.com>
To: Herbert Poetzl <herbert@13thfloor.at>
Cc: "K. Hampf" <khampf@users.sourceforge.net>, linux-kernel@vger.kernel.org
Subject: Re: Verified IDE performance issues in kernels newer than 2.4.20
Date: Wed, 03 Sep 2003 16:54:20 -0700 [thread overview]
Message-ID: <3F567F2C.3040707@rackable.com> (raw)
In-Reply-To: <20030903234932.GA15327@DUK2.13thfloor.at>
Herbert Poetzl wrote:
>On Thu, Sep 04, 2003 at 02:31:10AM +0300, K. Hampf wrote:
>
>
>>BRIEF:
>>I discovered the 2.4.21 and 2.4.22 kernels give me roughly 15% of the
>>troughput compared to 2.4.20. Anyone working on this?
>>
>>
>
>out of the blue, the following info could be very useful ...
>(for 2.4.20 and 2.4.22 on your systems)
>
>cat /proc/ide/*
>hdparm -i /dev/hd?
>hdparm /dev/hd?
>
>and try to make it available on a webpage
>
>
Also try "hdparm -a 2048 <some device>" before running hdparm. Also
the ide section of dmesg woul dbe handy in addition to the above.
[root@goblin e2fsprogs-1.26]# hdparm -t /dev/hdg
/dev/hdg:
Timing buffered disk reads: 70 MB in 3.04 seconds = 23.03 MB/sec
[root@goblin e2fsprogs-1.26]# hdparm -a 2048 /dev/hdg
/dev/hdg:
setting fs readahead to 2048
readahead = 2048 (on)
[root@goblin e2fsprogs-1.26]# hdparm -t /dev/hdg
/dev/hdg:
Timing buffered disk reads: 122 MB in 3.01 seconds = 40.47 MB/sec
--
Once you have their hardware. Never give it back.
(The First Rule of Hardware Acquisition)
Sam Flory <sflory@rackable.com>
next prev parent reply other threads:[~2003-09-04 0:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-03 23:31 Verified IDE performance issues in kernels newer than 2.4.20 K. Hampf
2003-09-03 23:49 ` Herbert Poetzl
2003-09-03 23:54 ` Samuel Flory [this message]
2003-09-04 12:58 ` K. Hampf
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=3F567F2C.3040707@rackable.com \
--to=sflory@rackable.com \
--cc=herbert@13thfloor.at \
--cc=khampf@users.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox