diff options
| author | Vincent Guittot <[email protected]> | 2015-08-03 11:55:50 +0200 |
|---|---|---|
| committer | Ingo Molnar <[email protected]> | 2015-09-13 09:52:51 +0200 |
| commit | c5afb6a87f2386bcf09fa051e6ca390d43e2222e (patch) | |
| tree | 3ba5357eeeb0d056db25c8e7869c4cbd854c40cc /tools/perf/scripts/python/export-to-postgresql.py | |
| parent | 446685e9bfa11174332fbb0b3218b37015fbf4ff (diff) | |
sched/fair: Fix nohz.next_balance update
Since commit:
d4573c3e1c99 ("sched: Improve load balancing in the presence of idle CPUs")
the ILB CPU starts with the idle load balancing of other idle CPUs and
finishes with itself in order to speed up the spread of tasks in all
idle CPUs.
The this_rq->next_balance is still used in nohz_idle_balance() as an
intermediate step to gather the shortest next balance before updating
nohz.next_balance. But the former has not been updated yet and is likely to
be set with the current jiffies. As a result, the nohz.next_balance will be
set with current jiffies instead of the real next balance date. This
generates spurious kicks of nohz ilde balance.
nohz_idle_balance() must set the nohz.next_balance without taking into
account this_rq->next_balance which is not updated yet. Then, this_rq will
update nohz.next_update with its next_balance once updated and if necessary.
Signed-off-by: Vincent Guittot <[email protected]>
Signed-off-by: Peter Zijlstra (Intel) <[email protected]>
Acked-by: Jason Low <[email protected]>
Cc: Linus Torvalds <[email protected]>
Cc: Mike Galbraith <[email protected]>
Cc: Peter Zijlstra <[email protected]>
Cc: Thomas Gleixner <[email protected]>
Cc: [email protected]
Link: http://lkml.kernel.org/r/[email protected]
Signed-off-by: Ingo Molnar <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions