lk/linux-kernel-test
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

sched: do not do cond_resched() when CONFIG_PREEMPT

Browse Source 
Why do we even have cond_resched when real preemption
is on? It seems to be a waste of space and time.

remove cond_resched with CONFIG_PREEMPT on.

Signed-off-by: Ingo Molnar <mingo@elte.hu>
This commit is contained in:
Herbert Xu
2008-01-25 21:08:28 +01:00
committed by Ingo Molnar
parent 03319ec8b0
commit 02b67cc3ba
3 changed files with 18 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
kernel/sched.c
View File

@@ -4678,7 +4678,8 @@ static void __cond_resched(void)
} while (need_resched());
}
int __sched cond_resched(void)
#if !defined(CONFIG_PREEMPT) || defined(CONFIG_PREEMPT_VOLUNTARY)
int __sched _cond_resched(void)
{
if (need_resched() && !(preempt_count() & PREEMPT_ACTIVE) &&
system_state == SYSTEM_RUNNING) {
@@ -4687,7 +4688,8 @@ int __sched cond_resched(void)
}
return 0;
}
EXPORT_SYMBOL(cond_resched);
EXPORT_SYMBOL(_cond_resched);
#endif
/*
* cond_resched_lock() - if a reschedule is pending, drop the given lock,