-
Notifications
You must be signed in to change notification settings - Fork 83
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Handle Windows TCC/WDDM mode more robustly #206
Comments
Can't we just say the pool is not available on Windows in TCC mode? I don't think we need to go above and beyond to support something the driver doesn't support. |
It is not appropriate because CUDA does support Windows TCC mode, just not the mempool. Right now @jrhemstad I suggest us to take this seriously if we want CUDA Mode to succeed, as we have many Windows TCC users in the LLM space, and they all hit this issue (it only took me 1 min to quickly google these): |
#209 is related (the 3rd step we should take in the future to address this issue). |
Another reason that TCC is important is because it's the default of GHA Windows GPU runner, e.g.: |
This issue tracks an internal discussion with QA. This simple snippet shows why using
cuda.core
today on Windows might fail, depending on if it's TCC or WDDM mode:cuda.core
currently assumes the stream-ordered memory allocator is available. However, CUDA on Windows is a bit more complicated than on Linux, since there are two operation modes:cuda.core
development), things should work just fine.We need some treatments to make it usable on TCC.
The text was updated successfully, but these errors were encountered: