On Thu, 26 Oct 2006, Nick Piggin wrote:
> > 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...
How is that supposed to work? The load calculations will be off
in that case and also the load balancing algorithm wont work anymore.
This is going to be a pretty significant rework of how the scheduler
works but given the problems with pinned tasks... maybe that is
necessary?
duler?
-
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]
