3 ms·
What surprises me is that the approaches to making cross-platform GPU computing work are so much focused on one specific use-case, ML. It's like someone builds
by amelius 4y ago
What surprises me is that the approaches to making cross-platform GPU computing work are so much focused on one specific use-case, ML.
It's like someone builds a CPU with a floating point unit specifically aimed at CAD software. Then someone else comes and builds a floating point unit for physics simulation. Then someone else ...
Can't we just get a generic compute model, and make that work everywhere? And don't we already have that, e.g. CUDA?
- MereInterest 4y agoWhile the use cases are tailed for machine learning, that isn't as much of a limitation as it sounds. The computationally-heavy portions of a machine-learning model are usually matrix multiplication and/or convolutions. The low-level operations could be combined into the training/evaluation of a machine-learning model, or could be combined into a physics simulation. That they are marketed as ML co-processors doesn't restrict their usage, just as a "graphics processing unit" isn't restricted to use for graphics.
- amelius 4y agoYeah, but that kind of marketing sucks to some extent because if they say they support A then as a consumer you don't know if they will support B now and in the future.
- UncleEntity 4y ago> It's like someone builds a CPU with a floating point unit specifically aimed at CAD software. Then someone else comes and builds a floating point unit for physics simulation. Then someone else ... The history of GPGPU in a nutshell… There are a few “generic compute models” but no incentive for the GPU manufacturers to support them over their proprietary model. Everyone could natively support Cuda and Vulcan and Metal and OpenCL and SPIR-V and…think I’m forgetting one but you get the point.