https://bugzilla.kernel.org/show_bug.cgi?id=3094 --- Comment #26 from Artem S. Tashkinov <t.artem@xxxxxxxxxxxx> 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. -- 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
