From: Peter Zijlstra <peterz@infradead.org>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: "Lesław Kopeć" <leslaw.kopec@nasza-klasa.pl>,
"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 22:21:06 +0200 [thread overview]
Message-ID: <1335212466.2463.85.camel@laptop> (raw)
In-Reply-To: <20120423175715.GD9635@burratino>
On Mon, 2012-04-23 at 12:57 -0500, Jonathan Nieder wrote:
> Lesław Kopeć wrote:
>
> > 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.
>
> Ok.
>
> Peter, do you think it would make sense to add c308b56b53987 to 3.0.y
> and newer stable kernels?
If anybody is still maintaining those and cares enough to do the work,
sure whatever.. ;)
prev parent reply other threads:[~2012-04-23 20:21 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ć
2012-04-23 17:57 ` Jonathan Nieder
2012-04-23 20:21 ` Peter Zijlstra [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=1335212466.2463.85.camel@laptop \
--to=peterz@infradead.org \
--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=leslaw.kopec@nasza-klasa.pl \
--cc=linux-kernel@vger.kernel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox