Async/Await on the GPU
vectorware.com
Async/Await on the GPU
1–10 of 61 posts
Re: Async/Await on the GPU
#2Re: Async/Await on the GPU
#3Re: Async/Await on the GPU
#4I'm not quite seeing the real benefit of this. Is the idea that warps will now be able to do work-stealing and continuation-stealing when running heterogenous parallel workloads? But that requires keeping the async function's state in GPU-wide shared memory, which is generally a scarce resource.
GPU-wide memory is not quite as scarce on datacenter cards or systems with unified memory. One could also have local executors with local futures that are `!Send` and place in a faster address space.
Re: Async/Await on the GPU
#5Re: Async/Await on the GPU
#6Re: Async/Await on the GPU
#7What's the performance like? What would the benefits be of converting a streaming multiprocessor programming model to this?
The anticipated benefits are similar to the benefits of async/await on CPU: better ergonomics for the developer writing concurrent code, better utilization of shared/limited resources, fewer concurrency bugs.
Re: Async/Await on the GPU
#8Is this Nvidia-only or does it work on other architectures?
Re: Async/Await on the GPU
#9Is this Nvidia-only or does it work on other architectures?
Currently NVIDIA-only, we're cooking up some Vulkan stuff in rust-gpu though.
In years prior I wouldn't have even bothered, but it's 2026 and AMD's drivers actually come with a recent version of torch that 'just works' on windows. Anything is possible :)
Re: Async/Await on the GPU
#10Is the goal with this project (generally, not specifically async) to have an equivalent to e.g. CUDA, but in Rust? Or is there another intended use-case that I'm missing?