-
Notifications
You must be signed in to change notification settings - Fork 28
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
Mark plugins as gpu capable #161
Comments
You should definitely mark the gpu apis supported in a list (are there multi api plugins? if not maybe skip that) since not all cards do CUDA. |
Or a more general option like device: ["cpu", "opencl"] where once again cpu only is assumed when not present. |
device sounds good, since there are plugins with both cpu and gpu support. There's also torch.cuda.is_available() but it's a "heavy" dependency. |
Found this https://gist.github.com/f0k/63a664160d016a491b2cbea15913d549#file-cuda_check-py-L60. Maybe looking for a cuda dll is enough? nvcuda.dll should be our dll |
Yes, nvcuda.dll existing sounds like enough. |
Step 1 is commited (just the tagging part) |
Since many plugins also use the GPU for processing, it would be nice to mark packages accordingly.
I was thinking something like this:
Maybe CUDA, VULKAN & OPENCL as options.
Or simply uses_gpu: yes
I don't think it makes much sense to mark it per release.
This would be then listed in vsrepo available / installed
What do you think?
The text was updated successfully, but these errors were encountered: