mirror of
https://github.com/deepseek-ai/3FS.git
synced 2026-11-05 00:47:47 +00:00
[PR #402] [Proposal] Design Doc of GDR integration for 3FS #416
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
deepseek-ai/3FS#416
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
📋 Pull Request Information
Original PR: https://github.com/deepseek-ai/3FS/pull/402
Author: @SimonCqk
Created: 3/17/2026
Status: 🔄 Open
Base:
main← Head:simoncqk/gdr-proposal-doc📝 Commits (1)
e910e79docs(proposal): add design proposal for GDR integrating into 3FS.📊 Changes
1 file changed (+382 additions, -0 deletions)
View changed files
➕
docs/proposals/usrbio-gdr-integration-proposal.md(+382 -0)📄 Description
As #395 discussed, currently, the application copies data to/from GPU VRAM. This adds latency, wastes CPU memory bandwidth, and can be a throughput bottleneck for model training and inference.
This proposal introduces GPU Direct RDMA (GDR) in 3FS, enabling the storage server to RDMA read/write directly to/from GPU VRAM with zero CPU-side copies.
I'd like to focus the discussion on the design first — collect community feedback on the API surface, architecture decisions, and known limitations before refining and submitting the complete implementation.
Waiting for your feedback and suggestions!
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.