VST and Sched Load Balance
[Sorry about sending my response from a different account. Can't seem to access my ibm account right now]
Quoted 11 lines · Ingo
Another, more effective, less intrusive but also more complex approach would be to make a distinction between 'totally idle' and 'partially idle or busy' system states. When all CPUs are idle then all timer irqs may be stopped and full VST logic applies. When at least one CPU is busy, all the other CPUs may still be put to sleep completely and immediately, but the busy CPU(s) have to take over a 'watchdog' role, and need to run the 'do the idle CPUs need new tasks' balancing functions. I.e. the scheduling function of other CPUs is migrated to busy CPUs. If there are no busy CPUs then there's no work, so this ought to be simple on the VST side. This needs some reorganization on the scheduler side but ought to be doable as well.
Hmm ..I think this is the approach that I have followed in my patch, where busy CPUs act as watchdogs and wakeup sleeping CPUs at an appropriate time. The appropriate time is currently based on the busy CPU's load being greater than 1 and the sleeping CPU not having balanced for its minimum balance_interval.
Do you have any other suggestions on how the watchdog function should be implemented?
- vatsa