]> git.ipfire.org Git - thirdparty/glibc.git/commit
manual: Explain sched_yield semantics with different schedulers
authorSiddhesh Poyarekar <siddhesh@sourceware.org>
Thu, 30 Jan 2025 15:05:17 +0000 (10:05 -0500)
committerSiddhesh Poyarekar <siddhesh@sourceware.org>
Wed, 5 Mar 2025 00:36:40 +0000 (19:36 -0500)
commit226476e32251b5688eead482a9338c04ce84d715
tree69ce831d89d1ac2d5aff5c934225f87286ddc6f1
parenta2bd5008a99032830add3e4005c25b61e3207112
manual: Explain sched_yield semantics with different schedulers

The manual entry for sched_yield mentions that the function call could
be a nop if there are no other tasks with the same absolute priority.
Expand the explanation to include example schedulers on Linux so that
it's clear that sched_yield may not always result in a different task
being scheduled.

Signed-off-by: Siddhesh Poyarekar <siddhesh@sourceware.org>
Reviewed-by: Joseph Myers <josmyers@redhat.com>
manual/resource.texi