Re: [patch 0/7] sched: change nohz idle load balancing logic to pushmodel

From: Nigel Cunningham
Date: Mon May 17 2010 - 18:39:31 EST

Hi Suresh.

On 18/05/10 04:27, Suresh Siddha wrote:
This is an updated version of patchset which is posted earlier at

Existing nohz idle load balance logic uses the pull model, with one
idle load balancer CPU nominated on any partially idle system and that
balancer CPU not going into nohz mode. With the periodic tick, the
balancer does the idle balancing on behalf of all the CPUs in nohz mode.

This is not very optimal and has few issues:
* the balancer will continue to have periodic ticks and wakeup
frequently (HZ rate), even though it may not have any rebalancing to do on
behalf of any of the idle CPUs.
* On x86 and CPUs that have APIC timer stoppage on idle CPUs, this periodic
wakeup can result in an additional interrupt on a CPU doing the timer

The alternative is to have a push model, where all idle CPUs can enter nohz
mode and any busy CPU kicks one of the idle CPUs to take care of idle
balancing on behalf of a group of idle CPUs.

Following patches switches idle load balancer to this push approach.

Updates from the previous version:

* Busy CPU uses send_remote_softirq() for invoking SCHED_SOFTIRQ on the
idle load balancing cpu, which does the load balancing on behalf of
all the idle CPUs.

* Dropped the per NUMA node nohz load balancing as it doesn't detect
certain imbalance scenarios. This will be addressed later.

Signed-off-by: Suresh Siddha<suresh.b.siddha@xxxxxxxxx>
Signed-off-by: Venkatesh Pallipadi<venki@xxxxxxxxxx>

Sounds great.

I'm in the middle of packing at the moment, but will try to find time to test the patches.

It might help to show the difference that the patch series makes (powertop output?)


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at