sched: Update yield() docs
Suggested-by: Joe Perches <joe@perches.com> Signed-off-by: Peter Zijlstra <a.p.zijlstra@chello.nl> Link: http://lkml.kernel.org/r/1331056466.11248.327.camel@twins Signed-off-by: Ingo Molnar <mingo@elte.hu>
This commit is contained in:
parent
3ccf3e8306
commit
8e3fabfde4
|
@ -4577,8 +4577,24 @@ EXPORT_SYMBOL(__cond_resched_softirq);
|
|||
/**
|
||||
* yield - yield the current processor to other threads.
|
||||
*
|
||||
* This is a shortcut for kernel-space yielding - it marks the
|
||||
* thread runnable and calls sys_sched_yield().
|
||||
* Do not ever use this function, there's a 99% chance you're doing it wrong.
|
||||
*
|
||||
* The scheduler is at all times free to pick the calling task as the most
|
||||
* eligible task to run, if removing the yield() call from your code breaks
|
||||
* it, its already broken.
|
||||
*
|
||||
* Typical broken usage is:
|
||||
*
|
||||
* while (!event)
|
||||
* yield();
|
||||
*
|
||||
* where one assumes that yield() will let 'the other' process run that will
|
||||
* make event true. If the current task is a SCHED_FIFO task that will never
|
||||
* happen. Never use yield() as a progress guarantee!!
|
||||
*
|
||||
* If you want to use yield() to wait for something, use wait_event().
|
||||
* If you want to use yield() to be 'nice' for others, use cond_resched().
|
||||
* If you still want to use yield(), do not!
|
||||
*/
|
||||
void __sched yield(void)
|
||||
{
|
||||
|
|
Loading…
Reference in New Issue