GPU Direct Storage (GDS) is a technology that enables a direct memory access (DMA) data path between a storage device—such as an NVMe drive or parallel filesystem—and GPU memory, completely bypassing the CPU and system memory buffer. This eliminates a traditional bottleneck where the CPU must copy data from storage into a bounce buffer in system RAM before the GPU can access it, adding latency and consuming valuable CPU cycles.
Glossary
GPU Direct Storage

What is GPU Direct Storage?
GPU Direct Storage (GDS) creates a direct data path between local or remote storage and GPU memory, bypassing the CPU and system memory to dramatically accelerate I/O for data-intensive AI and HPC workloads.
By leveraging RDMA and GPUDirect capabilities, GDS allows the GPU to pull data directly from a storage target into its own high-bandwidth memory. This is critical for workloads like deep learning training on massive datasets stored on Lustre or local NVMe arrays, where the CPU can become a severe I/O bottleneck, starving the GPU of data and reducing overall utilization.
Key Features of GPU Direct Storage
GPU Direct Storage (GDS) creates a direct data path between local or remote storage and GPU memory, bypassing the CPU and system memory to eliminate I/O bottlenecks for data-intensive AI and HPC workloads.
CPU Bypass Architecture
GDS enables a Direct Memory Access (DMA) engine to transfer data straight from NVMe drives or network-attached storage into GPU memory. This completely circumvents the CPU's buffer copy mechanism, eliminating the traditional bounce buffer in system memory. The result is a significant reduction in I/O latency and a dramatic increase in usable bandwidth for large-scale training datasets.
cuFile API Integration
The technology is exposed through the cuFile API, a core component of the CUDA toolkit. This API provides a POSIX-like interface for file operations, allowing developers to read directly from storage into GPU device memory without complex memory management. It supports standard file system operations and is compatible with both local file systems and parallel distributed file systems like Lustre and GPFS.
RDMA Network Compatibility
GDS extends its direct data path over the network by integrating with Remote Direct Memory Access (RDMA) technologies. This allows data to be pulled directly from remote storage servers or NVMe over Fabrics (NVMe-oF) targets into GPU memory without CPU intervention on either the client or server side. It is a critical enabler for disaggregated storage architectures in large-scale AI clusters.
Kernel Driver Model
The GDS functionality relies on the nvidia-fs.ko kernel module, which works in tandem with the NVIDIA GPU driver. This module intercepts storage I/O requests and orchestrates the DMA transfer between the storage controller and the GPU. It is designed to handle page-faults and memory pinning automatically, ensuring that GPU memory buffers are properly locked for direct hardware access during the transfer.
Compatibility Requirements
To leverage GDS, specific hardware and software alignment is required:
- GPU: NVIDIA Volta architecture or newer (Tesla V100, A100, H100).
- Storage: NVMe SSDs or NVMe-oF targets.
- Network: Mellanox/NVIDIA ConnectX adapters for RDMA.
- File System: A GDS-compatible file system such as ext4, XFS, or a parallel file system with GDS support enabled.
- CUDA: Version 11.4 or later with the cuFile library.
Magnum IO Stack
GPU Direct Storage is a foundational component of NVIDIA's Magnum IO suite, which encompasses the entire I/O stack for accelerated computing. It works in concert with GPUDirect RDMA (for network-to-GPU transfers) and GPUDirect P2P (for GPU-to-GPU transfers) to create a fully optimized data movement ecosystem. This integration ensures that data never makes a round-trip through the CPU or system memory at any stage of the pipeline.
Frequently Asked Questions
Clear, technical answers to the most common questions about GPU Direct Storage (GDS), the NVIDIA technology that creates a direct data path between storage and GPU memory to eliminate CPU bottlenecks in data-intensive AI and HPC workloads.
GPU Direct Storage (GDS) is an NVIDIA technology that enables a direct data path between local or remote storage (NVMe drives, NVMe-oF targets) and GPU memory, bypassing the CPU and system memory entirely. It works by allowing the GPU to initiate and control DMA (Direct Memory Access) transfers from storage devices through the PCIe bus directly into GPU framebuffer memory. The mechanism relies on a kernel module (nvidia-fs.ko) that integrates with the Linux kernel's libaio and io_uring interfaces, enabling RDMA-like semantics for storage. When a CUDA application requests data, the GDS-enabled driver coordinates with the NVMe controller to stream data across the PCIe fabric into a pinned GPU memory buffer, avoiding the traditional bounce buffer in CPU RAM. This eliminates the CPU's involvement in the data copy loop, reducing latency, freeing CPU cycles for computation, and dramatically increasing throughput for I/O-bound AI training and inference workloads.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Understanding GPU Direct Storage requires familiarity with the underlying interconnects, memory technologies, and I/O frameworks that enable a direct data path from storage to GPU memory.
Bounce Buffer Elimination
A core performance benefit of GPU Direct Storage. In traditional I/O, data is staged in a CPU-attached bounce buffer in system DRAM before being copied to GPU memory. This creates a double-copy penalty and saturates the CPU's memory bandwidth. GPU Direct Storage eliminates this intermediate step, enabling a direct PCIe peer-to-peer transfer from the storage device to the GPU's frame buffer.
PCIe Peer-to-Peer Communication
The hardware-level mechanism that allows two PCIe endpoints—such as an NVMe drive and a GPU—to transfer data directly without routing through the Root Complex or system memory. This requires BIOS and platform support to enable Access Control Services (ACS) redirection. GPU Direct Storage leverages PCIe P2P to map the storage device's BAR space into the GPU's address domain.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us