All of lore.kernel.org
 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 17:43:02 GMT	[thread overview]
Message-ID: <201005201743.o4KHh2AO014801@demeter.kernel.org> (raw)
In-Reply-To: <bug-3094-11633@https.bugzilla.kernel.org/>

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





--- Comment #30 from Artem S. Tashkinov <t.artem@mailcity.com>  2010-05-20 17:42:59 ---
In the second part of my message I referred to top/htop output which clearly
shows that IO wait is treated like it is _real_ CPU usage but you just ignored
it and now

(In reply to comment #29)
> I don't think this is going anywhere and am fairly sure that further bug
> reports on the subject won't lead anywhere.
> 
> Let's meet again in a more productive discussion.  Thanks.

you sound like "even though most sane people trust their eyes, in Linux you
should not trust your eyes, everything is so complicated we don't even have
utilities which can show real CPU usage".

And until we have such utilities and metrics which allow to instantly _see_ and
_not_ deduct real CPU usage people _will_ keep on bitching that Linux is broken
with my motherboard/chipset/HDD Linux because IO wait OR Linux gobbles down my
precious CPU cycles.

Just run Windows and see how easier it's to _see_ whether system is busy or
occupied. In Linux everything is such a way no layman (except kernel
developers) can really understand.

If you insist that everything is just fine and works correctly as intended I
have to resign and keep silent from now on and realize that Linux is only meant
for über geeks.

-- 
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 17:43 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
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 [this message]
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=201005201743.o4KHh2AO014801@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.