the connection I'm making is that both sit on the same interface: the CUDA driver api (module load, launch, memcpy).
the paper is about compiling kernels using safe rust instead of CUDA C++, what I did is reimplement the other side of it using rust for the calls from inside a VM get forwarded over vsock to the host driver via api-remoting.
Comments
Fascinating how many people still overcomplicate offloading to GPUs.
How so? I don’t know anything about this area.
What's the easy way here? Linking CUDA into your Rust binary?
:)
This might be an relevant read: https://smolmachines.com/engineering/gpu-over-vsock
I just read this tool up and down but still can't conceive of a use case.
that's fair
the connection I'm making is that both sit on the same interface: the CUDA driver api (module load, launch, memcpy).
the paper is about compiling kernels using safe rust instead of CUDA C++, what I did is reimplement the other side of it using rust for the calls from inside a VM get forwarded over vsock to the host driver via api-remoting.
I have no idea how spinning up a MicroVM solves the problems this paper talks about and I doubt you actually have programmed GPU kernels ever
happy to learn
Today I learn through GPU MODE & their discord: https://www.gpumode.com/events
I've only built toy kernels to experiment with supporting remoting CUDA workloads on smolvm: https://github.com/smol-machines/smolvm/blob/6dcb182d7fbc9f5...
No, it’s not relevant to simple GPU offload, stop spam linking your slop blog.
Will take it to heart