[FEA]: Prototype a design to ensure asynchronous operations on different streams work nicely with cuda::launch
#2143
Labels
2.7.0
Targeted for 2.7.0 release
CUDA Next
Feature intended for the Cuda Next experimental library
feature request
New feature or request.
Asynchronous operations are notoriously difficult.
We need to ensure that any memory allocation that we got from
cudaMallocAsync
is actually valid when we are trying to access it.Furthermore, we could have different streams interacting with a kernel, so we need to come up with a design that allows
cuda::launch
to synchronize when neccessaryTasks
cuda::launch
for their stream dependency #2206cuda::launch
to optionally synchronize with other streamsThe text was updated successfully, but these errors were encountered: