RFC vhost-nvme: new qemu nvme backend using nvme target
Get series with b4
b4 am 1448987171.3041.2.camel@haseeVersions 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 8 lines · Paolo Bonzini
Quoted 6 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
Quoted 8 lines
Quoted 1 line
"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_submitfor the data path, perhaps there's not much to gain from vhost-nvme...
What do you think about virtio-nvme+vhost-nvme?
I also have patch for vritio-nvme:
https://git.kernel.org/cgit/linux/kernel/git/mlin/linux.git/log/?h=nvme-split/virtio
Just need to change vhost-nvme to work with it.
Quoted 4 lines
Paolo
Quoted 1 line
Still tuning.