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

Management of NVML init calls #225

Open
asm582 opened this issue Nov 4, 2024 · 2 comments
Open

Management of NVML init calls #225

asm582 opened this issue Nov 4, 2024 · 2 comments

Comments

@asm582
Copy link
Contributor

asm582 commented Nov 4, 2024

There are three NVML init calls in the daemonset; there should only be one init call using setup, and the init should be destroyed when the manager is stopped. There are several ways to achieve this; one way is to have a separate manager file later registered with the controller call in the setup method.

@kannon92
Copy link
Contributor

Is this issue still relevant?

@asm582
Copy link
Contributor Author

asm582 commented Nov 25, 2024

Yes, the design is to create a file that performs nvml init once, reuses while the daemonset is up, and terminates when unavailable or deleted.

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

2 participants