Skip to content
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

In the presence of multiple OpenCL types, Milkyway runs on the wrong GPU #132

Open
piedar opened this issue Sep 24, 2022 · 0 comments
Open

Comments

@piedar
Copy link

piedar commented Sep 24, 2022

A machine has multiple OpenCL GPUs, which BOINC reports like this.

OpenCL: NVIDIA GPU 0: NVIDIA GeForce GTX 1050 (driver version 515.65.01, device version OpenCL 3.0 CUDA, 2000MB, 2000MB available, 1911 GFLOPS peak)
OpenCL: AMD/ATI GPU 0: AMD Radeon Vega 8 Graphics (raven, LLVM 14.0.6, DRM 3.42, 5.15.6 (driver version 22.1.7, device version OpenCL 1.1 Mesa 22.1.7, 3072MB, 3072MB available, 704 GFLOPS peak)

BOINC downloads tasks for both NVIDIA and AMD, but Milkyway runs both tasks on the NVIDIA GPU (as shown by nvidia-smi) and leaves the AMD device idle. According to BOINC/boinc#1641 Milkyway should be using gpu_opencl_dev_index rather than the raw numeric device index.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant