blob: 404288354aeeb601fae8950f04746f0f10acf1fb [file] [log] [blame]
Peter Zijlstrae26af0e2009-09-11 12:31:23 +02001/*
2 * Disregards a certain amount of sleep time (sched_latency_ns) and
3 * considers the task to be running during that period. This gives it
4 * a service deficit on wakeup, allowing it to run sooner.
5 */
Ingo Molnar51e03042009-09-16 08:54:45 +02006SCHED_FEAT(FAIR_SLEEPERS, 1)
7
8/*
9 * Only give sleepers 50% of their service deficit. This allows
10 * them to run sooner, but does not allow tons of sleepers to
11 * rip the spread apart.
12 */
13SCHED_FEAT(GENTLE_FAIR_SLEEPERS, 1)
Peter Zijlstrae26af0e2009-09-11 12:31:23 +020014
15/*
Peter Zijlstrae26af0e2009-09-11 12:31:23 +020016 * Place new tasks ahead so that they do not starve already running
17 * tasks
18 */
Peter Zijlstraf00b45c2008-04-19 19:45:00 +020019SCHED_FEAT(START_DEBIT, 1)
Peter Zijlstrae26af0e2009-09-11 12:31:23 +020020
21/*
22 * Should wakeups try to preempt running tasks.
23 */
24SCHED_FEAT(WAKEUP_PREEMPT, 1)
25
26/*
Peter Zijlstrae26af0e2009-09-11 12:31:23 +020027 * When converting the wakeup granularity to virtual time, do it such
28 * that heavier tasks preempting a lighter task have an edge.
29 */
30SCHED_FEAT(ASYM_GRAN, 1)
31
32/*
33 * Always wakeup-preempt SYNC wakeups, see SYNC_WAKEUPS.
34 */
35SCHED_FEAT(WAKEUP_SYNC, 0)
36
37/*
Peter Zijlstrae26af0e2009-09-11 12:31:23 +020038 * Use the SYNC wakeup hint, pipes and the likes use this to indicate
39 * the remote end is likely to consume the data we just wrote, and
40 * therefore has cache benefit from being placed on the same cpu, see
41 * also AFFINE_WAKEUPS.
42 */
Peter Zijlstraf00b45c2008-04-19 19:45:00 +020043SCHED_FEAT(SYNC_WAKEUPS, 1)
Peter Zijlstrae26af0e2009-09-11 12:31:23 +020044
45/*
46 * Based on load and program behaviour, see if it makes sense to place
47 * a newly woken task on the same cpu as the task that woke it --
48 * improve cache locality. Typically used with SYNC wakeups as
49 * generated by pipes and the like, see also SYNC_WAKEUPS.
50 */
51SCHED_FEAT(AFFINE_WAKEUPS, 1)
52
53/*
54 * Prefer to schedule the task we woke last (assuming it failed
55 * wakeup-preemption), since its likely going to consume data we
56 * touched, increases cache locality.
57 */
Mike Galbraith0ec9fab2009-09-15 15:07:03 +020058SCHED_FEAT(NEXT_BUDDY, 0)
Peter Zijlstrae26af0e2009-09-11 12:31:23 +020059
60/*
61 * Prefer to schedule the task that ran last (when we did
62 * wake-preempt) as that likely will touch the same data, increases
63 * cache locality.
64 */
65SCHED_FEAT(LAST_BUDDY, 1)
66
67/*
68 * Consider buddies to be cache hot, decreases the likelyness of a
69 * cache buddy being migrated away, increases cache locality.
70 */
71SCHED_FEAT(CACHE_HOT_BUDDY, 1)
72
Peter Zijlstra8e6598a2009-09-03 13:20:03 +020073/*
74 * Use arch dependent cpu power functions
75 */
76SCHED_FEAT(ARCH_POWER, 0)
77
Ingo Molnar0c4b83d2008-10-20 14:27:43 +020078SCHED_FEAT(HRTICK, 0)
Peter Zijlstraf00b45c2008-04-19 19:45:00 +020079SCHED_FEAT(DOUBLE_TICK, 0)
Peter Zijlstraefc2dea2008-08-20 12:44:55 +020080SCHED_FEAT(LB_BIAS, 1)
Peter Zijlstra3b640892009-09-16 13:44:33 +020081SCHED_FEAT(LB_SHARES_UPDATE, 1)
Peter Zijlstraf5bfb7d2008-06-27 13:41:39 +020082SCHED_FEAT(ASYM_EFF_LOAD, 1)
Peter Zijlstrae26af0e2009-09-11 12:31:23 +020083
84/*
85 * Spin-wait on mutex acquisition when the mutex owner is running on
86 * another cpu -- assumes that when the owner is running, it will soon
87 * release the lock. Decreases scheduling overhead.
88 */
Peter Zijlstra0d66bf62009-01-12 14:01:47 +010089SCHED_FEAT(OWNER_SPIN, 1)