Network Engine's Hardware Matrix Problem, and Why DPUs Solve What NICs Can't - Josh Brooks, WorldTech IT/Network Engine#

Speakers: Josh Brooks, Chief Solutions Architect / Distinguished Technologist, WorldTech IT

• Why: This is a rare, candid product-engineering postmortem about the gap every operator hits with SmartNIC offload: hardware support is a matrix, not a feature. The speaker runs a real product (a hypervisor for network virtual appliances) and explains precisely why NIC offload paths fragment — E823 supports switchdev, X710 does not, OVS-DPDK double-burns CPU when the appliance already runs its own DPDK fast path.
• What: WorldTech IT currently ships Network Engine without OVS, leaning on Linux bridges with NIC hardware acceleration, virtio multi-queue tuning, and SR-IOV/IOMMU passthrough for performance-critical NVAs — an explicitly pragmatic workaround. The talk announces OPI Blueprint 003: move OVS offload onto a DPU (NVIDIA BlueField-3 first, since it is largely packaged there), so switching stops consuming host CPU cores entirely, with the goal of generalizing the pattern to KVM and KubeVirt across the ecosystem. (from abstract only)
• How: Offload the host OVS datapath to the DPU's Arm cores via the BlueField-3's existing OVS packaging, rather than stacking DPDK in the host on top of appliance DPDK, or depending on per-NIC switchdev support that only exists on part of the hardware matrix.
• Where applicable: Describes WorldTech IT's own product engineering, but the underlying problem (per-NIC offload matrix, DPDK-in-host vs DPDK-in-appliance, when passthrough beats bridging) is common to anyone running virtualized network functions on commodity NICs. Blueprint work starts from one vendor's silicon (BlueField-3), which the speaker is upfront about — the OPI point is turning that single-vendor example into a repeatable standard.