version 4, including all changes.
.
Rev |
Author |
# |
Line |
1 |
perry |
1 |
GET_PRIORITY_MAX |
|
|
2 |
!!!GET_PRIORITY_MAX |
|
|
3 |
NAME |
|
|
4 |
SYNOPSIS |
|
|
5 |
DESCRIPTION |
|
|
6 |
RETURN VALUE |
|
|
7 |
ERRORS |
|
|
8 |
CONFORMING TO |
|
|
9 |
SEE ALSO |
|
|
10 |
---- |
|
|
11 |
!!NAME |
|
|
12 |
|
|
|
13 |
|
|
|
14 |
sched_get_priority_max, sched_get_priority_min - get static priority range |
|
|
15 |
!!SYNOPSIS |
|
|
16 |
|
|
|
17 |
|
|
|
18 |
__#include __ |
|
|
19 |
|
|
|
20 |
|
|
|
21 |
__int sched_get_priority_max(int__ |
|
|
22 |
''policy''__);__ |
|
|
23 |
|
|
|
24 |
|
|
|
25 |
__int sched_get_priority_min(int__ |
|
|
26 |
''policy''__);__ |
|
|
27 |
!!DESCRIPTION |
|
|
28 |
|
|
|
29 |
|
|
|
30 |
__sched_get_priority_max__ returns the maximum priority |
|
|
31 |
value that can be used with the scheduling algorithm |
|
|
32 |
identified by ''policy''. __sched_get_priority_min__ |
|
|
33 |
returns the minimum priority value that can be used with the |
|
|
34 |
scheduling algorithm identified by ''policy''. Supported |
|
|
35 |
''policy'' values are ''SCHED_FIFO'', ''SCHED_RR'', |
|
|
36 |
and ''SCHED_OTHER''. |
|
|
37 |
|
|
|
38 |
|
|
|
39 |
Processes with numerically higher priority values are |
|
|
40 |
scheduled before processes with numerically lower priority |
|
|
41 |
values. Thus, the value returned by |
|
|
42 |
__sched_get_priority_max__ will be greater than the value |
|
|
43 |
returned by __sched_get_priority_min__. |
|
|
44 |
|
|
|
45 |
|
|
|
46 |
Linux allows the static priority value range 1 to 99 for |
|
|
47 |
''SCHED_FIFO'' and ''SCHED_RR'' and the priority 0 for |
|
|
48 |
''SCHED_OTHER''. Scheduling priority ranges for the |
|
|
49 |
various policies are not alterable. |
|
|
50 |
|
|
|
51 |
|
|
|
52 |
The range of scheduling priorities may vary on other POSIX |
|
|
53 |
systems, thus it is a good idea for portable applications to |
|
|
54 |
use a virtual priority range and map it to the interval |
|
|
55 |
given by __sched_get_priority_max__ and |
|
|
56 |
__sched_get_priority_min__. POSIX.1b requires a spread of |
|
|
57 |
at least 32 between the maximum and the minimum values for |
|
|
58 |
''SCHED_FIFO'' and ''SCHED_RR''. |
|
|
59 |
|
|
|
60 |
|
|
|
61 |
POSIX systems on which __sched_get_priority_max__ and |
|
|
62 |
__sched_get_priority_min__ are available define |
|
|
63 |
''_POSIX_PRIORITY_SCHEDULING'' in |
|
|
64 |
'' |
|
|
65 |
!!RETURN VALUE |
|
|
66 |
|
|
|
67 |
|
|
|
68 |
On success, __sched_get_priority_max__ and |
|
|
69 |
__sched_get_priority_min__ return the maximum/minimum |
|
|
70 |
priority value for the named scheduling policy. On error, -1 |
|
|
71 |
is returned, ''errno'' is set appropriately. |
|
|
72 |
!!ERRORS |
|
|
73 |
|
|
|
74 |
|
|
|
75 |
__EINVAL__ |
|
|
76 |
|
|
|
77 |
|
|
|
78 |
The parameter ''policy'' does not identify a defined |
|
|
79 |
scheduling policy. |
|
|
80 |
!!CONFORMING TO |
|
|
81 |
|
|
|
82 |
|
|
|
83 |
POSIX.1b (formerly POSIX.4) |
|
|
84 |
!!SEE ALSO |
|
|
85 |
|
|
|
86 |
|
4 |
perry |
87 |
sched_setscheduler(2), __sched_getscheduler__(2), |
|
|
88 |
sched_setparam(2), |
|
|
89 |
sched_getparam(2) |
1 |
perry |
90 |
|
|
|
91 |
|
4 |
perry |
92 |
sched_setscheduler(2) has a description of the Linux |
1 |
perry |
93 |
scheduling scheme. |
|
|
94 |
|
|
|
95 |
|
|
|
96 |
''Programming for the real world - POSIX.4'' by Bill O. |
|
|
97 |
Gallmeister, O'Reilly |
|
|
98 |
'' |
|
|
99 |
IEEE Std 1003.1b-1993'' (POSIX.1b standard)'' |
|
|
100 |
ISO/IEC 9945-1:1996'' |
|
|
101 |
---- |