Nvidia原生Rust GPU编程可能减少CUDA锁定
问题概述
开发者担忧CUDA带来的供应商锁定、缺乏详尽的硬件文档以及缺乏易用的GPU核函数抽象工具,导致开发流程繁琐且难以跨平台迁移。
痛点标签
- 对CUDA的供应商锁定不满意
- 缺乏详细的硬件文档和接口说明
- 缺乏易用的GPU核函数抽象工具
待验证问题
- 是否愿意尝试使用基于Rust的GPU编程工具?
- 是否需要更详细的硬件文档来自行实现驱动?
- 当前的开发流程中是否有重复的手动内存管理工作?
证据
原话
I strongly dislike CUDA. Once you have allowed that proprietary cr*p into your C++ codebase, it is very hard to get rid, and you end up with code that is either tied to a single vendor or an #ifdef hell, probably both.The best way to program GPUs is face up to the reality that they are not the same machine as the CPU, write your kernels in separate files, and launch them manually, like in Metal, OpenCL, and D3D12, etc.
原话
Okay, so, GPUs are taking one more step towards being general purpose massively parallel machines. That's cool.What would be even cooler though would be for GPU vendors to start giving us the user manual. An I mean the real user manual, that explains how to use their piece of metal when all you have is that piece of metal. That means a precise description of the wire protocols, the data format of the buffers we send to & get from the GPU, the ISA of the cores we have access to, the relevant performance characteristics…In other words, enough information to write a state-of-the-art driver for any OS. That would be cool.
原话
Since NVIDIA owns huggingface now and huggingface has the excellent Candle [1] crate for inference on Rust, this seems like a good step towards nice native Rust kernels.[1] https://github.com/huggingface/candle
免责声明:本卡片由 AI 从社区讨论中提炼,属于「痛点证据」,是需求分析与验证的起点,不等同于「已验证的市场需求」。AI 存在分析局限,关键决策前请打开上方原始讨论人工复核。