3 ms·

Am I the only one who thinks that the API looks terrible? Lots of cryptic and hard-to-remember names (`cuMemcpyDtoHAsync`), no proper error and log handling, ma

Am I the only one who thinks that the API looks terrible? Lots of cryptic and hard-to-remember names (`cuMemcpyDtoHAsync`), no proper error and log handling, manual building of command line arguments (`opts = [b"--fmad=false", b"--gpu-architecture=compute_75"]` – wat), … And, knowing Nvidia, the documentation will probably be terrible and anything but beginner-friendly, too. I mean, if you want to improve upon the CUDA ecosystem why not start with the low-hanging fruit first?

somethingsome 6y ago
While those names are vestiges of the history, I would be curious how you would name cuMemcpyDtoHAsync? They have lots of functions [1] to name and I usually find they did a good job given the low level of the language and its proximity with the hardware and low level programming. I do not know for python but CUDA on C++ has error handling! As for the command line: think as you were programming for a specific architecture with its associated API [1] https://docs.nvidia.com/cuda/cuda-runtime-api/index.html https://docs.nvidia.com/cuda/cuda-runtime-api/index.html