On Thursday 09 Aug 2018 at 11:30:57 (+0200), Vincent Guittot wrote: > On Tue, 24 Jul 2018 at 14:26, Quentin Perret <quentin.per...@arm.com> wrote: > > > > From: Morten Rasmussen <morten.rasmus...@arm.com> > > > > Energy-aware scheduling is only meant to be active while the system is > > _not_ over-utilized. That is, there are spare cycles available to shift > > tasks around based on their actual utilization to get a more > > energy-efficient task distribution without depriving any tasks. When > > above the tipping point task placement is done the traditional way based > > on load_avg, spreading the tasks across as many cpus as possible based > > on priority scaled load to preserve smp_nice. Below the tipping point we > > want to use util_avg instead. We need to define a criteria for when we > > make the switch. > > > > The util_avg for each cpu converges towards 100% (1024) regardless of > > remove the "(1024)" because util_avg converges to max cpu capacity > which can be different from 1024
Good point, will be fixed in v6. Thanks, Quentin
