Intel® oneAPI Threading Building Blocks Developer Guide and API Reference
A newer version of this document is available. Customers should click here to go to the newest version.
Visible to Intel only — GUID: GUID-CB65B5E2-F9E1-46AC-B075-2461B6EC30C1
Visible to Intel only — GUID: GUID-CB65B5E2-F9E1-46AC-B075-2461B6EC30C1
Task Scheduler Bypass
Scheduler bypass is an optimization where you directly specify the next task to run. According to the rules of execution described in How Task Scheduler Works, the spawning of the new task to be executed by the current thread involves the next steps:
Push a new task onto the thread’s deque.
Continue to execute the current task until it is completed.
Take a task from the thread’s deque, unless it is stolen by another thread.
Steps 1 and 3 introduce unnecessary deque operations or, even worse, allow stealing that can hurt locality without adding significant parallelism. These problems can be avoided by using “Task Scheduler Bypass” technique to directly point the preferable task to be executed next instead of spawning it. When, as described in How Task Scheduler Works, the returned task becomes the first candidate for the next task to be executed by the thread. Furthermore, this approach almost guarantees that the task is executed by the current thread and not by any other thread.
Please note that at the moment the only way to use this optimization is to use preview feature of ``onepai::tbb::task_group`