public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Peter Zijlstra <peterz@infradead.org>
To: Florian Mickler <florian@mickler.org>
Cc: tmhikaru@gmail.com, linux-kernel@vger.kernel.org,
	Greg KH <gregkh@suse.de>,
	Chase Douglas <chase.douglas@canonical.com>,
	Ingo Molnar <mingo@elte.hu>
Subject: Re: PROBLEM: Unusually high load average when idle in 2.6.35, 2.6.35.1 and later
Date: Sun, 03 Oct 2010 14:04:38 +0200	[thread overview]
Message-ID: <1286107478.2144.177.camel@laptop> (raw)
In-Reply-To: <20101003121209.586f7b6b@schatten.dmk.lab>

On Sun, 2010-10-03 at 12:12 +0200, Florian Mickler wrote:
> On Sun, 03 Oct 2010 10:41:08 +0200
> Peter Zijlstra <peterz@infradead.org> wrote:
> 
> > On Sat, 2010-10-02 at 23:02 -0400, tmhikaru@gmail.com wrote:
> > >  The load average statistic is indeed broken somehow, and I
> > > did bisect it down to where the problem began, however there seems to be no
> > > performance problem related to it I can find. 
> > 
> > Chase, anything you can see broken with this stuff?
> 
> Peter, do you think it would be worthwile to test a kernel with the
> low load-averages in NOHZ=disable mode? The bisected commit claims to
> fix a NOHZ issue with the load average. So if the new figures are the
> correct ones, they should be somehow similar to the figures before
> with NOHZ? Or am I on the wrong track here?

No, that makes sense, but there is of course the distinct possibility
that the patch wrecked the !nohz path as well. So ideally you'd have to
compare NOHZ=n with this patch reverted and NOHZ=y with this patch in
place.



  reply	other threads:[~2010-10-03 12:04 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-01  3:53 PROBLEM: Unusually high load average when idle in 2.6.35, 2.6.35.1 and later tmhikaru
2010-10-01  9:48 ` tmhikaru
2010-10-03  3:02   ` tmhikaru
2010-10-03  8:41     ` Peter Zijlstra
2010-10-03 10:12       ` Florian Mickler
2010-10-03 12:04         ` Peter Zijlstra [this message]
2010-10-03 17:18           ` tmhikaru
2010-10-11  1:09             ` tmhikaru
2010-10-03 10:21     ` Florian Mickler
2010-10-03 17:10       ` tmhikaru
2010-10-01 18:09 ` Greg KH

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=1286107478.2144.177.camel@laptop \
    --to=peterz@infradead.org \
    --cc=chase.douglas@canonical.com \
    --cc=florian@mickler.org \
    --cc=gregkh@suse.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mingo@elte.hu \
    --cc=tmhikaru@gmail.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