https://bugzilla.kernel.org/show_bug.cgi?id=3094 --- Comment #30 from Artem S. Tashkinov <t.artem@xxxxxxxxxxxx> 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.-- To unsubscribe from this list: send the line "unsubscribe linux-ide" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
