pthread_attr_setinheritsched, pthread_attr_getinheritsched - set/get
inherit-scheduler attribute in thread attributes object
int pthread_attr_setinheritsched(pthread_attr_t *attr,
int pthread_attr_getinheritsched(const pthread_attr_t *attr,
Compile and link with -pthread.
() function sets the inherit-scheduler
attribute of the thread attributes object referred to by attr
value specified in inheritsched
. The inherit-scheduler attribute
determines whether a thread created using the thread attributes object
will inherit its scheduling attributes from the calling thread or
whether it will take them from attr
The following scheduling attributes are affected by the inherit-scheduler
attribute: scheduling policy (pthread_attr_setschedpolicy(3)
scheduling priority (pthread_attr_setschedparam(3)
), and contention
The following values may be specified in inheritsched
- Threads that are created using attr inherit scheduling attributes
from the creating thread; the scheduling attributes in attr are
- Threads that are created using attr take their scheduling
attributes from the values specified by the attributes object.
The default setting of the inherit-scheduler attribute in a newly initialized
thread attributes object is PTHREAD_INHERIT_SCHED
() returns the inherit-scheduler
attribute of the thread attributes object attr
in the buffer pointed to
On success, these functions return 0; on error, they return a nonzero error
() can fail with the following error:
- Invalid value in inheritsched.
POSIX.1-2001 also documents an optional ENOTSUP
error ("attempt was
made to set the attribute to an unsupported value") for
Multithreading (see pthreads(7))¶
() functions are thread-safe.
As at glibc 2.8, if a thread attributes object is initialized using
, then the scheduling policy of the attributes
object is set to SCHED_OTHER
and the scheduling priority is set to 0.
However, if the inherit-scheduler attribute is then set to
, then a thread created using the attribute
object wrongly inherits its scheduling attributes from the creating thread.
This bug does not occur if either the scheduling policy or scheduling priority
attribute is explicitly set in the thread attributes object before calling
This page is part of release 3.74 of the Linux man-pages
description of the project, information about reporting bugs, and the latest
version of this page, can be found at