Skip to content

api: recognize Fabric GPU sharing strategy in validation#849

Open
AkshatDudeja77 wants to merge 1 commit intoNVIDIA:mainfrom
AkshatDudeja77:patch-2
Open

api: recognize Fabric GPU sharing strategy in validation#849
AkshatDudeja77 wants to merge 1 commit intoNVIDIA:mainfrom
AkshatDudeja77:patch-2

Conversation

@AkshatDudeja77
Copy link

What this PR does

  • Allows the API validation layer to recognize the Fabric GPU sharing strategy
  • Prevents false validation errors when Fabric-backed GPUs are configured
  • Keeps behavior fully gated behind existing feature gates

Why this is needed

Fabric-attached GPUs (IMEX / NVLink fabric) introduce sharing modes that are not purely local.
Without this change, valid Fabric configurations are rejected during validation.

This PR is intentionally minimal and scoped to validation only.

Scope

  • Validation logic only
  • No behavior change unless the corresponding feature gates are enabled

Signed-off-by: Akshat Dudeja <akshat.dudeja77@gmail.com>
@copy-pr-bot
Copy link

copy-pr-bot bot commented Jan 31, 2026

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

@klueska klueska added this to the Backlog milestone Feb 8, 2026
Comment on lines +47 to +49
if s == FabricStrategy {
return fmt.Errorf("fabric GPU sharing strategy is not enabled")
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I still don't undertand how this qualifies is a "Sharing Strategy".
Also, I don't thin this needs to be in a PR on its own, I'd rather see it as a separate commit in the same PR that introduces the constant.

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Understood, that’s fair.

This PR was intended as a follow-up to avoid validation rejecting a future Fabric-backed configuration, but given that Fabric doesn’t clearly qualify as a SharingStrategy in the same sense as MPS or TimeSlicing, I agree this isn’t the right place for it.

I’m happy to close this PR and treat any Fabric-related validation changes as part of a single PR once there’s a concrete implementation and a clearer API shape.

@klueska klueska self-assigned this Feb 8, 2026
@klueska klueska added the feature issue/PR that proposes a new feature or functionality label Feb 8, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

feature issue/PR that proposes a new feature or functionality

Projects

Status: Backlog

Development

Successfully merging this pull request may close these issues.

2 participants