sched/numa: Decay ->wakee_flips instead of zeroing
authorRik van Riel <riel@redhat.com>
Fri, 16 May 2014 04:13:32 +0000 (00:13 -0400)
committerIngo Molnar <mingo@kernel.org>
Thu, 22 May 2014 09:16:41 +0000 (11:16 +0200)
Affine wakeups have the potential to interfere with NUMA placement.
If a task wakes up too many other tasks, affine wakeups will get
disabled.

However, regardless of how many other tasks it wakes up, it gets
re-enabled once a second, potentially interfering with NUMA
placement of other tasks.

By decaying wakee_wakes in half instead of zeroing it, we can avoid
that problem for some workloads.

Signed-off-by: Rik van Riel <riel@redhat.com>
Signed-off-by: Peter Zijlstra <peterz@infradead.org>
Cc: chegu_vinod@hp.com
Cc: umgwanakikbuti@gmail.com
Link: http://lkml.kernel.org/r/20140516001332.67f91af2@annuminas.surriel.com
Signed-off-by: Ingo Molnar <mingo@kernel.org>
kernel/sched/fair.c

index 503f750c2d2535be0cd7504112501998b7f028a8..c9617b73bcc00d6ac8b275f47f130afd15749dcd 100644 (file)
@@ -4065,7 +4065,7 @@ static void record_wakee(struct task_struct *p)
         * about the loss.
         */
        if (jiffies > current->wakee_flip_decay_ts + HZ) {
-               current->wakee_flips = 0;
+               current->wakee_flips >>= 1;
                current->wakee_flip_decay_ts = jiffies;
        }