diff options
Diffstat (limited to 'man2/sched_setscheduler.2')
| -rw-r--r-- | man2/sched_setscheduler.2 | 56 |
1 files changed, 28 insertions, 28 deletions
diff --git a/man2/sched_setscheduler.2 b/man2/sched_setscheduler.2 index b22dd76d5..517466bac 100644 --- a/man2/sched_setscheduler.2 +++ b/man2/sched_setscheduler.2 @@ -72,7 +72,7 @@ Various "real-time" policies are also supported, for special time-critical applications that need precise control over the way in which runnable threads are selected for execution. For the rules governing when a process may use these policies, see -.BR sched (7). +.MR sched 7 . The real-time policies that may be specified in .I policy are: @@ -87,9 +87,9 @@ For each of the above policies, .I param\->sched_priority specifies a scheduling priority for the thread. This is a number in the range returned by calling -.BR sched_get_priority_min (2) +.MR sched_get_priority_min 2 and -.BR sched_get_priority_max (2) +.MR sched_get_priority_max 2 with the specified .IR policy . On Linux, these system calls return, respectively, 1 and 99. @@ -101,10 +101,10 @@ flag can be ORed in when calling .BR sched_setscheduler (). As a result of including this flag, children created by -.BR fork (2) +.MR fork 2 do not inherit privileged scheduling policies. See -.BR sched (7) +.MR sched 7 for details. .P .BR sched_getscheduler () @@ -159,20 +159,20 @@ match the real user ID or the save set-user-ID of the target. The scheduling policy and parameters are in fact per-thread attributes on Linux. The value returned from a call to -.BR gettid (2) +.MR gettid 2 can be passed in the argument .IR pid . Specifying .I pid as 0 will operate on the attributes of the calling thread, and passing the value returned from a call to -.BR getpid (2) +.MR getpid 2 will operate on the attributes of the main thread of the thread group. (If you are using the POSIX threads API, then use -.BR pthread_setschedparam (3), -.BR pthread_getschedparam (3), +.MR pthread_setschedparam 3 , +.MR pthread_getschedparam 3 , and -.BR pthread_setschedprio (3), +.MR pthread_setschedprio 3 , instead of the .BR sched_* (2) system calls.) @@ -188,12 +188,12 @@ POSIX.1-2001. .SH NOTES Further details of the semantics of all of the above "normal" and "real-time" scheduling policies can be found in the -.BR sched (7) +.MR sched 7 manual page. That page also describes an additional policy, .BR SCHED_DEADLINE , which is settable only via -.BR sched_setattr (2). +.MR sched_setattr 2 . .P POSIX systems on which .BR sched_setscheduler () @@ -213,20 +213,20 @@ since it always returns 0 on success. .SH SEE ALSO .ad l .nh -.BR chrt (1), -.BR nice (2), -.BR sched_get_priority_max (2), -.BR sched_get_priority_min (2), -.BR sched_getaffinity (2), -.BR sched_getattr (2), -.BR sched_getparam (2), -.BR sched_rr_get_interval (2), -.BR sched_setaffinity (2), -.BR sched_setattr (2), -.BR sched_setparam (2), -.BR sched_yield (2), -.BR setpriority (2), -.BR capabilities (7), -.BR cpuset (7), -.BR sched (7) +.MR chrt 1 , +.MR nice 2 , +.MR sched_get_priority_max 2 , +.MR sched_get_priority_min 2 , +.MR sched_getaffinity 2 , +.MR sched_getattr 2 , +.MR sched_getparam 2 , +.MR sched_rr_get_interval 2 , +.MR sched_setaffinity 2 , +.MR sched_setattr 2 , +.MR sched_setparam 2 , +.MR sched_yield 2 , +.MR setpriority 2 , +.MR capabilities 7 , +.MR cpuset 7 , +.MR sched 7 .ad |