From: "Al Boldi" <a1426z@gawab.com>
To: "'André Tomt'" <andre@tomt.net>
Cc: 'Bartlomiej Zolnierkiewicz' <bzolnier@gmail.com>,
'Ondrej Zary' <linux@rainbow-software.org>,
'Linus Torvalds' <torvalds@osdl.org>,
linux-ide@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: IOWAIT block layer problem
Date: Tue, 5 Jul 2005 06:43:33 +0300 [thread overview]
Message-ID: <200507050343.GAA26158@raad.intranet> (raw)
In-Reply-To: <42C9C56D.7040701@tomt.net>
André Tomt wrote: {
>>>>On 7/4/05, Al Boldi <a1426z@gawab.com> wrote:
>>>>Hdparm -tT gives 38mb/s in 2.4.31
>>>>Cat /dev/hda > /dev/null gives 2% user 33% sys 65% idle
>>>>
>>>>Hdparm -tT gives 28mb/s in 2.6.12
>>>>Cat /dev/hda > /dev/null gives 2% user 25% sys 0% idle 73% IOWAIT
The "hdparm doesn't get as high scores as in 2.4" is a old discussed to
death "problem" on LKML. So far nobody has been able to show it affects
anything but that pretty useless quasi-benchmark.
>>>No errors though, only sluggish system.
Really sluggish or just "benchmark-sluggish"?
If the former, try selecting a different IO elevator/sheduler.
> When you compare 2.4.31 with 2.6.12 don't you see this problem on your
> machine?
> If you have a fast system the slowdown won't show, but your IOWAIT
> will be higher anyway!
Nothing wrong with 73% iowait
Beware 2.4 didn't export that statistic at all to userspace, so 0% iowait
gets reported from most 2.6-ready reporting tools on 2.4.
}
1. hdparm only gives you an indicator.
2. Really sluggish, as in unresponsive to commands.
3. Tried all IO elevators/shedulers to no avail.
4. In 2.4 IOWAIT is added to sys, as in 8% IOWAIT.
next prev parent reply other threads:[~2005-07-05 3:44 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-03 16:52 [git patches] IDE update Bartlomiej Zolnierkiewicz
2005-07-04 12:01 ` Al Boldi
2005-07-04 12:30 ` Bartlomiej Zolnierkiewicz
2005-07-04 15:30 ` Al Boldi
2005-07-04 15:41 ` Bartlomiej Zolnierkiewicz
2005-07-04 17:06 ` Al Boldi
2005-07-04 17:38 ` Ondrej Zary
2005-07-04 19:51 ` Bartlomiej Zolnierkiewicz
2005-07-04 20:32 ` Al Boldi
2005-07-04 20:47 ` Bartlomiej Zolnierkiewicz
2005-07-04 23:25 ` André Tomt
2005-07-05 3:43 ` Al Boldi [this message]
2005-07-05 10:01 ` Ondrej Zary
2005-07-05 10:14 ` Jens Axboe
2005-07-05 10:19 ` Ondrej Zary
2005-07-05 10:42 ` Jens Axboe
2005-07-05 12:35 ` Ondrej Zary
2005-07-05 12:51 ` Jens Axboe
2005-07-05 13:02 ` Ondrej Zary
2005-07-05 13:11 ` Jens Axboe
2005-07-05 15:51 ` Ondrej Zary
2005-07-05 14:21 ` Jens Axboe
2005-07-05 15:00 ` Ondrej Zary
2005-07-05 19:18 ` Jens Axboe
2005-07-05 19:25 ` Jens Axboe
2005-07-05 21:36 ` Ondrej Zary
2005-07-05 17:27 ` Linus Torvalds
2005-07-05 19:14 ` Jens Axboe
2005-07-05 21:39 ` Ondrej Zary
2005-07-11 14:21 ` Alan Cox
2005-07-06 0:35 ` Grant Coady
2005-07-06 0:51 ` Linus Torvalds
2005-07-06 3:26 ` Al Boldi
2005-07-06 4:56 ` Grant Coady
2005-07-06 5:22 ` Linus Torvalds
2005-07-08 8:48 ` Jens Axboe
2005-07-08 10:20 ` Ingo Molnar
2005-07-08 11:45 ` Jens Axboe
2005-07-07 22:32 ` Mark Lord
2005-07-08 0:06 ` Grant Coady
2005-07-08 11:37 ` Erik Slagter
2005-07-06 20:56 ` Bill Davidsen
2005-07-07 13:47 ` Ondrej Zary
2005-07-07 13:48 ` Bartlomiej Zolnierkiewicz
2005-07-07 19:34 ` Bill Davidsen
2005-07-05 2:47 ` Jeff Garzik
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=200507050343.GAA26158@raad.intranet \
--to=a1426z@gawab.com \
--cc=andre@tomt.net \
--cc=bzolnier@gmail.com \
--cc=linux-ide@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=torvalds@osdl.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