2 weeks of driver and client optimizations for working with RDMA seems to be 1 victory. Already, RDMA mode on my M2 Ultra with a unified memory bandwidth of 800 GB/s and DGX Spark with a unified memory bandwidth of 273 GB/s gives this result
https://t.co/Pff6vgNARp
@u1tra_instinct@ivanfioravanti@audreyt Well, it’s like I’m on the finish line with the Roce v2 driver to work rdma between Spark and the studio
https://t.co/Pff6vgNARp
Shipped MelonDMA v0.2.0 — a native RDMA (RoCEv2) driver for macOS that doesn't officially exist. Mellanox ConnectX runs on an M2 Ultra Mac Studio via DriverKit. 40G. No Apple driver, no NVIDIA stack.
https://t.co/yjfbNF7Rgd
The goal: make RDMA normal on macOS — llama.cpp / MLX / distributed inference moving KV cache and weights over RoCE, no TCP. Disaggregated inference on Apple Silicon with better TTFT. Eventually a Metal GPUDirect-style CPU bypass.
Where it stands: data path + isolation are done and proven. Open: MSI-X delivery (timer polling today), observability, a true kernel-bypass fast path. Pre-1.0, honestly — but it's a driver holding real traffic, not a demo.
Live-verified on real hardware: full firmware lifecycle, P0/P1/P3 gates pass on a loaded DEXT — 1M msgs with zero errors, isolation, quotas, ABI fuzzing, inline sends, atomics. ~73µs RTT, 20–28 Gbit/s (PCIe Gen3 x4 cap, not the driver).
MelonDMA is a DriverKit DEXT that takes over the Mellanox ConnectX-4 Lx PCI card and brings up real RoCEv2: QP/MR/CQ, SEND/RECV, RDMA read/write, atomics, DCQCN. Plus a libibverbs-compatible layer, so existing RDMA apps just work.
Well
I thought it would be easy to assemble the rdma driver.
Now the driver’s work is at the stage of surpassing TCP and finding all optimization points.