RDMA · RoCEv2 · Lossless Ethernet

What Is RDMA?

RDMA (Remote Direct Memory Access) lets one machine read or write another machine's memory directly over the network, bypassing both CPUs and the operating system. The network adapter moves bytes straight between application memory on both ends, so latency is very low and CPU overhead is near zero. Over Ethernet, RoCEv2 carries RDMA so it can be routed, and because RDMA assumes no dropped packets it runs on a lossless fabric.

Zero-copykernel bypass, adapter to adapter
Near zeroCPU overhead on the data path
UDP 4791RoCEv2 encapsulation, routable
LosslessOcNOS-DC on Broadcom TH5
The mechanism

Zero-copy, CPU bypass, and why that is the point

A normal network transfer copies data through the kernel and leans on the CPU at both ends. RDMA removes both. The adapter reads directly from application memory on the sender and writes directly into application memory on the receiver, with nothing traversing the CPU on the data path. That is what delivers RDMA's combination of very low latency, very high throughput, and almost no CPU cost, and it is why RDMA became the standard for GPU-to-GPU communication.

  • Zero-copy: bytes move straight between application memory on both ends, never staged through intermediate kernel buffers.
  • Kernel bypass: the network adapter, not the operating system, drives the transfer, so the CPU is off the data path.
  • Near-zero overhead: the CPU is freed to run the workload rather than shuffle packets, which is decisive at GPU scale.
RDMA over Ethernet

How RoCEv2 carries RDMA over Ethernet

RoCEv2 (RDMA over Converged Ethernet, version 2) encapsulates RDMA in UDP and IP, using destination UDP port 4791, so it can be routed across a standard Layer 3 Ethernet fabric with no separate network required. The RDMA operation still runs adapter to adapter with the same zero-copy behavior; RoCEv2 simply gives it a routable Ethernet path. That is what lets a multi-vendor Ethernet fabric stand in for InfiniBand on GPU clusters.

Routable transport

RDMA rides inside UDP and IP on port 4791, so it crosses a standard routed data center instead of needing a dedicated fabric.

No-drop network

RDMA assumes the network never drops a packet, so it runs on a lossless fabric with PFC and ECN keeping every hop no-drop.

The AI fabric

This transport is the foundation of an AI fabric: the GPU-to-GPU network that carries every collective during training.

Why it matters for AI

Why AI collectives depend on RDMA, and why the fabric must be lossless

AI training runs collective operations such as AllReduce: after each step, every GPU exchanges gradients with every other GPU, then all wait for that exchange before the next step. The data volumes are large and the schedule is tight, so RDMA keeps each exchange fast and off the CPU. Because a single lost packet forces recovery that spikes tail latency and can stall the whole collective, RDMA over Ethernet always runs on a lossless fabric.

  • Collectives block every GPU until the exchange completes, so lower latency shortens the step that the entire cluster is waiting on.
  • RDMA keeps the exchange off the CPU and free of copies, which multiplied across millions of steps is a direct lever on total training time.
  • OcNOS-DC supplies the no-drop fabric with PFC, ECN, and dynamic load balancing on Broadcom Tomahawk 5, keeping flows off hot links.
FAQ

What Is RDMA, answered

What is RDMA?
RDMA stands for Remote Direct Memory Access. It lets one machine read or write another machine’s memory directly over the network, without involving either machine’s CPU and without copying the data through the operating system kernel. The network adapter moves the bytes straight between application memory on both ends. The result is very low latency and very high throughput with almost no CPU overhead, which is why RDMA is the standard way GPUs exchange data during AI training.
How does RoCEv2 carry RDMA over Ethernet?
RoCEv2 (RDMA over Converged Ethernet, version 2) encapsulates RDMA in UDP and IP, using destination UDP port 4791, so RDMA can be routed across a standard Layer 3 Ethernet data center rather than needing a separate network. The RDMA operation still runs adapter to adapter with the same zero-copy, CPU-bypass behavior; RoCEv2 just gives it a routable Ethernet path. This is what makes a multi-vendor Ethernet fabric a viable alternative to InfiniBand for GPU clusters.
Why do zero-copy and CPU bypass matter for AI?
AI training runs collective operations such as AllReduce, where every GPU exchanges gradients with every other GPU after each step, moving enormous amounts of data on a tight schedule. If the CPU had to copy every message through the kernel, it would become the bottleneck and burn power doing it. RDMA removes the CPU and the copies from the data path, so a GPU’s data lands in the peer GPU’s memory with minimal latency, which shortens the exchange every GPU is waiting on.
Why does RDMA need a lossless fabric?
RDMA was designed assuming the network does not drop packets. When a packet is lost, recovery is expensive and spikes tail latency, which can stall a whole GPU collective. So RDMA over Ethernet runs on a lossless fabric: Priority Flow Control and ECN keep the network no-drop. OcNOS-DC provides that fabric with PFC, ECN, and dynamic load balancing on Broadcom Tomahawk 5 hardware. See the lossless Ethernet and RoCEv2 pages for detail.

Designing an RDMA fabric? Let's build it lossless

Tell us the workload and the GPU scale, and an IP Infusion engineer will walk the RoCEv2 and lossless-fabric design with you on open hardware running OcNOS-DC.