Date: Tue, 14 Apr 2015 11:54:24 +0200
From: Peter Zijlstra <peterz@infradead.org>
To: Azat Khuzhin <a3at.mail@gmail.com>
Cc: Linux Kernel ML <linux-kernel@vger.kernel.org>,
        Ingo Molnar <mingo@kernel.org>
Subject: Re: load average always more then 1 on idle system with dyntick
 (just after boot)
Message-ID: <20150414095424.GJ5029@twins.programming.kicks-ass.net>
References: <20150331195248.GA3582@azat>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <20150331195248.GA3582@azat>
User-Agent: Mutt/1.5.21 (2012-12-30)
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1153
Lines: 29

On Tue, Mar 31, 2015 at 10:52:48PM +0300, Azat Khuzhin wrote:
> Hi all,
> 
> On one of machines [SUPERMICRO], after installing fresh kernel
> (v4.0-rc5-25-g90a5a89), I noticed that loadavg always greater then 1.
> 
> I do a lot of digging and finally have more information on this issue:
> CONFIG_NO_HZ_IDLE=y  # loadavg always > 1
> CONFIG_HZ_PERIODIC=y # loadavg < 1
> 
> After this I tried to disable "nohz" at boot, to determine whether it is
> statically added code under #ifdef during compilation or not, so I added
> "nohz=off" to cmdline, and it helps!
> 
> Also if you enable preemption loadavg is also < 1:
> CONFIG_PREEMPT_VOLUNTARY=y

So you need CONFIG_PREEMPT=n and CONFIG_NO_HZ_IDLE=y for this to happen?

That's somewhat odd (and uncommon I think, most everybody has at least
VOLUNTARY enabled these days).

I'll try to look over the code to see if I can find a preempt relation,
weird that.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/