GPUDirect Storage#
GPUDirect Storage (GDS) enables direct DMA transfers between GPU memory and storage, reducing CPU overhead and helping applications move data with lower latency and higher throughput.
GDS documentation is organized around two interfaces. cuFile covers file-system-based GPUDirect Storage for local and distributed storage. cuObject covers client and server APIs for object storage solutions that use GDS data paths.
Why GPUDirect Storage#
GPUDirect Storage is designed for workloads that need to move large amounts of data efficiently between storage and GPUs. By avoiding unnecessary CPU copies, it helps improve throughput, reduce latency, and free CPU resources for other work.
Choose Your Path#
Use cuFile if your application reads from or writes to files on supported local or distributed file systems. This is the main entry point for installation, configuration, API usage, troubleshooting, and performance guidance for GPUDirect Storage deployments.
Use cuObject if you are working with object storage deployments and need the client or server APIs. This section focuses on the API model for object storage solutions and the release notes for cuObject components.
Common Tasks#
Set up a new GPUDirect Storage environment
Begin with Getting Started for an overview of the setup flow. Then use the Troubleshooting and Installation Guide and Configuration Guide when preparing or validating a deployment.
Integrate GPUDirect Storage into an application
Start with the Overview Guide to understand the programming model and supported usage patterns. Then use the cuFile API Reference for detailed API behavior and interfaces.
Tune and validate performance
Use the Best Practices Guide, Design Guide, and O_DIRECT Requirements Guide to understand deployment considerations, performance tradeoffs, and I/O requirements.
Check current platform behavior and support
Review the Release Notes for platform support, known limitations, fixes, and behavior changes.
Object Storage APIs#
If you are working with object storage solutions, start with the cuObject Overview and then move to the API specification that matches your role:
For component-specific updates, refer to the following release notes:
How to Use This Documentation#
If you are new to GPUDirect Storage, start with cuFile unless you are specifically working with object storage APIs. If you already know your deployment model, use the left navigation to move directly to the guide or reference that matches your task.
For file-system-based deployments, the typical path is Getting Started, then Configuration or Troubleshooting and Installation, followed by the cuFile API Reference and performance guidance as needed.
For object-storage-based deployments, start with cuObject and then choose the client or server API specification based on your role in the system.