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 09:09:09 GMT	[thread overview]
Message-ID: <201005200909.o4K9999s001489@demeter.kernel.org> (raw)
In-Reply-To: <bug-3094-11633@https.bugzilla.kernel.org/>

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


Tejun Heo <tj@kernel.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |tj@kernel.org




--- Comment #25 from Tejun Heo <tj@kernel.org>  2010-05-20 09:08:51 ---
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.

Zenith88, if Linux grinds your gears that much and makes you angry, go ahead
and use or do something else.  Life is short.  Do something you like and, well,
more importantly to me, don't get in the way of other people at the very least.
 If you wanna actually delve into solving a technical issue, please stay
technical from this point on.

Thanks.

-- 
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  9:09 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 [this message]
2010-05-20 15:49 ` bugzilla-daemon
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=201005200909.o4K9999s001489@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).