nvidia-container-toolkit/internal/lookup
Evan Lezar fa5a4ac499
Read ldcache at construction instead of on each locate call
This change udpates the ldcache locator to read the ldcache at construction
and use these contents to perform future lookups against. Each of the cache
entries are resolved and lookups return the resolved target.

Assuming a symlink chain: libcuda.so -> libcuda.so.1 -> libcuda.so.VERSION, this
means that libcuda.so.VERION will be returned for any of the following inputs:
libcuda.so, libcuda.so.1, libcudal.so.*.

Signed-off-by: Evan Lezar <elezar@nvidia.com>
2024-10-24 23:12:58 +02:00
..
cuda run goimports -local against the entire codebase 2023-12-01 11:13:17 +01:00
root [no-relnote] Add test for libcuda lookup 2024-10-24 15:56:25 +02:00
symlinks Fix typo in error message 2024-10-17 15:46:49 +02:00
device_test.go
device.go
dir.go
executable_test.go
executable.go
file_test.go
file.go
ldcache_test.go Read ldcache at construction instead of on each locate call 2024-10-24 23:12:58 +02:00
ldcache.go Read ldcache at construction instead of on each locate call 2024-10-24 23:12:58 +02:00
library_test.go Read ldcache at construction instead of on each locate call 2024-10-24 23:12:58 +02:00
library.go Read ldcache at construction instead of on each locate call 2024-10-24 23:12:58 +02:00
locator_mock.go
locator.go
merge.go
null.go Read ldcache at construction instead of on each locate call 2024-10-24 23:12:58 +02:00
path.go
symlinks.go Fix bug in sorting of symlink chain 2024-10-24 15:56:25 +02:00