Close task signaling for critical execution paths

Abstract

Embodiments include computing devices, systems, and methods for task signaling on computing devices. The execution of the task by the initiating thread on the critical execution path can be interrupted to create at least one parallel task by the initiating thread, wherein the at least one parallel task can be executed in parallel with the task executed by the initiating thread. The start thread may send a start signal indicating to the relay thread the creation of the at least one parallel task. Before acquiring the at least one parallel task, execution of the task by the initiating thread may be resumed.

Description

Background technique [0001] Building responsive, performant, and efficient applications is critical to providing a satisfying user experience. To improve performance and power efficiency, parallel portions of a program may be executed by one or more threads running on one or more computing cores, central processing units (CPUs), graphics processing units (GPUs), or other parallel hardware. Typically, one thread, called the "main thread," enters the parallel section, creates helper tasks, and notifies other threads to help execute the parallel section. [0002] Although task creation is usually inexpensive, notifying other threads can be relatively expensive since it usually involves operating system calls. For example, in a top-of-the-line quad-core smartphone, the latency of a signal thread waiting on a condition variable can be as high as 40 microseconds (roughly 90,000 CPU cycles). Each of several parallel sections of code may take 40 microseconds to execute, making this ...

AI Technical Summary

Problems solved by technology

Each of several parallel parts of the code may take 40 microseconds to execute, making this high signaling cost unacceptable for parallel execution

Images