Loading…
Topic
GPUDirect Storage
2 posts about GPUDirect Storage. Every summary links to the original.
- 2 posts
- 1 company
The Good Stuff
Paid picks we use ourselves. Links carry a referral code — a subscription through one earns us a commission at no extra cost to you.
Newest first
Posts
How to Check and Configure NVIDIA GPUDirect Storage for Your Platform
NVIDIA GPUDirect Storage (GDS) accelerates GPU storage access by providing a direct data path between GPUs and storage, reducing latency and CPU overhead. The gds-diag tool, an open-source command-line utility distributed via the NVIDIA Magnum IO GitHub repository, simplifies configuring and optimizing GDS deployments by assessing environments, identifying problems, and suggesting improvements. It includes an optional AI agent skill that adds a natural-language interface and orchestration layer for multi-step diagnostics, working with coding assistants like Claude and Codex. The tool supports bare-metal, virtual machine, and container environments, and its subcommands include pre-install, post-install, config-audit, mount-check, and container-check, with each finding having a status badge (FAIL, WARN, INFO, PASS) and a mitigation plan. It requires Python 3.8 or newer, does not modify the system, and can output findings as structured JSON, while the support-matrix subcommand shows supported platform combinations with color-coded compatibility.
How to Read Data into GPU Memory in Python with NVIDIA GPUDirect Storage
GPU applications face growing datasets that demand efficient data movement to keep accelerators supplied. NVIDIA GPUDirect Storage (GDS) enables a direct path between storage and GPU memory through the nvidia-fs kernel module, bypassing CPU staging. KvikIO provides Python interfaces over cuFile with defaults of a 16 KiB GDS threshold and 4 MiB task size, and its compat_mode setting determines whether cuFile is invoked. This tutorial demonstrates reading a 1 GiB file into a CuPy buffer on an H100 system with NVMe and verifying the path by setting CUFILE_STATS_LEVEL=3 and inspecting gds_stats output. With four cuFile worker threads and max_request_parallelism set to four, the default task size divides the read into 256 cuFile requests, while a 1 GiB task size results in four 256 MiB pieces processed through bounce buffers with slab caching.
Related topics
All topics →Weekly digest
The best engineering reads, once a week.