sched: Remove ASYM_GRAN feature

This features has been enabled for quite a while, after testing showed that
easing preemption for light tasks was harmful to high priority threads.

Remove the feature flag.

Signed-off-by: Mike Galbraith <efault@gmx.de>
Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl>
LKML-Reference: <1268301675.6785.44.camel@marge.simson.net>
Signed-off-by: Ingo Molnar <mingo@elte.hu>
This commit is contained in:
Mike Galbraith 2010-03-11 17:17:04 +01:00 committed by Ingo Molnar
parent c6ee36c423
commit 13814d42e4
2 changed files with 11 additions and 23 deletions

View File

@ -1583,9 +1583,7 @@ wakeup_gran(struct sched_entity *curr, struct sched_entity *se)
/* /*
* Since its curr running now, convert the gran from real-time * Since its curr running now, convert the gran from real-time
* to virtual-time in his units. * to virtual-time in his units.
*/ *
if (sched_feat(ASYM_GRAN)) {
/*
* By using 'se' instead of 'curr' we penalize light tasks, so * By using 'se' instead of 'curr' we penalize light tasks, so
* they get preempted easier. That is, if 'se' < 'curr' then * they get preempted easier. That is, if 'se' < 'curr' then
* the resulting gran will be larger, therefore penalizing the * the resulting gran will be larger, therefore penalizing the
@ -1597,10 +1595,6 @@ wakeup_gran(struct sched_entity *curr, struct sched_entity *se)
*/ */
if (unlikely(se->load.weight != NICE_0_LOAD)) if (unlikely(se->load.weight != NICE_0_LOAD))
gran = calc_delta_fair(gran, se); gran = calc_delta_fair(gran, se);
} else {
if (unlikely(curr->load.weight != NICE_0_LOAD))
gran = calc_delta_fair(gran, curr);
}
return gran; return gran;
} }

View File

@ -16,12 +16,6 @@ SCHED_FEAT(START_DEBIT, 1)
*/ */
SCHED_FEAT(WAKEUP_PREEMPT, 1) SCHED_FEAT(WAKEUP_PREEMPT, 1)
/*
* When converting the wakeup granularity to virtual time, do it such
* that heavier tasks preempting a lighter task have an edge.
*/
SCHED_FEAT(ASYM_GRAN, 1)
/* /*
* Based on load and program behaviour, see if it makes sense to place * 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 -- * a newly woken task on the same cpu as the task that woke it --