summaryrefslogtreecommitdiffstats
path: root/init
diff options
context:
space:
mode:
authorMike Galbraith2015-07-14 17:39:50 +0200
committerIngo Molnar2015-08-03 12:21:23 +0200
commit63b0e9edceec10fa41ec33393a1515a5ff444277 (patch)
treed895837f47d954fc91e98862d853dfd810e56feb /init
parentsched: Introduce the 'trace_sched_waking' tracepoint (diff)
downloadkernel-qcow2-linux-63b0e9edceec10fa41ec33393a1515a5ff444277.tar.gz
kernel-qcow2-linux-63b0e9edceec10fa41ec33393a1515a5ff444277.tar.xz
kernel-qcow2-linux-63b0e9edceec10fa41ec33393a1515a5ff444277.zip
sched/fair: Beef up wake_wide()
Josef Bacik reported that Facebook sees better performance with their 1:N load (1 dispatch/node, N workers/node) when carrying an old patch to try very hard to wake to an idle CPU. While looking at wake_wide(), I noticed that it doesn't pay attention to the wakeup of a many partner waker, returning 1 only when waking one of its many partners. Correct that, letting explicit domain flags override the heuristic. While at it, adjust task_struct bits, we don't need a 64-bit counter. Tested-by: Josef Bacik <jbacik@fb.com> Signed-off-by: Mike Galbraith <umgwanakikbuti@gmail.com> [ Tidy things up. ] Signed-off-by: Peter Zijlstra (Intel) <peterz@infradead.org> Cc: Linus Torvalds <torvalds@linux-foundation.org> Cc: Mike Galbraith <efault@gmx.de> Cc: Peter Zijlstra <peterz@infradead.org> Cc: Thomas Gleixner <tglx@linutronix.de> Cc: kernel-team<Kernel-team@fb.com> Cc: morten.rasmussen@arm.com Cc: riel@redhat.com Link: http://lkml.kernel.org/r/1436888390.7983.49.camel@gmail.com Signed-off-by: Ingo Molnar <mingo@kernel.org>
Diffstat (limited to 'init')
0 files changed, 0 insertions, 0 deletions