On Fri, 10 Nov 2006, Siddha, Suresh B wrote:
> Nick was suggesting another alternative, that we should increase the max
> interval and probably make it dependent on number of cpus that
> share the group. Today for NUMA domain, we already set max_interval
> based on online cpus. Perhaps we need to do that for other domains (SMP, MC)
> too and increase the max interval on NUMA for big systems?
I have been trying to run with this patch. We increase the min interval so
that we can at least put one tick between each of the load balance actions
of each processor. The cpu_offset can be modified to:
/* Don't have all balancing operations going off at once: */
static inline unsigned long cpu_offset(int cpu)
{
if (NR_CPUS < HZ)
return jiffies + cpu * HZ / NR_CPUS;
else
return jiffies + cpu;
}
But exclusion in load balancing would take care of the above.
Index: linux-2.6.19-rc4-mm2/include/linux/topology.h
===================================================================
--- linux-2.6.19-rc4-mm2.orig/include/linux/topology.h 2006-11-07 16:43:43.084665449 -0600
+++ linux-2.6.19-rc4-mm2/include/linux/topology.h 2006-11-07 16:55:23.027245226 -0600
@@ -182,7 +182,7 @@
.parent = NULL, \
.child = NULL, \
.groups = NULL, \
- .min_interval = 64, \
+ .min_interval = max(64, jiffies_to_msec(num_online_cpus())),\
.max_interval = 64*num_online_cpus(), \
.busy_factor = 128, \
.imbalance_pct = 133, \
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
