ilkerandClaude Opus 5
55417546fc
NVML is the only source of NVLink topology, and that topology is what keeps a tensor-parallel group off the slow path inside a node. It needs cgo, so it sits behind the nvml tag and the default build keeps using nvidia-smi. Discover() picks the backend and falls back to nvidia-smi when NVML fails, logging the fallback rather than performing it silently: on a node that is meant to have working NVML, a quiet downgrade hides a broken driver installation and costs the scheduler its topology. CI now compiles the tagged build. That immediately paid for itself: ErrNoNVML was declared only in the untagged file, so the tests did not compile under -tags nvml. It is now declared where both builds can see it. Not verified: the NVML path has never run against a driver, because there is no GPU machine available. The NVLink domains it reports should be treated as unverified until someone runs `llmgw agent inventory` on a real node. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
12 lines
289 B
Go
12 lines
289 B
Go
//go:build !nvml
|
|
|
|
package discovery
|
|
|
|
import "context"
|
|
|
|
// nvmlAvailable reports that this build cannot use NVML.
|
|
const nvmlAvailable = false
|
|
|
|
// DiscoverGPUsNVML is unavailable in builds without the nvml tag.
|
|
func DiscoverGPUsNVML(context.Context) ([]GPU, error) { return nil, ErrNoNVML }
|