diff options
| author | Alejandro Colomar <alx@kernel.org> | 2023-05-03 18:26:12 +0200 |
|---|---|---|
| committer | Alejandro Colomar <alx@kernel.org> | 2023-05-03 18:43:57 +0200 |
| commit | 2f53e3a7e30432f40dd6bcc9dc63c60b01a1cebf (patch) | |
| tree | 54742c341f09b42c6297e979ac06079038df2539 | |
| parent | a4803e53aa7bed4d40aea8e40c21460ca48fe66a (diff) | |
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>
| -rw-r--r-- | man2/sched_yield.2 | 5 |
1 files changed, 0 insertions, 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 @@ 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 |