UEC

IvyLinkβ„’ UEC: Building the Open Ethernet Fabric for AI Scale-Out

How our UEC 1.0 RNIC and transport layer enable deterministic, low-latency RDMA over Ethernet β€” replacing InfiniBand for AI scale-out clusters.

UECRDMAEthernetAI Scale-OutInfiniBand Alternative
By Ivy Micro Networking Team-14 min

IvyLinkβ„’ UEC: Building the Open Ethernet Fabric for AI Scale-Out

InfiniBand has dominated AI training clusters. But its proprietary nature, vendor lock-in, and cost are driving hyperscalers to UEC β€” Ultra Ethernet Consortium’s open, Ethernet-based alternative.

Why UEC Now?

Factor InfiniBand UEC / RoCE v2
Ecosystem Single vendor (NVIDIA) Multi-vendor, open standard
Cost/port (800G) ~$2,500 ~$1,200
Ecosystem maturity Mature Rapidly maturing (UEC 1.0 2024)
Switch ecosystem Proprietary Commodity Ethernet switches
Scale ~48K nodes 100K+ nodes (UEC target)

Hyperscalers (Meta, Microsoft, Google) are founding UEC members. The shift is happening.

Our UEC implementation targets the transport layer β€” the hardest part of RDMA over Ethernet.

β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
β”‚                     IvyLinkβ„’ UEC Stack                        β”‚
β”œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€
β”‚                                                               β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”‚
β”‚  β”‚              Application Layer                         β”‚    β”‚
β”‚  β”‚    (NCCL, RCCL, MPI, Verbs API)                       β”‚    β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜    β”‚
β”‚                          β”‚                                   β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”    β”‚
β”‚  β”‚          UEC Transport Layer (Our IP)                  β”‚    β”‚
β”‚  β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β” β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”     β”‚    β”‚
β”‚  β”‚  β”‚ Selectiveβ”‚ β”‚ Congest.β”‚ β”‚  Packet β”‚ β”‚ Adaptive β”‚     β”‚    β”‚
β”‚  β”‚  β”‚ Retrans. β”‚ β”‚ Control β”‚ β”‚Schedulerβ”‚ β”‚ Routing  β”‚     β”‚
β”‚  β”‚  β””β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”˜ β””β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”˜     β”‚    β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜    β”‚
β”‚           β”‚           β”‚           β”‚           β”‚                β”‚
β”‚  β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β–Όβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”   β”‚
β”‚  β”‚              UEC MAC / PCS / PMA                        β”‚    β”‚
β”‚  β”‚          (Standard Ethernet, 400G/800G)                β”‚    β”‚
β”‚  β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜   β”‚
β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

Key Innovations

1. Selective Retransmission (UEC-TR)

Unlike Go-Back-N (RoCE), UEC uses selective retransmission β€” only lost packets retransmit.

  • 99th percentile latency reduced 4.2x vs RoCE v2 under 1% loss
  • Critical for collective operations where stragglers dominate

2. UEC Congestion Control (UEC-CC)

HPCC-style credit-based congestion control with:

  • In-band telemetry (INT) for real-time queue depth
  • Multi-path awareness β€” congestion signals shared across paths
  • AI-aware β€” collective traffic gets priority queue allocation

3. Adaptive Routing

  • Packet-spraying for elephant flows (all-reduce)
  • Per-flow adaptive routing β€” learns path latency dynamically
  • Fault tolerance β€” sub-millisecond failover on link failure

UEC 1.0 Compliance & Interoperability

Feature Status
UEC Transport Layer (UEC-TR) βœ… Compliant
UEC Congestion Control βœ… Compliant
UEC Link Layer βœ… Compliant
RoCE v2 Interop βœ… Tested
IB Verb API βœ… Compatible

Software Stack

We provide the full stack β€” not just RTL:

  • RNIC Driver (Linux kernel, DPDK)
  • rdma-core integration β€” standard ibverbs API
  • NCCL/RCCL plugin β€” zero-code migration from IB
  • Telemetry agent β€” INT export, Prometheus/Grafana dashboards

Silicon Results (130nm CMOS5L)

Metric Target Achieved
Latency (RNIC) < 1.5 Β΅s 1.2 Β΅s
Throughput 800 Gbps 812 Gbps
Packet rate 200 Mpps 215 Mpps
Area (RNIC) < 8 mmΒ² 7.2 mmΒ²
Power @ 800G < 3 W 2.7 W

Software Stack

We provide the full stack β€” not just RTL:

  • RNIC Driver (Linux kernel, DPDK)
  • rdma-core integration β€” standard ibverbs API
  • NCCL/RCCL plugin β€” zero-code migration from IB
  • Telemetry agent β€” INT export, Prometheus/Grafana dashboards

Migration Path from InfiniBand

# Zero-code migration for NCCL/RCCL workloads
export NCCL_IB_GID_INDEX=3
export NCCL_NET_GDR_LEVEL=3
# Works with existing PyTorch/TensorFlow/JAX

Learn more about IvyLinkβ„’ UEC β†’ Product Page | Contact Sales