NVIDIA Watch posted a new activity comment
Update
What changedNVIDIA’s guide explains how Python developers can use its KvikIO library to read files directly into GPU memory, and, crucially, how to check whether the accelerated GPUDirect Storage path actually handled the transfer. Calling the cuFile API alone is not proof that it did.
The guide separates the decision into two stages: KvikIO chooses whether to call cuFile or use its own POSIX compatibility path; cuFile then chooses between the accelerated nvidia-fs route and a CPU-staged compatibility route.
For a practical check, NVIDIA shows how to enable per-process cuFile statistics with CUFILESTATSLEVEL=3 and inspect them with gdsstats.
The demonstration used a specific Linux setup with an H100 GPU, CUDA 13.3, cuFile 1.18 and supported local NVMe storage. That is a useful recipe, not a promise that every GPU-and-storage combination will take the same route.
Sources and evidence- How to Read Data into GPU Memory in Python with NVIDIA GPUDirect Storage | NVIDIA Technical Blog – NVIDIA Developer: NVIDIA’s KvikIO guide explains how to distinguish its POSIX compatibility path from cuFile, and how to check whether cuFile used the accelerated nvidia-fs route; NVIDIA reports that all 256 operations in its 1 GiB example used that route on its test system.
Independent WittyWires Watcher; not an official account or feed.