]> git.ipfire.org Git - thirdparty/man-pages.git/blame - man2/sched_setattr.2
sched_setattr.2: tfix
[thirdparty/man-pages.git] / man2 / sched_setattr.2
CommitLineData
225d97f2
MK
1.\" Copyright (C) 2014 Michael Kerrisk <mtk.manpages@gmail.com>
2.\" and Copyright (C) 2014 Peter Zijlstra <peterz@infradead.org>
3.\"
4.\" %%%LICENSE_START(VERBATIM)
5.\" Permission is granted to make and distribute verbatim copies of this
6.\" manual provided the copyright notice and this permission notice are
7.\" preserved on all copies.
8.\"
9.\" Permission is granted to copy and distribute modified versions of this
10.\" manual under the conditions for verbatim copying, provided that the
11.\" entire resulting derived work is distributed under the terms of a
12.\" permission notice identical to this one.
13.\"
14.\" Since the Linux kernel and libraries are constantly changing, this
15.\" manual page may be incorrect or out-of-date. The author(s) assume no
16.\" responsibility for errors or omissions, or for damages resulting from
17.\" the use of the information contained herein. The author(s) may not
18.\" have taken the same level of care in the production of this manual,
19.\" which is licensed free of charge, as they might when working
20.\" professionally.
21.\"
22.\" Formatted or processed versions of this manual, if unaccompanied by
23.\" the source, must acknowledge the copyright and authors of this work.
24.\" %%%LICENSE_END
25.\"
4b8c67d9 26.TH SCHED_SETATTR 2 2017-09-15 "Linux" "Linux Programmer's Manual"
225d97f2
MK
27.SH NAME
28sched_setattr, sched_getattr \-
29set and get scheduling policy and attributes
30.SH SYNOPSIS
31.nf
32.B #include <sched.h>
dbfe9c70 33.PP
c3529e3b 34.BI "int sched_setattr(pid_t " pid ", struct sched_attr *" attr ,
225d97f2 35.BI " unsigned int " flags );
dbfe9c70 36.PP
4b081d8d 37.BI "int sched_getattr(pid_t " pid ", struct sched_attr *" attr ,
225d97f2
MK
38.BI " unsigned int " size ", unsigned int " flags );
39.fi
bea08fec 40.\" FIXME . Add feature test macro requirements
225d97f2
MK
41.SH DESCRIPTION
42.SS sched_setattr()
43The
44.BR sched_setattr ()
45system call sets the scheduling policy and
46associated attributes for the thread whose ID is specified in
47.IR pid .
48If
49.I pid
50equals zero,
51the scheduling policy and attributes of the calling thread will be set.
efeece04 52.PP
225d97f2
MK
53Currently, Linux supports the following "normal"
54(i.e., non-real-time) scheduling policies as values that may be specified in
55.IR policy :
56.TP 14
57.BR SCHED_OTHER
58the standard round-robin time-sharing policy;
59.\" In the 2.6 kernel sources, SCHED_OTHER is actually called
60.\" SCHED_NORMAL.
61.TP
62.BR SCHED_BATCH
63for "batch" style execution of processes; and
64.TP
65.BR SCHED_IDLE
66for running
67.I very
68low priority background jobs.
69.PP
70Various "real-time" policies are also supported,
71for special time-critical applications that need precise control over
72the way in which runnable threads are selected for execution.
73For the rules governing when a process may use these policies, see
74.BR sched (7).
75The real-time policies that may be specified in
76.IR policy
77are:
78.TP 14
79.BR SCHED_FIFO
80a first-in, first-out policy; and
81.TP
82.BR SCHED_RR
83a round-robin policy.
84.PP
85Linux also provides the following policy:
86.TP 14
87.B SCHED_DEADLINE
88a deadline scheduling policy; see
89.BR sched (7)
90for details.
91.PP
92The
93.I attr
94argument is a pointer to a structure that defines
95the new scheduling policy and attributes for the specified thread.
96This structure has the following form:
efeece04 97.PP
225d97f2 98.in +4n
b8302363 99.EX
225d97f2
MK
100struct sched_attr {
101 u32 size; /* Size of this structure */
102 u32 sched_policy; /* Policy (SCHED_*) */
103 u64 sched_flags; /* Flags */
104 s32 sched_nice; /* Nice value (SCHED_OTHER,
105 SCHED_BATCH) */
106 u32 sched_priority; /* Static priority (SCHED_FIFO,
107 SCHED_RR) */
108 /* Remaining fields are for SCHED_DEADLINE */
109 u64 sched_runtime;
110 u64 sched_deadline;
111 u64 sched_period;
112};
b8302363 113.EE
225d97f2 114.in
efeece04 115.PP
225d97f2
MK
116The fields of this structure are as follows:
117.TP
118.B size
119This field should be set to the size of the structure in bytes, as in
120.IR "sizeof(struct sched_attr)" .
121If the provided structure is smaller than the kernel structure,
122any additional fields are assumed to be '0'.
123If the provided structure is larger than the kernel structure,
124the kernel verifies that all additional fields are 0;
125if they are not,
126.BR sched_setattr ()
127fails with the error
128.BR E2BIG
129and updates
130.I size
131to contain the size of the kernel structure.
132.IP
133The above behavior when the size of the user-space
134.I sched_attr
135structure does not match the size of the kernel structure
136allows for future extensibility of the interface.
137Malformed applications that pass oversize structures
138won't break in the future if the size of the kernel
139.I sched_attr
140structure is increased.
141In the future,
142it could also allow applications that know about a larger user-space
143.I sched_attr
144structure to determine whether they are running on an older kernel
145that does not support the larger structure.
146.TP
147.I sched_policy
148This field specifies the scheduling policy, as one of the
149.BR SCHED_*
150values listed above.
151.TP
152.I sched_flags
c7456cdd
MK
153This field contains contains zero or more of the following flags
154that are ORed together to control scheduling behavior:
155.RS
156.TP
157.BR SCHED_FLAG_RESET_ON_FORK
158Children created by
225d97f2
MK
159.BR fork (2)
160do not inherit privileged scheduling policies.
161See
162.BR sched (7)
163for details.
c7456cdd
MK
164.TP
165.BR SCHED_FLAG_RECLAIM " (since Linux 4.13)"
166.\" 2d4283e9d583a3ee8cfb1cbb9c1270614df4c29d
167This flag allows a
87b4fd4b 168.BR SCHED_DEADLINE
a5e76996 169thread to reclaim bandwidth unused by other real-time threads.
927b72f4
MK
170.\" Bandwidth reclaim is done via the GRUB algorithm; see
171.\" Documentation/scheduler/sched-deadline.txt
c7456cdd
MK
172.TP
173.BR SCHED_FLAG_DL_OVERRUN " (since Linux 4.16)"
174.\" commit 34be39305a77b8b1ec9f279163c7cdb6cc719b91
5fa62195 175This flag allows an application to get informed about run-time overruns in
87b4fd4b 176.BR SCHED_DEADLINE
5fa62195
MK
177threads.
178Such overruns may be caused by (for example) coarse execution time accounting
b8bd34ac
MK
179or incorrect parameter assignment.
180Notification takes the form of a
c7456cdd 181.B SIGXCPU
b8bd34ac 182signal which is generated on each overrun.
5fa62195
MK
183.IP
184This
185.BR SIGXCPU
186signal is
187.I process-directed
188(see
189.BR signal (7))
190rather than thread-directed.
191This is probably a bug.
192On the one hand,
193.BR sched_setattr ()
194is being used to set a per-thread attribute.
195On the other hand, if the process-directed signal is delivered to
196a thread inside the process other than the one that had a run-time overrun,
197the application has no way of knowing which thread overran.
c7456cdd 198.RE
225d97f2
MK
199.TP
200.I sched_nice
201This field specifies the nice value to be set when specifying
202.IR sched_policy
203as
204.BR SCHED_OTHER
205or
206.BR SCHED_BATCH .
207The nice value is a number in the range \-20 (high priority)
208to +19 (low priority); see
9b7b2ea5 209.BR sched (7).
225d97f2
MK
210.TP
211.I sched_priority
212This field specifies the static priority to be set when specifying
213.IR sched_policy
214as
215.BR SCHED_FIFO
216or
217.BR SCHED_RR .
218The allowed range of priorities for these policies can be determined using
219.BR sched_get_priority_min (2)
220and
221.BR sched_get_priority_max (2).
222For other policies, this field must be specified as 0.
223.TP
224.I sched_runtime
225This field specifies the "Runtime" parameter for deadline scheduling.
226The value is expressed in nanoseconds.
227This field, and the next two fields,
228are used only for
0da5e58a 229.BR SCHED_DEADLINE
225d97f2
MK
230scheduling; for further details, see
231.BR sched (7).
232.TP
233.I sched_deadline
234This field specifies the "Deadline" parameter for deadline scheduling.
235The value is expressed in nanoseconds.
236.TP
237.I sched_period
238This field specifies the "Period" parameter for deadline scheduling.
239The value is expressed in nanoseconds.
240.PP
241The
242.I flags
243argument is provided to allow for future extensions to the interface;
244in the current implementation it must be specified as 0.
245.\"
246.\"
247.SS sched_getattr()
248The
249.BR sched_getattr ()
250system call fetches the scheduling policy and the
251associated attributes for the thread whose ID is specified in
252.IR pid .
253If
254.I pid
255equals zero,
256the scheduling policy and attributes of the calling thread
257will be retrieved.
efeece04 258.PP
225d97f2
MK
259The
260.I size
261argument should be set to the size of the
262.I sched_attr
263structure as known to user space.
264The value must be at least as large as the size of the initially published
265.I sched_attr
266structure, or the call fails with the error
267.BR EINVAL .
efeece04 268.PP
225d97f2
MK
269The retrieved scheduling attributes are placed in the fields of the
270.I sched_attr
271structure pointed to by
272.IR attr .
273The kernel sets
274.I attr.size
275to the size of its
276.I sched_attr
277structure.
efeece04 278.PP
225d97f2
MK
279If the caller-provided
280.I attr
281buffer is larger than the kernel's
282.I sched_attr
283structure,
284the additional bytes in the user-space structure are not touched.
285If the caller-provided structure is smaller than the kernel
286.I sched_attr
287structure and the kernel needs to return values outside the provided space,
288.BR sched_getattr ()
289fails with the error
290.BR E2BIG .
291As with
292.BR sched_setattr (),
293these semantics allow for future extensibility of the interface.
efeece04 294.PP
225d97f2
MK
295The
296.I flags
297argument is provided to allow for future extensions to the interface;
298in the current implementation it must be specified as 0.
299.SH RETURN VALUE
300On success,
301.BR sched_setattr ()
302and
303.BR sched_getattr ()
304return 0.
305On error, \-1 is returned, and
306.I errno
307is set to indicate the cause of the error.
308.SH ERRORS
309.BR sched_getattr ()
310and
311.BR sched_setattr ()
312can both fail for the following reasons:
313.TP
314.B EINVAL
315.I attr
316is NULL; or
317.I pid
318is negative; or
319.I flags
320is not zero.
321.TP
322.B ESRCH
323The thread whose ID is
324.I pid
325could not be found.
326.PP
327In addition,
328.BR sched_getattr ()
329can fail for the following reasons:
330.TP
331.B E2BIG
332The buffer specified by
333.I size
334and
335.I attr
336is too small.
337.TP
338.B EINVAL
339.I size
340is invalid; that is, it is smaller than the initial version of the
341.I sched_attr
342structure (48 bytes) or larger than the system page size.
343.PP
344In addition,
345.BR sched_setattr ()
346can fail for the following reasons:
347.TP
348.B E2BIG
349The buffer specified by
350.I size
351and
352.I attr
353is larger than the kernel structure,
354and one or more of the excess bytes is nonzero.
355.TP
356.B EBUSY
357.B SCHED_DEADLINE
358admission control failure, see
359.BR sched (7).
360.TP
361.B EINVAL
362.I attr.sched_policy
363is not one of the recognized policies;
364.I attr.sched_flags
365contains a flag other than
366.BR SCHED_FLAG_RESET_ON_FORK ;
367or
368.I attr.sched_priority
369is invalid; or
370.I attr.sched_policy
371is
372.BR SCHED_DEADLINE
373and the deadline scheduling parameters in
374.I attr
375are invalid.
376.TP
377.B EPERM
378The caller does not have appropriate privileges.
379.TP
380.B EPERM
4a6f17b5
MK
381The CPU affinity mask of the thread specified by
382.I pid
225d97f2
MK
383does not include all CPUs in the system
384(see
385.BR sched_setaffinity (2)).
386.SH VERSIONS
387These system calls first appeared in Linux 3.14.
bea08fec 388.\" FIXME . Add glibc version
225d97f2
MK
389.SH CONFORMING TO
390These system calls are nonstandard Linux extensions.
391.SH NOTES
392.BR sched_setattr ()
393provides a superset of the functionality of
394.BR sched_setscheduler (2),
395.BR sched_setparam (2),
396.BR nice (2),
397and (other than the ability to set the priority of all processes
398belonging to a specified user or all processes in a specified group)
399.BR setpriority (2).
400Analogously,
1b05b97a 401.BR sched_getattr ()
225d97f2
MK
402provides a superset of the functionality of
403.BR sched_getscheduler (2),
404.BR sched_getparam (2),
405and (partially)
406.BR getpriority (2).
407.SH BUGS
408In Linux versions up to
bea08fec 409.\" FIXME . patch sent to Peter Zijlstra
225d97f2
MK
4103.15,
411.BR sched_settattr ()
412failed with the error
413.BR EFAULT
414instead of
415.BR E2BIG
416for the case described in ERRORS.
417.\" In Linux versions up to up 3.15,
bea08fec 418.\" FIXME . patch from Peter Zijlstra pending
225d97f2
MK
419.\" .BR sched_setattr ()
420.\" allowed a negative
421.\" .I attr.sched_policy
422.\" value.
423.SH SEE ALSO
424.ad l
425.nh
ac30de07 426.BR chrt (1),
225d97f2
MK
427.BR nice (2),
428.BR sched_get_priority_max (2),
429.BR sched_get_priority_min (2),
430.BR sched_getaffinity (2),
225d97f2 431.BR sched_getparam (2),
03768726 432.BR sched_getscheduler (2),
225d97f2
MK
433.BR sched_rr_get_interval (2),
434.BR sched_setaffinity (2),
225d97f2 435.BR sched_setparam (2),
03768726 436.BR sched_setscheduler (2),
225d97f2
MK
437.BR sched_yield (2),
438.BR setpriority (2),
439.BR pthread_getschedparam (3),
440.BR pthread_setschedparam (3),
441.BR pthread_setschedprio (3),
442.BR capabilities (7),
443.BR cpuset (7),
444.BR sched (7)
445.ad