Christoph Lameter wrote:
Only call rebalance_domains when needed from scheduler_tick.
Call rebalance_domains from a tasklet with interrupt enabled.
Only call it when one of the sched domains is to be rebalanced.
The jiffies when the next balancing action is to take place is
kept in a per cpu variable next_balance.
sched-domains was supposed to be able to build a whacky topology
so you didn't have to take the occasional big latency hit when
scanning 512 CPUs...
Ideas were: overlapping, non-covering top level domains, or a
SD_BALANCE_ROTOR, which scans only N (< all) groups on each
balance attempt, but more frequently.
--
SUSE Labs, Novell Inc.
Send instant messages to your online friends http://au.messenger.yahoo.com
-
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]
