Threads Library Options

The POSIX standard for the threads library specifies the implementation of some parts as optional. All subroutines defined by the threads library API are always available. Depending on the available options, some subroutines may not be implemented. Unimplemented subroutines can be called by applications, but they always return the ENOSYS error code.

Read the following to learn more about threads library options:

• List of Options.
• Checking the Availability of an Option.

List of Options

The following options are defined:

• Stack address
• Stack size
• Priority scheduling
• Priority inheritance
• Priority protection
• Process sharing.

The priority inheritance and priority protection options require the implementation of the priority scheduling option.

Stack Address POSIX Option

The stack address option enables the control of the stackaddr attribute of a thread attributes object. This attribute specifies the location of storage to be used for the created thread's stack. See "Stack Address for more information about the stackaddr attribute.

The following attribute and subroutines are available when the option is implemented:

• The stackaddr attribute of the thread attributes object
• The pthread_attr_getstackaddr and pthread_attr_setstackaddr subroutines.

This option is not implemented in AIX Version 4.1 at this time.

Stack Size POSIX Option

The stack size option enables the control of the stacksize attribute of a thread attributes object. This attribute specifies the minimum stack size to be used for the created thread. See "Stack Size for more information about the stacksize attribute.

The following attribute and subroutines are available when the option is implemented:

• The stacksize attribute of the thread attributes object
• The pthread_attr_getstacksize and pthread_attr_setstacksize subroutines.

This option is implemented in AIX.

Priority Scheduling POSIX Option

The priority scheduling option enables the control of execution scheduling at thread level. When this option is disabled, all threads within a process share the scheduling properties of the process. When this option is enabled, each thread has its own scheduling properties. For local contention scope threads, the scheduling properties are handled at process level by a library scheduler, while for global contention scope threads, the scheduling properties are handled at system level by the kernel scheduler. See "Threads Scheduling" to get more information about the scheduling properties of a thread.

The attributes and subroutines shown below are available when the option is implemented:

• The inheritsched attribute of the thread attributes object
• The schedparam attribute of the thread attributes object and the thread
• The schedpolicy attribute of the thread attributes objects and the thread
• The contention-scope attribute of the thread attributes objects and the thread
• The pthread_attr_getschedparam and pthread_attr_setschedparam subroutines
• The pthread_getschedparam subroutine.

This option is implemented in AIX.

Priority Inheritance POSIX Option

The priority inheritance option enables the use of the priority inheritance protocol to prevent priority inversions. This option allows thread deadlines to be guaranteed even in the presence of synchronization requirements; it prevents priority inversions, lower-priority threads blocking higher-priority threads by holding a mutex.

The following attribute and subroutines are available when the option is implemented:

• The protocol attribute of the mutex attributes object and the mutex

This option is not implemented in AIX Version 4.1 at this time.

Priority Protection POSIX Option

The priority protection option enables the usage of the priority protection protocol to prevent priority inversions. When the priority inheritance protocol is enabled, this option adds a second protocol; otherwise, it is not available. This protocol requires one more attribute to store the priority ceiling.

The following attribute and subroutines are available when the option is implemented:

• The prioceiling attribute of the mutex attributes objects and mutexes.

This option is not implemented in AIX Version 4.1 at this time.

Process Sharing POSIX Option

The process sharing option enables synchronization objects (mutexes and condition variables) to be shared among different processes. It provides highly efficient synchronization facilities to processes.

The following attribute and subroutines are available when the option is implemented:

• The process-shared attribute of the mutex attributes objects, mutexes, condition attributes objects, and condition variables.
• The pthread_mutexattr_getpshared and pthread_mutexattr_setpshared subroutines.
• The pthread_condattr_getpshared and pthread_condattr_setpshared subroutines.

This option is not implemented in AIX Version 4.1 at this time.

Checking the Availability of an Option

Options can be checked at compile time or at run time. Portable programs should check the availability of options before using them, so that they do not need to be rewritten when ported to other systems.

Compile Time Checking

Symbolic constants (symbols) can be used to get the availability of options on the system where the program is compiled. The symbols are defined in the pthread.h header file by the #define pre-processor command. For unimplemented options, the corresponding symbol is undefined by the #undef pre-processor command. Checking option symbols should be done in each program that may be ported to another system.

The following list indicates the symbol associated with each option:

The simplest action to take when an option is not available is to stop the compilation, as in the following example:

#ifndef _POSIX_THREAD_ATTR_STACKSIZE
#error "The stack size POSIX option is required"
#endif

The pthread.h header file also defines the following symbols that can be used by other header files or by programs:

Run Time Checking

The sysconf subroutine can be used to get the availability of options on the system where the program is executed. This is useful when porting programs between systems that have a binary compatibility, such as two versions of AIX.

The following list indicates the symbolic constant associated with each option and that must be used for the Name parameter of the sysconf subroutine. The symbolic constants are defined in the unistd.h header file.

Two general options may also be checked using the sysconf subroutine with the following Name parameter values:

Related Information

Understanding Threads.

Threads Programming Overview.

Threads Library Quick Reference.