[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20120530.165426.1421117300206344483.anders@netinsight.net>
Date: Wed, 30 May 2012 16:54:26 +0200 (CEST)
From: Anders Boström <anders@...insight.net>
To: dsmythies@...us.net
Cc: jrnieder@...il.com, linux-kernel@...r.kernel.org,
leslaw.kopec@...za-klasa.pl, aman@...1.net, a.p.zijlstra@...llo.nl,
tglx@...utronix.de
Subject: Re: [3.2.16 -> 3.2.17 regression] High reported CPU load when idle
>>>>> "DS" == Doug Smythies <dsmythies@...us.net> writes:
DS> This statement: "Starting with 3.2.17-1, the CPU load accounting is broken when the computer is idle. The CPU load is reported as >0.50 when idle. 3.2.16-1 don't suffer from this problem."
DS> In my opinion has the following mistakes:
DS> . The computer is not actually idle. If it was actually idle the reported load average would be 0.
Well, I tested in single user mode, with very few processes running,
mostly init, getty, bash and top (+ a lot of kernel threads). And
3.2.17 reported a load of >0.5 . Under the same conditions 3.2.16
typically reports 0.01 or 0.00 .
DS> . Yes, the new kernel reported load average is high, as detailed in the PNG file or the web notes.
DS> . The older kernel suffers from a different problem, under all other conditions being the same, the reported load average would have been too low.
I don't know if 0.01 is *too* low, but it should be much closer to the
truth than >0.5.
/ Anders
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists