NVIDIA / NVIDIA/cuda-python

[FEA]: Ability to provide an extra path for cuda-pathfinder to search with high priority

Offen
#1,054 7 Kommentare 1 Reaktion 1 zugewiesene Person Auf GitHub ansehen

@rwgk arbeitet bereits daran.

Seit 30.9.2025.

awaiting-response cuda.pathfinder feature
Vorherrschende Sprache
Cython
Sterne
3.4k
Forks
329
Ø Merge
1 T. 21 Std.
Gemergte PRs (30 T.)
113

Beschreibung

Is this a duplicate?
Area

cuda.pathfinder

Is your feature request related to a problem? Please describe.

The cuda-pathfinder's search path prioritizes libraries from wheels. For example, libnvshmem_host.so comes from libnvidia-nvshmem-cuXX wheel. If I'm working from a development branch of nvshmem, I may need to manually copy libraries over the site-packages directory in order to get my custom libraries to be opened. LD_LIBRARY_PATH is much lower in the priority order (on purpose), so that won't work either.

Describe the solution you'd like

A few different ideas come to mind:

  • <LIBNAME_UPPER_CASE>_PATH_OVERRIDE so each library has an ability to be overridden independently
  • CUDA_PATHFINDER_TOP_PRIORITY_PATH which applies to all pathfinder searches
  • Adding a <library>_HOME environment variable, and prioritizing it above other search paths
Describe alternatives you've considered

I think I listed all 3 above. The current hacky WAR is to copy .so files around on the system.

Additional context

No response

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

  1. Lies das ganze Issue und danach den Beitragsleitfaden des Projekts.
  2. Schreib ins Issue, dass du es übernimmst — das erspart doppelte Arbeit.
  3. Forke das Repository und arbeite in einem Branch.
  4. Öffne einen Pull Request, der die Issue-Nummer nennt.

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.