2. API synchronization behavior
The API provides memcpy/memset functions in both synchronous and asynchronous forms, the latter having an "Async" suffix. This is a misnomer as each function may exhibit synchronous or asynchronous behavior depending on the arguments passed to the function.
Memcpy
In the reference documentation, each memcpy function is categorized as synchronous or asynchronous, corresponding to the definitions below.
-
All transfers involving Unified Memory regions are fully synchronous with respect to the host.
-
For transfers from pageable host memory to device memory, a stream sync is performed before the copy is initiated. The function will return once the pageable buffer has been copied to the staging memory for DMA transfer to device memory, but the DMA to final destination may not have completed.
-
For transfers from pinned host memory to device memory, the function is synchronous with respect to the host.
-
For transfers from device to either pageable or pinned host memory, the function returns only once the copy has completed.
-
For transfers from device memory to device memory, no host-side synchronization is performed.
-
For transfers from any host memory to any host memory, the function is fully synchronous with respect to the host.
-
For transfers from device memory to pageable host memory, the function will return only once the copy has completed.
-
For transfers from any host memory to any host memory, the function is fully synchronous with respect to the host.
-
For all other transfers, the function is fully asynchronous. If pageable memory must first be staged to pinned memory, this will be handled asynchronously with a worker thread.