HybridMesh: A Hardware-software Hybrid Approach for Accelerating Service Mesh Ingress
summary
HybridMesh implements an ingress gateway that splits tasks between a SmartNIC and CPU proxy, using an NVIDIA BlueField-2 DPU running DPDK for layer‑7 parsing and hardware regex, and a lightweight HAProxy-based node stack for control tasks. The NIC stack tags packets with 6-byte metadata after regex matching and RSS-aware dispatch, and an eBPF-based HMT (XDP/TC/socket redirection) collapses namespaces and avoids double TCP/IP processing. The prototype reaches 4.4× HTTP throughput, reports 2.3× cost‑effectiveness and 2.8× better power efficiency versus software-only.
AI-written summary · about
chapters (11)
- 0:00HybridMesh project intro
- 1:41Ingress gateway challenges
- 3:52Current ingress bottlenecks
- 5:16Limitations of optimizations
- 6:43HybridMesh design
- 8:06NIC and node stack workflow
- 10:13HybridMesh tunnel
- 11:18Implementation details
- 11:59Performance vs software gateways
- 12:42Cost and power efficiency
- 13:44Summary and conclusion
related talks
30mTo Mesh or not to Mesh
31mThe Future of Service Meshes: Sidecarless or eBPF?
39mHardware Accelerated Service Mesh Overview
37mService MESH without the MESS - Raymond de Jong
43mService MESH without the MESS
19mCluster Optimization: Harnessing DPUs for Ambient Mesh Workloads
28mIt's a Multi-Mesh World
05mUnlocking Next-Gen Networking and Security with Cilium Service Mesh