sched_yield.2: NOTES: Remove misleading sentence

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@nginx.com>
Signed-off-by: Alejandro Colomar <alx@nginx.com>

diff --git a/man2/sched_yield.2 b/man2/sched_yield.2
index bab0f9569f000beb9efd9e6b22f865a8acaeb25c..5e5b45a489e1187149bea4de1977029c221f6804 100644 (file)
--- a/man2/sched_yield.2
+++ b/man2/sched_yield.2
@@ -54,11 +54,6 @@ priority list at that time,
 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