mirror of https://github.com/mkerrisk/man-pages
sched.7: Don't mention sched_setscheduler(2) in discussions of setting policies
In a couple of places, sched_setscheduler(2) is mentioned as the way of setting policies. But now there is sched_setattr(2) as well, rewrite the text in a more generic way. Signed-off-by: Michael Kerrisk <mtk.manpages@gmail.com>
This commit is contained in:
parent
4c2eb0c23f
commit
759e1210fc
|
@ -305,8 +305,7 @@ threads can set a nonzero static priority (i.e., set a real-time
|
|||
scheduling policy).
|
||||
The only change that an unprivileged thread can make is to set the
|
||||
.B SCHED_OTHER
|
||||
policy, and this can be done only if the effective user ID of the caller of
|
||||
.BR sched_setscheduler ()
|
||||
policy, and this can be done only if the effective user ID of the caller
|
||||
matches the real or effective user ID of the target thread
|
||||
(i.e., the thread specified by
|
||||
.IR pid )
|
||||
|
@ -451,9 +450,7 @@ kernel, the additional configuration item
|
|||
becomes available.
|
||||
If this is selected, Linux is transformed into a regular
|
||||
real-time operating system.
|
||||
The FIFO and RR scheduling policies that can be selected using
|
||||
.BR sched_setscheduler ()
|
||||
are then used to run a thread
|
||||
The FIFO and RR scheduling policies are then used to run a thread
|
||||
with true real-time priority and a minimum worst-case scheduling latency.
|
||||
.SH SEE ALSO
|
||||
.ad l
|
||||
|
|
Loading…
Reference in New Issue