-
Notifications
You must be signed in to change notification settings - Fork 25.4k
Open
Labels
enhancementNot as big of a feature, but technically not a bug. Should be easy to fixNot as big of a feature, but technically not a bug. Should be easy to fixmodule: vulkanneeds researchWe need to decide whether or not this merits inclusion, based on research worldWe need to decide whether or not this merits inclusion, based on research worldtriagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleThis issue has been looked at a team member, and triaged and prioritized into an appropriate module
Description
🚀 The feature, motivation and pitch
Vulkan-PyTorch interoperability including zero-copy data transfer on GPU (Cuda <-> Vulkan).
I am working on a real-time machine learning graphics project which uses Vulkan (or OpenGL) both as an intermediate processing step in the model and to visualize the output. But the problem is transferring data between PyTorch/Cuda and Vulkan. I can copy data from PyTorch/cuda to CPU and then back to Vulkan on GPU but this is prohibitively slow.
This feature would simplify a lot of interesting research into machine learning graphics.
Alternatives
No response
Additional context
- Vulkan can be used from Python with e.g.: https://github.com/realitix/vulkan
- As Vulkan is a backend to ExecuTorch maybe this feature wouldn't be to far from what is currently being worked on
Metadata
Metadata
Assignees
Labels
enhancementNot as big of a feature, but technically not a bug. Should be easy to fixNot as big of a feature, but technically not a bug. Should be easy to fixmodule: vulkanneeds researchWe need to decide whether or not this merits inclusion, based on research worldWe need to decide whether or not this merits inclusion, based on research worldtriagedThis issue has been looked at a team member, and triaged and prioritized into an appropriate moduleThis issue has been looked at a team member, and triaged and prioritized into an appropriate module