sched_yield(2) is not the right thing for heavily contended resources. The right thing to do is to call functions that wake the waiting threads. Link: <https://www.realworldtech.com/forum/?threadid=189711&curpostid=189752> Cc: Andrew Clayton <a.clayton@xxxxxxxxx> Signed-off-by: Alejandro Colomar <alx@xxxxxxxxx> --- man2/sched_yield.2 | 5 ----- 1 file changed, 5 deletions(-) diff --git a/man2/sched_yield.2 b/man2/sched_yield.2 index bab0f9569..5e5b45a48 100644 --- a/man2/sched_yield.2 +++ b/man2/sched_yield.2 @@ -54,11 +54,6 @@ .SH NOTES it will continue to run after a call to .BR sched_yield (). .PP -Strategic calls to -.BR sched_yield () -can improve performance by giving other threads or processes -a chance to run when (heavily) contended resources (e.g., mutexes) -have been released by the caller. Avoid calling .BR sched_yield () unnecessarily or inappropriately -- 2.40.1
