RFC vhost-nvme: new qemu nvme backend using nvme target
Get series with b4
b4 am [email protected]Versions newest first
- v1 RFC Latest0 of 9 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 9 patches the cover letter announces are in this archive.
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [RFC PATCH 0/9] vhost-nvme: new qemu nvme backend using nvme target
Quoted 7 lines · Ming Lin
qemu-nvme: 148MB/s
vhost-nvme + google-ext: 230MB/s
qemu-nvme + google-ext + eventfd: 294MB/s
virtio-scsi: 296MB/s
virtio-blk: 344MB/s"vhost-nvme + google-ext" didn't get good enough performance.
I'd expect it to be on par of qemu-nvme with ioeventfd but the question
is: why should it be better? For vhost-net, the answer is that more zerocopy can be done if you put the data path in the kernel.
But qemu-nvme is already using io_submit for the data path, perhaps there's not much to gain from vhost-nvme...
Paolo
Quoted 1 line
Still tuning.