That’s an even bigger problem that I first thought then.
On Linux, DRM is used by every other major GPU vendor to mediate access so that the process holding DRM master access can always take priority, potentially allowing desktop workloads to still function alongside compute even if you’re spanking a card to its fullest. Software is still required to use the DRM render node device file (e.g. /dev/dri/renderD128) even to perform compute, whether it be Vulkan or OpenCL or any other API, making every workload subject to kernel GPU scheduling algorithms.
On Windows, everything (even CUDA) is still subject to the whims of WDDM and its included GPU scheduling algorithms, so if I absolutely spank every drop of resources, I’m still able to use my computer for other interactive purposes, because built-in scheduling of each workload ensures other applications get their fair share of access to the card’s resources. With each improvement Microsoft makes, every vendor driver benefits automatically.