RFC vhost-nvme: new qemu nvme backend using nvme target
Get series with b4
b4 am 1448477482.6540.3.camel@ssiVersions 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 2 lines · Paolo Bonzini
Do you still have a
blk_set_aio_contextsomewhere? I'm losing track of the changes.
No.
Quoted 5 lines
In any case, I think using a separate I/O thread is a bit premature, except for benchmarking. In the meanwhile I think the best option is to post a two-patch series with the vendor extension and the ioeventfd respectively.
I'll post.
BTW, I'm not sure about qemu upstream policy. Do I need to first make the kernel side patch upstream?
https://git.kernel.org/cgit/linux/kernel/git/mlin/linux.git/log/?h=nvme-google-ext
I think the kernel side patch will take a bit longer time to upstream.
Quoted 2 lines
Paolo