From: "Lesław Kopeć" <leslaw.kopec@nasza-klasa.pl>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: Peter Zijlstra <peterz@infradead.org>, Aman Gupta <aman@tmm1.net>,
linux-kernel@vger.kernel.org,
Chase Douglas <chase.douglas@canonical.com>,
Damien Wyart <damien.wyart@free.fr>,
Kyle McMartin <kyle@redhat.com>,
Venkatesh Pallipadi <venki@google.com>,
Doug Smythies <dsmythies@telus.net>,
Thomas Gleixner <tglx@linutronix.de>
Subject: Re: Inconsistent load average on tickless kernels
Date: Mon, 23 Apr 2012 18:20:17 +0200 [thread overview]
Message-ID: <4F958141.2000505@nasza-klasa.pl> (raw)
In-Reply-To: <20120417153032.GB21534@burratino>
[-- Attachment #1: Type: text/plain, Size: 1303 bytes --]
On 04/17/2012 05:30 PM, Jonathan Nieder wrote:
>> Looking at results for 2.6.32.55 branch it seems that we're back at
>> 74f5187ac8 patch - the values are almost the same. The difference
>> between NO_HZ and HZ versions is noticeable.
>
> How does 3.0.y + c308b56b53 do? (I ask because the usual flow of
> fixes is mainline -> 3.3.y -> 3.2.y -> 3.0.y -> 2.6.32.y with the
> first three steps happening pretty quickly, so it we can get this
> working on 3.0.y then that would be progress. Also because, like
> 2.6.32.y, 3.0.y is longterm maintained, so it might be useful in the
> meantime.)
It seems that load reported by 3.0.28 with and without c308b56b53 patch
is almost identical to 3.2.12. This might be more clearly visible on a
comparison chart. [1]
2.6.32.55-hz-0f004f5a69 9.88
2.6.32.55-no-hz-74f5187ac8 2.48
2.6.32.55-no-hz-c308b56b53 2.22
3.0.28-hz 10.66
3.0.28-no-hz 0.60
3.0.28-no-hz-c308b56b53 4.09
3.0.28-no-hz-c308b56b53 nohz=off 6.78
3.2.12-hz 10.16
3.2.12-no-hz 0.66
3.2.12-no-hz-c308b56b53 4.36
What's worth noting is that I haven't seen any nasty side effects of the
latest patch on all kernel versions that I've tested. Hope that helps.
[1] http://img855.imageshack.us/img855/2204/kernelload.png
--
Lesław Kopeć
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2012-04-23 16:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-06 6:51 Inconsistent load average on tickless kernels Aman Gupta
2012-02-23 15:46 ` Lesław Kopeć
2012-02-29 12:06 ` Peter Zijlstra
2012-02-29 16:24 ` Peter Zijlstra
2012-02-29 17:03 ` Peter Zijlstra
2012-03-05 19:57 ` Lesław Kopeć
2012-03-05 22:45 ` Aman Gupta
2012-03-05 23:25 ` Peter Zijlstra
2012-03-05 23:32 ` Peter Zijlstra
2012-03-05 23:33 ` Peter Zijlstra
2012-04-17 12:52 ` Lesław Kopeć
2012-04-17 15:30 ` Jonathan Nieder
2012-04-23 16:20 ` Lesław Kopeć [this message]
2012-04-23 17:57 ` Jonathan Nieder
2012-04-23 20:21 ` Peter Zijlstra
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=4F958141.2000505@nasza-klasa.pl \
--to=leslaw.kopec@nasza-klasa.pl \
--cc=aman@tmm1.net \
--cc=chase.douglas@canonical.com \
--cc=damien.wyart@free.fr \
--cc=dsmythies@telus.net \
--cc=jrnieder@gmail.com \
--cc=kyle@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peterz@infradead.org \
--cc=tglx@linutronix.de \
--cc=venki@google.com \
/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.