Rename gds backend to cufile and bump to v0.3.1 - #9
Merged
Conversation
The backend is built on the cuFile userspace library, which ships with the CUDA toolkit. True GPUDirect Storage additionally needs the kernel-side nvidia-fs driver; without it cuFile falls back to a host-staged path. Name the backend 'cufile' so we don't promise GDS when only the library is present. Renames the backend string, the fil_cufile_io struct, fil_cufile_async_submit, and related symbols/messages, plus CLI help and README. Signed-off-by: Karl Bonde Torp <k.torp@samsung.com>
Signed-off-by: Karl Bonde Torp <k.torp@samsung.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Renames the
gdsI/O backend tocufileso the backend name reflects what itactually depends on. The backend is built on the cuFile userspace library,
which ships with the CUDA toolkit. True GPUDirect Storage additionally requires
the kernel-side
nvidia-fsdriver — without it, cuFile transparently falls backto a host-staged compatibility path. Naming the backend
cufileavoids promisingGDS when only the library is present (e.g. environments where the kernel-side
GDS stack isn't installed).
Motivation
Upstream AiSIO main dropped the kernel-side GDS stack (
nvidia-gds/nvidia-fs/ MLNX_OFED), keeping only the CUDA toolkit. fil still compiles and the backend
still runs there, but it no longer does true NVMe→GPU DMA — so the
gdsname wasmisleading.
NOTE Version is bumped for easy consumption from AiSIO