ollama/discover
Daniel Hiltgen 3f30836734
CUDA: filter devices on secondary discovery (#13317)
We now do a deeper probe of CUDA devices to verify the library version has
the correct compute capability coverage for the device.  Due to ROCm also
interpreting the CUDA env var to filter AMD devices, we try to avoid setting
it which leads to problems in mixed vendor systems.  However without setting
it for this deeper probe, each CUDA library subprocess discovers all CUDA GPUs
and on systems with lots of GPUs, this can lead to hitting timeouts.  The fix is
to turn on the CUDA visibility env var just for this deeper probe use-case.
2025-12-03 12:58:16 -08:00
..
cpu_linux_test.go DRY out the runner lifecycle code (#12540) 2025-10-23 11:20:02 -07:00
cpu_linux.go discover: Support cgroups cores and memory limitations (#10292) 2025-11-17 16:13:03 -08:00
cpu_windows_test.go Use runners for GPU discovery (#12090) 2025-10-01 15:12:32 -07:00
cpu_windows.go win: revert CPU discovery logic to 0.12.3 (#12969) 2025-11-05 10:32:38 -08:00
gpu_darwin.go Use runners for GPU discovery (#12090) 2025-10-01 15:12:32 -07:00
gpu_info_darwin.h Rename gpu package discover (#7143) 2024-10-16 17:45:00 -07:00
gpu_info_darwin.m Rename gpu package discover (#7143) 2024-10-16 17:45:00 -07:00
gpu.go log: instrument CPU discovery timing (#12960) 2025-11-04 16:23:37 -08:00
runner_test.go app: add code for macOS and Windows apps under 'app' (#12933) 2025-11-04 11:40:17 -08:00
runner.go CUDA: filter devices on secondary discovery (#13317) 2025-12-03 12:58:16 -08:00
types.go discovery: only retry AMD GPUs (#12894) 2025-11-04 15:33:46 -08:00