libgomp: GOMP_RTEMS_THREAD_POOLS
1
1 3.19 'GOMP_RTEMS_THREAD_POOLS' - Set the RTEMS specific thread pools
1 ====================================================================
1
1 _Description_:
1 This environment variable is only used on the RTEMS real-time
1 operating system. It determines the scheduler instance specific
1 thread pools. The format for 'GOMP_RTEMS_THREAD_POOLS' is a list
1 of optional '<thread-pool-count>[$<priority>]@<scheduler-name>'
1 configurations separated by ':' where:
1 * '<thread-pool-count>' is the thread pool count for this
1 scheduler instance.
1 * '$<priority>' is an optional priority for the worker threads
1 of a thread pool according to 'pthread_setschedparam'. In
1 case a priority value is omitted, then a worker thread will
1 inherit the priority of the OpenMP master thread that created
1 it. The priority of the worker thread is not changed after
1 creation, even if a new OpenMP master thread using the worker
1 has a different priority.
1 * '@<scheduler-name>' is the scheduler instance name according
1 to the RTEMS application configuration.
1 In case no thread pool configuration is specified for a scheduler
1 instance, then each OpenMP master thread of this scheduler instance
1 will use its own dynamically allocated thread pool. To limit the
1 worker thread count of the thread pools, each OpenMP master thread
1 must call 'omp_set_num_threads'.
1 _Example_:
1 Lets suppose we have three scheduler instances 'IO', 'WRK0', and
1 'WRK1' with 'GOMP_RTEMS_THREAD_POOLS' set to '"1@WRK0:3$4@WRK1"'.
1 Then there are no thread pool restrictions for scheduler instance
1 'IO'. In the scheduler instance 'WRK0' there is one thread pool
1 available. Since no priority is specified for this scheduler
1 instance, the worker thread inherits the priority of the OpenMP
1 master thread that created it. In the scheduler instance 'WRK1'
1 there are three thread pools available and their worker threads run
1 at priority four.
1