|
|
|
|
|
by dahart
206 days ago
|
|
This article has good info, but is the overloading premise slightly contrived? Maybe I don’t talk to enough CUDA beginners. I work with CUDA a lot but I’m not exactly a CUDA expert, and from my perspective, in practice there are default assumptions one can safely make for the base terms, and people do qualify the alternatives almost always. For example, if someone says “CUDA version”, they always mean the toolkit, and never mean compute capability, runtime, or language. The term “driver” when used without qualification always means the display driver, and never means the driver API, there really is no overload there. |
|
"The CUDA "driver version" looks like the CUDA runtime version - so what's the difference?" https://stackoverflow.com/q/40589814/1593077
or consider the version you get when you run nvidia-smi, versus the version you get when you run nvcc --version. Those are very different numbers...
The compatibility between different versions of the driver and the toolkit is also a cause for some headaches in my experience.