RE: [PATCH] top level scheduler domain for ia64

From: Luck, Tony <>
Date: 2004-10-21 03:48:41
>Some have noticed that the overlapping sched domains code 
>doesn't quite work as intended (it results in disjoint domains
>on some machines), and that a top level, machine spanning domain
>is needed.

Why is the solution to jam this into the ia64 specific code?  From
this description it sounds like a generic scheduler problem, so
the solution ought to be up in some generic code.

+	.min_interval		= 80,			\
+	.max_interval		= 320,			\
+	.busy_factor		= 320,			\
+	.imbalance_pct		= 125,			\
+	.cache_hot_time		= (10*1000000),		\
+	.balance_interval	= 100*(63+num_online_cpus())/64,   \

That's a lot of magic numbers and formulae ... are they right?
How would a user know if they are right.

>Nick, can you buy off on the sched.c change?  Alternatively, 
>do you want to send that fix separately John?

I saw the ACK from Nick ... but kernel/sched.c changes will have
to go through Andrew, not me.  Are the ia64 and generic parts
separable?  If the sched.c change goes in, do other architectures
need to have some equivalent change?


To unsubscribe from this list: send the line "unsubscribe linux-ia64" in
the body of a message to
More majordomo info at

Received on Wed Oct 20 14:24:58 2004

This archive was generated by hypermail 2.1.8 : 2005-08-02 09:20:31 EST