Provide a zero-copy method on KVM virtio-net.
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest3 patches 6 repliesIn review
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | A device for zero-copy based on KVM virtio-net.drivers/ drivers/ drivers/ +2 more | +1203 | 2 replies | |
| 2/3 | Provides multiple submits and asynchronous notifications.drivers/ drivers/ | +164 | 0 replies | |
| 3/3 | Let host NIC driver to DMA to guest user space.include/ include/ net/ +1 more | +184 | 0 replies |
Reviews trailers per patch
None of the 3 patches has a Reviewed-by or Acked-by.
| Patch | Jeff Dike |
|---|---|
| 1/3 | Sigend-off-by |
| 2/3 | |
| 3/3 | Sigend-off-by |
Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.
Cover letter [PATCH 0/3] Provide a zero-copy method on KVM virtio-net.
The idea is simple, just to pin the guest VM user space and then let host NIC driver has the chance to directly DMA to it. The patches are based on vhost-net backend driver. We add a device which provides proto_ops as sendmsg/recvmsg to vhost-net to send/recv directly to/from the NIC driver. KVM guest who use the vhost-net backend may bind any ethX interface in the host side to get copyless data transfer thru guest virtio-net frontend.
We provide multiple submits and asynchronous notifiicaton to vhost-net too.
Our goal is to improve the bandwidth and reduce the CPU usage. Exact performance data will be provided later. But for simple test with netperf, we found bindwidth up and CPU % up too, but the bindwidth up ratio is much more than CPU % up ratio.
What we have not done yet:
To support GRO
Performance tuning