vDPA virtio data-path acceleration subsystem
A virtualization framework that lets SmartNICs and DPUs expose their hardware data paths to virtual machines as standard virtio devices, giving guests near-native networking and storage speed without vendor-specific drivers. It backs current hardware from NVIDIA (ConnectX-6, BlueField), AMD/Pensando, Intel, Marvell, Alibaba, and SolidRun, plus a userspace variant (VDUSE) for emulation.
recommendation
It should stay because this is an actively developed virtualization subsystem, not a single legacy driver, with cleanup and feature work still landing upstream in 2026 and multiple major vendors shipping hardware that depends on it. NVIDIA's current DOCA documentation and the in-tree AMD pds_vdpa docs confirm it is part of live DPU and SmartNIC deployments for VM networking, and there is no successor framework on the horizon.
repository signals
sources
- lore.kernel.org
Recent upstream work still lands in the core vDPA bus code; the subsystem was touched in March 2026 by a cleanup/update series rather than retirement work.
- docs.kernel.org
Upstream kernel documentation describes active use of the AMD/Pensando DSC vDPA driver, including setup steps for creating vDPA devices for virtio networking.
- docs.nvidia.com
NVIDIA’s 2026 DOCA docs describe current vDPA deployments on ConnectX-6 Lx/Dx and BlueField-2-and-later hardware for VM virtio connectivity and hardware offload.
- docs.kernel.org
Kernel documentation describes VDUSE as an in-tree userspace-backed vDPA framework, showing the subsystem also serves ongoing software-emulated/prototyping use cases rather than only legacy hardware.
codex reasoning notes (technical)
`drivers/vdpa` is an active driver subsystem, not a dead single-device driver: local tree inspection via shell showed a core bus plus vendor drivers and simulators. Lore evidence came from `lore_file_timeline` on `drivers/vdpa/vdpa.c`, which showed fresh 2026 activity and no obvious removal signal in the sample. Deployment evidence came from `web.search_query` + `web.open` on official kernel docs and NVIDIA docs, which show current vendor-backed vDPA products and continued VM/DPU deployment. Because the directory covers an active virtualization offload subsystem with current hardware and no natural successor, the right hint is `keep`.