| /oneTBB/include/oneapi/tbb/detail/ |
| H A D | _concurrent_skip_list.h | 129 node_ptr next( size_type level ) const { in next() argument
169 return arr[level]; in get_atomic_next()
174 return arr[level]; in get_atomic_next()
587 for (size_type level = 0; level < head->height(); ++level) { in clear() local
865 curr = prev->next(level); in internal_find_position()
885 curr = prev->next(level); in internal_find_position()
902 for (size_type level = curr_max_height; level > 0; --level) { in fill_prev_curr_arrays() local
914 for (size_type level = node->height(); level > 0; --level) { in fill_prev_array_for_existing_node() local
991 for (std::size_t level = 1; level < new_height; ++level) { in internal_insert_node() local
1045 for (size_type level = 0; level < erase_node->height(); ++level) { in internal_extract() local
[all …]
|
| /oneTBB/doc/main/tbb_userguide/ |
| H A D | Summary_of_Loops_and_Pipelines.rst | 6 The high-level loop and pipeline templates in |full_name|
8 They let you design your software at a high task-pattern level and not worry about low-level manipu…
|
| H A D | Task-Based_Programming.rst | 25 - Higher–level thinking
55 level (though its logical thread can be preempted).
62 to undertake without understanding the higher-level organization of a
64 higher-level information, and so can sacrifice fairness for efficiency.
85 they let you think at a higher, task-based, level. With thread-based
86 programming, you are forced to think at the low level of physical
|
| H A D | work_isolation.rst | 13 construct, a thread can obtain a task from the outer-level construct
14 while waiting for completion of the inner-level one.
67 One of these ways is to execute the inner level loop in a separate
99 thread is prohibited from executing any outer level tasks or tasks
|
| H A D | Summary_of_Containers.rst | 7 The high-level containers in |full_name|
|
| H A D | Mac_OS.rst | 6 This section uses *<install_dir>* to indicate the top-level installation directory.
|
| H A D | The_Task_Scheduler.rst | 12 onto one of the high-level templates, use the task scheduler.
|
| H A D | Linux_OS.rst | 7 This section uses *<tbb_install_dir>* to indicate the top-level
|
| H A D | Floating_Point_Settings.rst | 36 … a task group with explicitly captured floating-point settings, the outer-level settings are used.
37 If none of the outer-level contexts capture floating-point settings, the settings captured during t…
|
| H A D | Windows_OS_ug.rst | 6 This section uses <*tbb_install_dir*> to indicate the top-level
|
| H A D | Containers.rst | 21 Containers provided by oneTBB offer a much higher level of concurrency,
|
| H A D | use_nested_algorithms.rst | 10 coarse-grained parallelism at the level of the graph, with finer grained
|
| H A D | Predefined_Node_Types.rst | 29 … and output types. Executes a user body, and has controllable concurrency level and buffering poli…
33 …output types. It executes a user body, and has controllable concurrency level and buffering poli…
|
| H A D | Cancellation_and_Nested_Parallelism.rst | 79 If your code catches the exception at any level, then oneTBB does not
|
| H A D | Concurrent_Queue_Classes.rst | 63 appropriate when the synchronization has to be done at a higher level.
|
| H A D | Guiding_Task_Scheduler_Execution.rst | 26 - The level of ``task_arena`` concurrency
|
| /oneTBB/examples/parallel_for/tachyon/src/ |
| H A D | ui.cpp | 70 void rt_ui_message(int level, const char *msg) { in rt_ui_message() argument
78 rt_static_ui_message(level, msg); in rt_ui_message()
|
| /oneTBB/doc/main/tbb_userguide/design_patterns/ |
| H A D | Non-Preemptive_Priorities.rst | 63 interface for it and top-level implementation follow:
127 // One queue for each priority level
128 oneapi::tbb::concurrent_queue<WorkItem*> level[P_Low+1];
132 level[item->priority].push(item);
139 if( level[i].try_pop(item) )
|
| H A D | Fenced_Data_Transfer.rst | 25 to create synchronization. High level synchronization constructs
127 Higher level synchronization constructs normally include the
|
| /oneTBB/doc/main/intro/ |
| H A D | Benefits.rst | 17 The advantage of oneTBB is that it works at a higher level than raw
26 inefficient programs, because threads are low-level, heavy constructs
37 result, general-purpose packages tend to be low-level tools that
40 delivering higher-level, simpler solutions.
|
| /oneTBB/.github/scripts/ |
| H A D | codespell.sh | 54 SCAN_RESULT=`codespell --quiet-level=2 --skip "${SKIP_PATTERN}" ${SCAN_TARGET}`
|
| /oneTBB/test/tbb/ |
| H A D | test_scheduler_mix.cpp | 387 int level{}; member
481 ts.arenaIdxStack[ts.level++] = int(idx); in acquire()
497 CHECK_FAST(ts.level > 0); in release()
498 auto idx = ts.arenaIdxStack[--ts.level]; in release()
|
| H A D | test_eh_algorithms.cpp | 559 int DoWork (int level);
598 int Worker::DoWork ( int level ) { in DoWork() argument
599 ++level; in DoWork()
600 if ( level < max_nesting ) { in DoWork()
601 RecursiveParReduceBodyWithSharedWorker rt (this, level); in DoWork()
|
| /oneTBB/doc/main/tbb_userguide/Migration_Guide/ |
| H A D | Task_API.rst | 3 Migrating from low-level task API
6 The low-level task API of Intel(R) Threading Building Blocks (TBB) was considered complex and hence
8 (oneTBB). This guide helps with the migration from TBB to oneTBB for the use cases where low-level
95 the execution of a parallel algorithm were mostly covered by ``tbb::parallel_do`` high-level
393 The TBB low-level task API separates the task creation from the actual spawning. This separation al…
|
| /oneTBB/cmake/compilers/ |
| H A D | MSVC.cmake | 32 …# https://docs.microsoft.com/en-us/cpp/error-messages/compiler-warnings/compiler-warning-level-1-c…
|