summaryrefslogtreecommitdiff
path: root/kernel/sched_features.h
diff options
context:
space:
mode:
authorMike Galbraith <efault@gmx.de>2010-03-11 17:16:43 +0100
committerIngo Molnar <mingo@elte.hu>2010-03-11 18:32:53 +0100
commitc6ee36c423c3ed1fb86bb3eabba9fc256a300d16 (patch)
treea7c98864e3a5c84fac57e8f0ce8777f83df81372 /kernel/sched_features.h
parentf2e74eeac03ffb779d64b66a643c5e598145a28b (diff)
sched: Remove SYNC_WAKEUPS feature
Sync wakeups are critical functionality with a long history. Remove it, we don't need the branch or icache footprint. Signed-off-by: Mike Galbraith <efault@gmx.de> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> LKML-Reference: <1268301817.6785.47.camel@marge.simson.net> Signed-off-by: Ingo Molnar <mingo@elte.hu>
Diffstat (limited to 'kernel/sched_features.h')
-rw-r--r--kernel/sched_features.h8
1 files changed, 0 insertions, 8 deletions
diff --git a/kernel/sched_features.h b/kernel/sched_features.h
index 1cb7c4701bf3..f54b6f9cc3dd 100644
--- a/kernel/sched_features.h
+++ b/kernel/sched_features.h
@@ -23,14 +23,6 @@ SCHED_FEAT(WAKEUP_PREEMPT, 1)
SCHED_FEAT(ASYM_GRAN, 1)
/*
- * Use the SYNC wakeup hint, pipes and the likes use this to indicate
- * the remote end is likely to consume the data we just wrote, and
- * therefore has cache benefit from being placed on the same cpu, see
- * also AFFINE_WAKEUPS.
- */
-SCHED_FEAT(SYNC_WAKEUPS, 1)
-
-/*
* Based on load and program behaviour, see if it makes sense to place
* a newly woken task on the same cpu as the task that woke it --
* improve cache locality. Typically used with SYNC wakeups as