VDUSE - vDPA Device in Userspace
summary
vDUSE implements vDPA device emulation entirely in userspace with the control path handled by the kernel driver and the data path by a userspace daemon that uses mmu-based soft IOVA and bouncing buffers or direct mapping via fd + mmap. Communication uses control ioctls and three messages (get vq state, update iotlb, set status), plus kick fds and interrupt injection for queue notifications. Work is on GitHub, patches are posted upstream, current support is block device only with plans for more device types and zero copy.
AI-written summary · about
chapters (9)
- 0:00Intro
- 0:45VDPA Overview
- 3:06What is VDUSE
- 3:58Why Userspace
- 4:54Architecture Overview
- 5:56Control Path
- 7:37Data Path
- 9:54How to implement a VDUSE Daemon
- 15:43Status & Future Work
related talks
12mGetting GPUDirect to Work with Broadcom NICs
34mDeclarative Device Virtualization: Orchestrating GPUs & Hardware in Cloud Native Environments
18mQEMU Live Update
30mIntroduction and Deep Dive into containerd
26mGPUDirect + SDR: How to Move One Billion Samples per Second over PCIe
38mSIG-Node: Intro and Deep Dive
32mSponsor Talk – Haydn Nelson
34mIntroduction to libuv: What's a Unicorn Velociraptor?