public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: James Pearson <james-p@moving-picture.com>
To: linux-kernel@vger.kernel.org
Subject: Re: High load average on idle machine running 2.6.32
Date: Thu, 10 Dec 2009 16:29:22 +0000	[thread overview]
Message-ID: <4B2121E2.2030900@moving-picture.com> (raw)
In-Reply-To: <4B1D8C5D.9040900@moving-picture.com>

James Pearson wrote:
> I've booted a 64 bit 2.6.32 kernel on dual processor, quad core Xeon 
> E5440 machine. The load average when the machine is idle varies between 
> 2 and 3.
> 
> When using a 2.6.31 kernel on the same machine, the load average when 
> idle is nearly 0
> 
> The kernel doesn't use modules - all that is needed is compiled in. The 
> machine uses NFS-root
> 
> Strangely, when I run 'iftop' (from http://www.ex-parrot.com/pdw/iftop/) 
> using the 2.6.32 kernel, the load average drops to below 0.5  - stop 
> running iftop, and the load average climbs again ...
> 
> Any idea what might be causing this?

It looks like whatever is causing this happened between 2.6.31-git7 and 
2.6.31-git8 - unfortunately I don't know how to find out what change 
caused this ...

Also, if I 'hot-unplug' CPUs 1 to 7, the load average drops to 0 - when 
I re-enable theses CPUs, the load average climbs.

I guess this is a problem with my particular config - or maybe because 
I'm using NFS-root (the root file system is readonly), or using a 
non-module kernel?

Thanks

James Pearson

  reply	other threads:[~2009-12-10 16:29 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-07 23:14 High load average on idle machine running 2.6.32 James Pearson
2009-12-10 16:29 ` James Pearson [this message]
2009-12-14 17:49   ` James Pearson
2009-12-18 13:43     ` Andrea Suisani
2009-12-18 14:12       ` Peter Zijlstra
2009-12-18 15:34         ` James Pearson

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=4B2121E2.2030900@moving-picture.com \
    --to=james-p@moving-picture.com \
    --cc=linux-kernel@vger.kernel.org \
    /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