linux-ide.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: bugzilla-daemon@bugzilla.kernel.org
To: linux-ide@vger.kernel.org
Subject: [Bug 3094] POOR I/O perfomance on VIA chipsets
Date: Thu, 20 May 2010 15:49:42 GMT	[thread overview]
Message-ID: <201005201549.o4KFngro010990@demeter.kernel.org> (raw)
In-Reply-To: <bug-3094-11633@https.bugzilla.kernel.org/>

https://bugzilla.kernel.org/show_bug.cgi?id=3094





--- Comment #26 from Artem S. Tashkinov <t.artem@mailcity.com>  2010-05-20 15:49:11 ---
(In reply to comment #25)
> Artem, if some tool is showing iowait as cpu time consumed, that tool needs to
> be fixed.  The kernel is simply exporting what it's doing.  The presentation is
> upto system monitoring tools.  I recall lots of tools which kind of gave the
> wrong signals years ago but these days I don't recall seeing such things too
> often.  There always is a problem with people who are fixated on weird stuff
> but I don't think it's possible to satisfy everyone.  We can't show cached as
> free memory for people who claim the kernel is wasting all memory, right? 
> That's a very bad solution for a virtually non-existing problem.
> 

Are you aware of any other tools except htop and top (from procps package)?
They both show IO wait as CPU load.

What about kernel itself? load average to my knowledge is statistical data
exported by kernel itself and according to your words this data can be trusted,
or I am missing something here?  Why do we have this kind of situation (I need
to quote myself here):

(In reply to comment #21)
> 
> `cat /dev/sda > /dev/null` results in load average rapidly climbing to 1.32 and
> counting on my PC, that's just insane and wrong.

I've just rerun this test for 10 minutes and load average climbed to 2.14 on my
4 cores SMP system (2 real cores, 2 HT's). That means that intensive I/O
operations consume a mind boggling 50% of my CPU power and mind that I have a
really fast CPU (3.4GHz Intel Core i5).

On this issue there are two almost identical bugs filed by me, bug 14531 and
bug 14648 but it seems like no one cares.

-- 
Configure bugmail: https://bugzilla.kernel.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are watching the assignee of the bug.

  parent reply	other threads:[~2010-05-20 15:49 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-3094-11633@https.bugzilla.kernel.org/>
2010-05-18 23:33 ` [Bug 3094] POOR I/O perfomance on VIA chipsets bugzilla-daemon
2010-05-18 23:38 ` bugzilla-daemon
2010-05-18 23:44 ` bugzilla-daemon
2010-05-19  0:47 ` bugzilla-daemon
2010-05-19  0:51 ` bugzilla-daemon
2010-05-19  0:59 ` bugzilla-daemon
2010-05-19  1:12 ` bugzilla-daemon
2010-05-19  1:14 ` bugzilla-daemon
2010-05-19  3:08 ` bugzilla-daemon
2010-05-19  6:29 ` bugzilla-daemon
2010-05-19 11:16 ` bugzilla-daemon
2010-05-19 17:18 ` bugzilla-daemon
2010-05-19 20:53 ` bugzilla-daemon
2010-05-19 23:11 ` bugzilla-daemon
2010-05-20  5:28 ` bugzilla-daemon
2010-05-20  9:09 ` bugzilla-daemon
2010-05-20 15:49 ` bugzilla-daemon [this message]
2010-05-20 16:14 ` bugzilla-daemon
2010-05-20 16:56 ` bugzilla-daemon
2010-05-20 17:07 ` bugzilla-daemon
2010-05-20 17:43 ` bugzilla-daemon
2010-05-20 18:51 ` bugzilla-daemon
2010-05-20 19:02 ` bugzilla-daemon
2010-05-20 23:45 ` bugzilla-daemon
2010-05-21  5:48 ` bugzilla-daemon

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=201005201549.o4KFngro010990@demeter.kernel.org \
    --to=bugzilla-daemon@bugzilla.kernel.org \
    --cc=linux-ide@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).