diff options
author | Mike Galbraith <umgwanakikbuti@gmail.com> | 2015-07-14 15:39:50 (GMT) |
---|---|---|
committer | Ingo Molnar <mingo@kernel.org> | 2015-08-03 10:21:23 (GMT) |
commit | 63b0e9edceec10fa41ec33393a1515a5ff444277 (patch) | |
tree | d895837f47d954fc91e98862d853dfd810e56feb /crypto/fcrypt.c | |
parent | fbd705a0c6184580d0e2fbcbd47a37b6e5822511 (diff) | |
download | linux-63b0e9edceec10fa41ec33393a1515a5ff444277.tar.xz |
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 'crypto/fcrypt.c')
0 files changed, 0 insertions, 0 deletions