diff options
author | Herbert Xu <herbert@gondor.apana.org.au> | 2008-01-25 20:08:28 (GMT) |
---|---|---|
committer | Ingo Molnar <mingo@elte.hu> | 2008-01-25 20:08:28 (GMT) |
commit | 02b67cc3ba36bdba351d6c3a00593f4ec550d9d3 (patch) | |
tree | 5185ad2d780974dc864f12d81d6c8b9fec73097b /include/linux/kernel.h | |
parent | 03319ec8b06849051747a17aa2a0f9aba9277980 (diff) | |
download | linux-fsl-qoriq-02b67cc3ba36bdba351d6c3a00593f4ec550d9d3.tar.xz |
sched: do not do cond_resched() when CONFIG_PREEMPT
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>
Diffstat (limited to 'include/linux/kernel.h')
-rw-r--r-- | include/linux/kernel.h | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/include/linux/kernel.h b/include/linux/kernel.h index 94bc996..a7283c9 100644 --- a/include/linux/kernel.h +++ b/include/linux/kernel.h @@ -105,8 +105,8 @@ struct user; * supposed to. */ #ifdef CONFIG_PREEMPT_VOLUNTARY -extern int cond_resched(void); -# define might_resched() cond_resched() +extern int _cond_resched(void); +# define might_resched() _cond_resched() #else # define might_resched() do { } while (0) #endif |