Ultra Ethernet Promises New RDMA Protocol

This week saw the formal launch of the Ultra Ethernet Consortium (UEC), which aims to reinvent Ethernet fabrics for massive-scale AI and HPC deployments. An impressive list of founding members back this ambitious effort: hyperscalers Meta and Microsoft; chip vendors AMD, Broadcom, and Intel; OEMs Arista, Atos, and HPE; and Cisco, which straddles the chip and OEM camps. Absent this backing, we could easily write off this consortium as doomed to failure.

Our skepticism is rooted not in the obvious need the UEC looks to serve but rather in the challenges of standardizing and implementing a full-stack approach. The effort plans to replace existing transport protocols as well as user-space APIs. Specifically, the Ultra Ethernet Transport (UET) protocol will be a new RDMA protocol to replace ROCE, and new APIs will replace the Verbs API from the InfiniBand heritage. UET will provide an alternative to RoCEv2 and Amazon’s SRD, both of which are deployed in hyperscale data centers.

(Source: Ultra Ethernet Consortium)

If the concept sounds familiar, you may have read our recent piece on NVIDIA’s Spectrum-X. That end-to-end Ethernet fabric builds on the ROCEv2 protocol, and it uses DPUs in endpoints to assist in congestion management. The Spectrum-X software stack supports only NVIDIA networking hardware, and the underlying protocol still relies on Priority-Based Flow Control (PFC) as a backstop against packet loss. Microsoft and others have documented the congestion problems that PFC can cause.

The UEC laid out some of the features planned for its new transport protocol. Some key new features include multipath packet spraying, out-of-order packet delivery, and novel rate-control algorithms. Given its early involvement, we expect Broadcom will contribute intellectual property related to the edge-queued datagram service (EQDS) described in an NSDI 2022 paper. Last year, it quietly acquired Correct Networks, which developed EQDS. An optional EQDS element is packet trimming, which drops payloads but delivers headers to inform receivers of network congestion. EQDS employs tunnels, however, rather than replacing the RDMA transport protocol.

To support the UET, the consortium will define new APIs that enable out-of-order packet delivery. Beyond the transport layer, the UEC will also address link-layer issues such as forward-error correction and retry mechanisms. These efforts may feed into other organizations including IEEE 802. One of the reasons the UEC launched before having a formal roadmap is that it needs to begin building liaisons with other standards bodies.

So can the UEC really expect to supplant the successful ROCE protocol? Amazon’s SDP provides existence proof that it can be done, at least when one party controls the end-to-end design. The challenge, therefore, is to replicate this effort in an ad-hoc standard with many parties contributing and voting. From a hardware perspective, we expect existing smart NICs can handle the transmit-rate pacing, packet spraying, and out-of-order reception. Multiple Ethernet-switch ASICs already implement packet trimming, also known as drop congestion notification. In our view, the UET must work with at least a subset of existing NICs and switch chips to achieve rapid adoption. The UEC plans to admit new members beginning in 4Q23, the next big milestone in building industry momentum.