-
Notifications
You must be signed in to change notification settings - Fork 64
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
Getting the wrong MIG count per GPU Index #60
Comments
Hi @anaconda2196. From the
This means that the MIG count being returned is correct. This is the maximum number of possible MIG devices and not the number of MIG devices actually allocated. For a GPU with MIG disabled this is 0. To get the number of actual MIG devices you need to iterate over possible MIG devices and call From the docs:
A return value of |
Here's an example from our go-nvlib wrapper library: |
@klueska @elezar Oh okay got it. Thanks for sharing this. Could you please tell me which exact function I should call to get the number of actual MIG devices created per GPU index? I would like to first get the total MIG device count per GPU index, and then later use DeviceGetMigDeviceHandleByIndex to get the MIG ID and MIG UUID as per the above sample program. |
@anaconda2196 there is no specific function to get the number of MIG devices. If you need to get the available MIG devices you would need to:
|
Hello @klueska @elezar
I am getting the wrong MIG count per GPU Index.
Sample Program:
GPU - A100 (MIG enabled but no MIG devices are created)
-> Wrong output, should be MIG Count - 0
GPU - A100 (MIG enabled - Mix Strategy)
-> Wrong output, should be MIG Count - 3
GPU - A100 (MIG disabled)
-> Correct output
Any help would be greatly appreciated
The text was updated successfully, but these errors were encountered: