aclrtSubscribeReport
Applicability
|
Product |
Supported |
|---|---|
|
Atlas 350 Accelerator Card |
√ |
|
|
√ |
|
|
√ |
|
|
√ |
|
|
√ |
|
|
√ |
Description
Subscribes to a thread for handling the callback function in a stream.
- Define and implement a callback function. Function prototype: typedef void (*aclrtCallback)(void *userData)
- Create a thread. Call aclrtProcessReport in the thread function to set the timeout interval (cyclic calling is required), and wait for the callback task execution.
- Call aclrtSubscribeReport to bind the thread created in Step 2 to the stream. The callback function delivered by the stream is executed in the bound thread.
- Execute an asynchronous task (for example, an asynchronous inference job) on the specified stream.
- Call aclrtLaunchCallback to deliver a callback task in the task queue of the stream and trigger the thread created in step 2 to process the callback function. Each time aclrtLaunchCallback is called, the callback function is executed.
- After all asynchronous tasks are executed, call aclrtUnSubscribeReport to unsubscribe from the thread.
Prototype
1
|
aclError aclrtSubscribeReport(uint64_t threadId, aclrtStream stream) |
Parameters
|
Parameter |
Input/Output |
Description |
|---|---|---|
|
threadId |
Input |
Thread ID. |
|
stream |
Input |
Stream. For details about the type definition, see aclrtStream. |
Returns
0 on success; otherwise, failure. For details, see aclError.
Restrictions
Calling aclrtSubscribeReport multiple times to register the same callback thread for multiple streams is supported (restricted to multiple streams within the same device); To ensure that tasks within a stream are executed in the order of invocation, registering multiple callback threads for a single stream via aclrtSubscribeReport is not supported; Within the same process, the same thread ID cannot be specified when registering callback threads across different devices.
If the number of threads subscribed by this call in a single process exceeds a specified limit, a failure code is returned. Considering the thread switching performance overhead of the OS, try to keep the number of threads subscribed by the aclrtSubscribeReport call within 32. The maximum number of threads supported by each product model varies, as shown in the following table.
|
Model |
Maximum Threads |
|---|---|
|
Atlas 350 Accelerator Card |
1024 |