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

GPU module CUDA forced load #177

Open
bouthilx opened this issue Nov 8, 2017 · 0 comments
Open

GPU module CUDA forced load #177

bouthilx opened this issue Nov 8, 2017 · 0 comments

Comments

@bouthilx
Copy link
Collaborator

bouthilx commented Nov 8, 2017

We faced a problem with the default module in GPU queues on Cedar. I added a CUDA module in the Cedar config just it's done for others clusters (helios example), but the our lab stack CUDA is conflicting with the module loaded by SmartDispatch. I understand adding the module to queues is convenient because most of the people need that to use the GPU, but what if the user wants something else? In best case, module is loaded uselessly, but in worst case it conflicts with the users' one.

I would suggest that we remove all cuda modules from configuration files. Users already need to setup their environments, loading CUDA should be part of it. We could add a temporary check for CUDA when a GPU is requested to alert users that they requested a GPU but did not load a cuda module. That would only be temporary, to ease the transition for users relying on module load CUDA.

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