Lines Matching refs:to

6 By default, the task scheduler tries to use all available computing resources. In some cases,
7 you may want to configure the task scheduler to use only some of them.
13 |full_name| provides the ``task_arena`` interface to guide tasks execution within the arena by:
18 To set the limitation, you have to customize the ``task_arena::constraints`` and then pass
19 it to the ``task_arena`` instance during the construction or initialization.
21 The structure ``task_arena::constraints`` allows to specify the following restrictions:
28 You may use the interfaces from ``tbb::info`` namespace to construct the ``tbb::task_arena::constra…
33 The following examples show how to use these interfaces:
40 instances, whose execution preference is set to different NUMA nodes. To set execution preference,
41 assign a NUMA node identifier to the ``task_arena::constraints::numa_id`` field.
66 To set the preferred core type for the execution, assign a specific core type identifier to the ``t…
68 The example shows how to set the most performant core type as preferable for work execution:
81 .. rubric:: Limiting the maximum number of threads simultaneously scheduled to one core
84 allow more than one thread to run on each core simultaneously. However, there might be situations
85 when there is need to lower the number of simultaneously running threads per core. In such cases,
86 assign the desired value to the ``task_arena::constraints::max_threads_per_core`` field.
88 The example shows how to allow only one thread to run on each core at a time:
97 A more composable way to limit the number of threads executing on cores is by setting the maximal
110 Similarly to the previous example, the number of threads inside the arena is equal to the