Skip to content

RFC virtio nvme

Keith Busch linux-nvme virtualization 1 version New

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 RFC Latest0 of 2 patches 0 repliesNew

Patches in v1 No applies recorded yet

None of the 2 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.

Read the v1 thread

Cover letter [RFC PATCH 0/2] virtio nvme
Quoted 20 lines · Ming Lin

The goal is to have a full NVMe stack from VM guest(virtio-nvme) to host(vhost_nvme) to LIO NVMe-over-fabrics target.

Now there are lots of duplicated code with linux/nvme-core.c and qemu/nvme.c. The ideal result is to have a multi level NVMe stack(similar as SCSI). So we can re-use the nvme code, for example

.-------------------------.
| NVMe device register |

 Upper level           | NVMe protocol process   |
                       |                         |
                       '-------------------------'



             .-----------.    .-----------.    .------------------.
Lower level  |   PCIe    |    | VIRTIO    |    |NVMe over Fabrics |
             |           |    |           |    |initiator         |
             '-----------'    '-----------'    '------------------'
Quoted 5 lines

todo:
- tune performance. Should be as good as virtio-blk/virtio-scsi
- support discard/flush/integrity
- need Redhat's help for the VIRTIO_ID_NVME pci id
- multi level NVMe stack

Hi Ming,

I'll be out for travel for the next week, so I won't have much time to do a proper review till the following week.

I think it'd be better to get this hierarchy setup to make the most reuse possible than to have this much code duplication between the existing driver and emulated qemu nvme. For better or worse, I think the generic nvme layer is where things are going. Are you signed up with the fabrics contributors?