RDMA and RoCE in briefWhat the terms mean and what a lossless RoCEv2 network needs. Switch-side configuration is in Cisco DC CLI under Lossless Ethernet.
RDMA (remote direct memory access) lets one host read or write memory on another host without going through either kernel or the remote CPU. The adapter does the copy directly from and to registered application buffers, so latency drops to a few microseconds and CPU use stays low at 100 to 400 Gb/s. It carries NVMe over Fabrics, iSER, NFS over RDMA, SMB Direct, vSAN, MPI and GPU-to-GPU traffic for AI training.
| Transport | Runs on | Routable | Needs a lossless network |
|---|---|---|---|
| InfiniBand | Its own link layer, switches and subnet manager | Within the IB subnet (IB routers between subnets) | Built in: credit-based flow control |
| RoCE v1 | Ethernet, EtherType 0x8915 | No, one Layer 2 domain | Yes, PFC |
| RoCE v2 | UDP destination port 4791 over IPv4 or IPv6 | Yes | Yes in most designs: PFC plus ECN |
| iWARP | TCP | Yes | No, TCP recovers from loss |
- Verbs
- The programming interface (libibverbs). Applications create objects on an RDMA device and post work requests to them.
- Queue pair (QP)
- A send queue and a receive queue that form one end of a connection. RC (reliable connected) is the usual type; UD is datagram.
- Completion queue (CQ)
- Where the adapter reports that a work request has finished.
- Memory region (MR)
- A buffer registered and pinned with the adapter. The remote side needs its rkey to read or write it.
- GID and GID index
- The RDMA address of a port. On RoCE each IP address creates a v1 and a v2 entry in the GID table, so tools must use the index of the v2 entry.
- RDMA CM
- Connection manager that sets up QPs from IP addresses, the way sockets do. NVMe, iSER, NFS and rping use it.
A lossless RoCEv2 recipe. RoCE retransmits by going back to the lost packet, so even small loss cuts throughput sharply. The usual design is:
- One priority for RoCE, most often 3, marked with DSCP 26 (ToS 104, or 106 with the ECN-capable bits). Hosts and switches trust DSCP.
- PFC (802.1Qbb) enabled on that priority only, on every host and switch port in the path, with the PFC watchdog on the switches. Global 802.3x pause off.
- ECN marking on the switch queue for that priority, and DCQCN congestion control on the adapters. The receiver answers ECN marks with CNP packets, usually DSCP 48, which the switches forward in a strict-priority queue.
- The same jumbo MTU on every hop (9000 on hosts, 9216 on switches), which gives a RoCE MTU of 4096.
- Either static settings everywhere or DCBX learning from the switch, not a mix.
Newer adapters with selective retransmission tolerate some loss better, and a few vendors support RoCE over lossy networks, but check the vendor design guide before dropping PFC.
Your valuesType a value and it replaces the yellow placeholders in every command. Nothing leaves this page.
No commands match that search. Try a shorter word, or pick All topics.