3 ms·
Isnt this what intels trying to do with OneAPI?
by 7speter 3y ago
Isnt this what intels trying to do with OneAPI?
- smoldesu 3y agoYeah, but a lot of other companies have similar libraries with varying levels of commitment/coverage. ARM has ARMnn, Apple has CoreML, Intel has both Vino and OneAPI (plus SSE/AVX implementations), Google has NNAPI for Android and Google Cloud tensor accelerators, AMD has... Vitis/Xilinix, ROCm, OpenCL and MIGraphX, Windows has DirectML/Olive alongside Microsoft's Azure Execution Providers, Rockchip has RKNPU and Huawei has CANN. Suffice to say, there are a lot of "competing standards" a-la the XKCD : https://xkcd.com/927/ https://xkcd.com/927/ I don't think any of those will really topple CUDA, though. The best way to unseat Nvidia's dominance would be to target their two weaknesses; the closed nature of CUDA and the lock-in to Nvidia hardware. It would be difficult to overturn them both, but an open and fast CUDA alternative is really all people actually want. That's why I think libraries like ONNX have the right idea; instead of relying on chip manufacturers to not rip each other's throats out (they won't), they unify everyone's proprietary APIs. Barring some ground-up GPGPU library like OpenCL, this seems like the smartest path to me.