From: "Doug Smythies" <dsmythies@telus.net>
To: "'Jonathan Nieder'" <jrnieder@gmail.com>
Cc: "'Anders Boström'" <anders@netinsight.net>,
linux-kernel@vger.kernel.org,
"'Lesław Kopeć'" <leslaw.kopec@nasza-klasa.pl>,
"'Aman Gupta'" <aman@tmm1.net>,
"'Peter Zijlstra'" <a.p.zijlstra@chello.nl>,
"'Thomas Gleixner'" <tglx@linutronix.de>,
"'Charles Wang'" <muming.wq@gmail.com>,
"Doug Smythies" <dsmythies@telus.net>
Subject: RE: [3.2.16 -> 3.2.17 regression] High reported CPU load when idle
Date: Mon, 11 Jun 2012 23:12:04 -0700 [thread overview]
Message-ID: <003901cd4862$57435dc0$05ca1940$@net> (raw)
In-Reply-To: <20120610174939.GA456@burratino>
[-- Attachment #1: Type: text/plain, Size: 1749 bytes --]
>> On 2012.06.08 10:01 Doug Smythies wrote:
> On 2012.06.10 10:50 Jonathan Nieder wrote:
>> By the way, I found and tested
>> 5aaa0b7a2ed5b12692c9ffb5222182bd558d3146
>> It is similar (minimally tested).
Which a day later was included in kernel 3.5 RC2, which I also tested for
low load conditions only (i.e. in case I made some mistake with my manual
back edit.)
Herein, the abbreviation "5aaa" means Kernel 3.5 RC2 with
5aaa0b7a2ed5b12692c9ffb5222182bd558d3146 and its predecessors.
> Another load average related patch is being discussed (not meant
> particularly to address the too-low load case, just mentioning it FYI):
> sched: Folding nohz load accounting more accurate
> [...]
> From [*].
> [*] http://thread.gmane.org/gmane.linux.kernel/1310462
Jonathan: Thanks for the reference.
I also back edited that patch (by Charles Wang) into my working Kernel.
Herein, the abbreviation "Wang" means my working Kernel (3.2.0-24.39
(Ubuntu reference)) with these back edits: The above referenced patch by
Charles Wang; 5aaa0b7a2ed5b12692c9ffb5222182bd558d3146;
556061b00c9f2fd6a5524b6bde823ef12f299ecf;
and c308b56b5398779cd3da0f62ab26b0453494c3d4.
The abbreviation "c308" means my working kernel with only
c308b56b5398779cd3da0f62ab26b0453494c3d4.
The abbreviation "Control" means a tick based kernel compiled with
CONFIG_NO_HZ=no.
See the attached PNG file (and or [1]) for relatively low load test
results.
Summary:
"c308" and "5aaa" are the same, with reported load averages higher than
actual.
"Wang" is worse, with reported load averages in error even higher.
"Control" tends to track, but sometimes reported load averages are
somewhat low.
[1] http://www.smythies.com/~doug/network/load_average/wang_compare.png
Doug Smythies
[-- Attachment #2: wang_compare.png --]
[-- Type: image/png, Size: 78127 bytes --]
prev parent reply other threads:[~2012-06-12 6:12 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20120523.144057.899060240318474097.anders@netinsight.net>
2012-05-23 21:53 ` [3.2.16 -> 3.2.17 regression] High reported CPU load when idle Jonathan Nieder
2012-05-24 21:45 ` Jonathan Nieder
2012-05-30 14:30 ` Doug Smythies
2012-05-30 14:54 ` Anders Boström
2012-06-05 15:35 ` Lesław Kopeć
2012-06-08 17:01 ` Doug Smythies
2012-06-10 17:49 ` Jonathan Nieder
2012-06-12 6:12 ` Doug Smythies [this message]
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='003901cd4862$57435dc0$05ca1940$@net' \
--to=dsmythies@telus.net \
--cc=a.p.zijlstra@chello.nl \
--cc=aman@tmm1.net \
--cc=anders@netinsight.net \
--cc=jrnieder@gmail.com \
--cc=leslaw.kopec@nasza-klasa.pl \
--cc=linux-kernel@vger.kernel.org \
--cc=muming.wq@gmail.com \
--cc=tglx@linutronix.de \
/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