Skip to content

Conversation

@tariq1890
Copy link
Contributor

No description provided.

@tariq1890 tariq1890 requested a review from klueska January 29, 2025 21:40
klueska and others added 2 commits January 29, 2025 19:48
This pulls in a temporary change to ensure that the CI created within a
GI is always of maximum size. It is a WIP because the change in go-nvlib
is not yet finalized, so we can't actually vendor in the solution yet.

It works by reversing the loop that walks through CIs to ensure that we
visit up any "newer" CI profiles before visiting older ones. The
assumption being that newer ones may provide a CI definition that has a
larger memory slice count with the same compute slice count.
Unfortunately, we don't have a way to distinguish this in the canonical
naming convention, so the same names refers to both MIG devices -- hence
the bug.

We need a more robust / comprehensive solution to this issue, possibly
introducing a "custom" naming convention to distibguish the cases.

Signed-off-by: Kevin Klues <[email protected]>
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

Successfully merging this pull request may close these issues.

3 participants