PFC · ECN · DCQCN

What Is Lossless Ethernet?

Lossless Ethernet is standard Ethernet configured so a chosen class of traffic, typically RDMA, is not dropped under congestion. Priority Flow Control (PFC) pauses a specific priority queue before it overflows, Explicit Congestion Notification (ECN) marks packets early so senders slow down, and DCQCN ties switch ECN marking to NIC rate control. RoCEv2 needs this no-drop path, and OcNOS-DC ships these controls on Broadcom Tomahawk 5.

No-dropRDMA traffic class
3 controlsPFC · ECN · DCQCN
Tomahawk 5OcNOS-DC lossless stack
gNMIclosed-loop telemetry
The three controls

PFC, ECN, and DCQCN, and how they layer

The design intent is a ladder. ECN and DCQCN do the everyday work of keeping queues shallow so traffic keeps flowing; PFC only engages when a burst outruns them, pausing a priority for a moment rather than dropping. A fabric triggering PFC constantly needs its ECN thresholds tuned, not more PFC.

The backstop

Priority Flow Control (PFC)

PFC pauses one priority queue hop by hop when its buffer is about to overflow, so nothing is dropped. It is coarse and fast, used as the last line of defense rather than the everyday control.

The primary control

Explicit Congestion Notification (ECN)

ECN marks packets as a queue starts to build. The receiving NIC signals the sender, which lowers its rate before the queue ever fills. Fine-grained and continuous, it does the everyday work.

The loop

DCQCN

DCQCN binds ECN marking on the switch to rate control on the NIC. The switch role is the ECN marking; the NIC does the rate adjustment. Together they hold queues low without triggering PFC.

Why RDMA needs it

Why RoCEv2 requires a lossless path

RDMA was built for a no-drop transport. RoCEv2 carries RDMA over UDP and IP so it can be routed across a data center, but it inherits that low tolerance for loss: a single dropped packet forces recovery that spikes tail latency and can stall a GPU collective, which stalls the whole training step.

Making the Ethernet path lossless with PFC and ECN gives RoCEv2 the behavior it was designed for. That is the entire reason lossless Ethernet exists in AI fabrics, and it is why a production RoCEv2 GPU fabric always runs on a lossless-configured network.

On open hardware

What OcNOS-DC ships

On Broadcom Tomahawk 5 platforms, OcNOS-DC is the enabler for the full lossless stack, tuned in a closed loop during cluster bring-up rather than guessed.

  • PFC, including PFC over L3 with DCBX and LLDP, plus PFC Deadlock Detection and Recovery.
  • ECN and Dynamic ECN, with Enhanced Transmission Selection (ETS) and WRED.
  • Buffer tuning and RTAG7 hashing to spread flows across the fabric.
  • Congestion and queue counters streamed over gNMI and OpenConfig telemetry for closed-loop threshold tuning.
FAQ

What Is Lossless Ethernet FAQ

What is lossless Ethernet?
Lossless Ethernet is standard Ethernet configured so that a chosen class of traffic, typically RDMA, is not dropped when the network gets congested. It is achieved with Priority Flow Control (PFC), which pauses a specific priority queue before its buffer overflows, and Explicit Congestion Notification (ECN), which marks packets early so the sender slows down before any queue fills. The goal is a no-drop path for traffic that reacts badly to loss, without turning the whole network no-drop.
How do PFC, ECN, and DCQCN work together?
They operate at different speeds. ECN is the primary, fine-grained control: a switch marks packets when a queue starts to build, and the receiving NIC signals the sender to reduce its rate. DCQCN is the end-to-end algorithm that ties ECN marking on the switch to rate control on the NIC in a continuous loop; the switch role in DCQCN is the ECN marking. PFC is the fast backstop: when a queue is about to overflow anyway, PFC pauses that priority hop by hop so nothing is dropped while ECN and DCQCN take effect. Well-tuned fabrics lean on ECN and DCQCN and keep PFC as the last resort.
Why does RoCEv2 need lossless Ethernet?
RoCEv2 is RDMA carried over UDP and IP. RDMA was designed for a no-drop transport, so a dropped packet forces recovery that is expensive in tail latency and can stall a GPU collective. Making the Ethernet path lossless with PFC and ECN gives RoCEv2 the no-drop behavior it expects, which is why a production RoCEv2 GPU fabric always runs on a lossless-configured network.
What lossless features does OcNOS-DC support?
On Broadcom Tomahawk 5 hardware, OcNOS-DC supports PFC (including PFC over L3, with DCBX and LLDP), ECN, Dynamic ECN, Enhanced Transmission Selection (ETS), WRED, and PFC Deadlock Detection and Recovery, along with buffer tuning and RTAG7 hashing. Congestion state and queue counters stream over gNMI and OpenConfig telemetry for closed-loop tuning. See the PFC deadlock and DCQCN pages for the detail behind each.

Tuning a lossless fabric? Let's do the thresholds together

Tell us the GPU scale and the traffic classes, and an IP Infusion engineer will set PFC, ECN, and DCQCN with you rather than leave the thresholds to guesswork.