From: Andreas Hartmann <andihartmann@freenet.de>
To: Bill Davidsen <davidsen@tmr.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.4 : 100% CPU use on EIDE disk operarion, VIA chipset
Date: Sun, 04 Apr 2004 10:07:02 +0200 [thread overview]
Message-ID: <406FC226.5090802@A8bb8.a.pppool.de> (raw)
In-Reply-To: <fa.idlmgtf.1pluljl@ifi.uio.no>
Bill Davidsen wrote:
> Andreas Hartmann wrote:
>> This is what top says during cp of 512MB-file:
>> Cpu(s): 2.0% us, 8.3% sy, 0.0% ni, 0.0% id, 89.0% wa, 0.7% hi,
>> 0.0% si
>>
>> New is "wa", what probably means "wait". This value is very high as long
>> as the HD is writing or reading datas:
>>
>> cp dummy /dev/null
>> produces this top-line:
>> Cpu(s): 3.0% us, 5.3% sy, 0.0% ni, 0.0% id, 91.0% wa, 0.7% hi,
>> 0.0% si
>
> Yes "wa" is not intuitive, some other operating systems use "wio" for
> "wait i/o" time. As noted in the other thread, you can try the deadline
> elevator or increased readahead for your load.
If the processor and the kernel could do other things during wa, like
compiling e.g., it would be no problem. But it seems to be, that this is
not possible. Or did I oversee something?
Regards,
Andreas Hartmann
next parent reply other threads:[~2004-04-04 8:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fa.g80v5s8.b2ofhi@ifi.uio.no>
[not found] ` <fa.idlmgtf.1pluljl@ifi.uio.no>
2004-04-04 8:07 ` Andreas Hartmann [this message]
2004-04-05 2:12 ` 2.6.4 : 100% CPU use on EIDE disk operarion, VIA chipset Bill Davidsen
[not found] ` <fa.ljb660n.d2ofa9@ifi.uio.no>
2004-04-04 8:24 ` Andreas Hartmann
2004-04-04 19:57 ` Mikhail Ramendik
2004-04-05 2:14 ` Bill Davidsen
[not found] <fa.ld6rcgc.1lhmd9q@ifi.uio.no>
2004-04-03 11:24 ` Andreas Hartmann
2004-04-03 12:51 ` Bill Davidsen
2004-04-03 14:12 ` Mikhail Ramendik
2004-04-04 8:02 ` Mikhail Ramendik
2004-04-02 21:54 Mikhail Ramendik
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=406FC226.5090802@A8bb8.a.pppool.de \
--to=andihartmann@freenet.de \
--cc=davidsen@tmr.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