All of lore.kernel.org
 help / color / mirror / Atom feed
From: Greg KH <gregkh@suse.de>
To: tmhikaru@gmail.com
Cc: Florian Mickler <florian@mickler.org>, linux-kernel@vger.kernel.org
Subject: Re: PROBLEM: Unusually high load average when idle in 2.6.35, 2.6.35.1 and later
Date: Fri, 1 Oct 2010 11:09:23 -0700	[thread overview]
Message-ID: <20101001180923.GB9353@suse.de> (raw)
In-Reply-To: <20101001035321.GA2360@roll>

On Thu, Sep 30, 2010 at 11:53:21PM -0400, tmhikaru@gmail.com wrote:

<snip>

> Author: Peter Zijlstra <a.p.zijlstra@chello.nl>
> Date:   Thu Apr 22 21:50:19 2010 +0200
> 
>     sched: Cure load average vs NO_HZ woes
> 
>     Chase reported that due to us decrementing calc_load_task prematurely
>     (before the next LOAD_FREQ sample), the load average could be scewed
>     by as much as the number of CPUs in the machine.
> 
>     This patch, based on Chase's patch, cures the problem by keeping the
>     delta of the CPU going into NO_HZ idle separately and folding that in
>     on the next LOAD_FREQ update.
> 
>     This restores the balance and we get strict LOAD_FREQ period samples.
> 
>     Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
>     Acked-by: Chase Douglas <chase.douglas@canonical.com>
>     LKML-Reference: <1271934490.1776.343.camel@laptop>
>     Signed-off-by: Ingo Molnar <mingo@elte.hu>

Care to resend this and cc: Peter, Chase, and Ingo?

thanks,

greg k-h

      parent reply	other threads:[~2010-10-01 18:42 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
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 [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=20101001180923.GB9353@suse.de \
    --to=gregkh@suse.de \
    --cc=florian@mickler.org \
    --cc=linux-kernel@vger.kernel.org \
    --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 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.