NVIDIA/Mellanox mlx5 vDPA virtio-net offload for BlueField DPUs
Hardware acceleration for virtio-net network devices on NVIDIA/Mellanox ConnectX and BlueField data processing units (DPUs). It lets a hypervisor present a standard virtio-net NIC to a guest VM while the actual packet processing runs directly on the SmartNIC, giving virtual machines near-native networking performance in modern cloud and telco deployments.
recommendation
It should stay because the underlying hardware is current: NVIDIA still sells BlueField-3 today and is rolling out BlueField-4, and their 2025-era DOCA documentation actively promotes virtio-net emulation as a supported feature. The code itself is under steady upstream maintenance with fixes and new features landing through 2025/2026, so there is no sign of decline.
repository signals
sources
- git.kernel.org
Upstream directory has ongoing mainline development; local git history in this tree shows substantive fixes/features continuing into 2026, which is inconsistent with deprecation or removal.
- git.kernel.org
The directory is a real in-tree kernel driver implementation for mlx5 vDPA net, not helper-only code.
- docs.nvidia.com
Recent NVIDIA BlueField-2 documentation still describes virtio-net emulated devices and a 'vDPA over VirtIO Full Emulation' flow, indicating contemporary deployment of this capability.
- docs.nvidia.com
NVIDIA's 2025-era DOCA virtio-net service guide documents BlueField-3 virtio-net service as a current product capability, supporting ongoing deployments rather than legacy-only use.
- nvidia.com
NVIDIA's current product page lists BlueField-3 and BlueField-4 as active platform offerings, so mlx5-backed BlueField hardware is still sold new in 2025.
codex reasoning notes (technical)
Local `rg` confirmed a loadable module entry point in `mlx5_vnet.c` (`module_auxiliary_driver`). Local `git -c safe.directory=... log` showed active substantive maintenance through 2026 with many recent vdpa/mlx5 fixes, so no dead-driver signal. `lei` was unavailable, and web searches did not surface any lore removal/deprecation thread; I therefore used canonical-recall kernel.org tree/log URLs for stable upstream references, plus NVIDIA docs/product pages obtained via web search (`turn0search5`, `turn0search8`, `turn6search0`). Hardware is current BlueField/related mlx5 infrastructure, so the driver should be kept.