search for: vhost_nvm

...; Learned vhost architecture: > http://blog.vmsplice.net/2011/09/qemu-internals-vhost-architecture.html > > The nice thing is it is not tied to KVM in any way. > Yes. There are assumptions vhost currently makes about the guest using virtio queues however, and at least for an initial vhost_nvme prototype it's probably easier to avoid hacking up drivers/vhost/* (for now).. (Adding MST CC') > For SCSI, there are "virtio-scsi" in guest kernel and "vhost-scsi" in > host kernel. > > For NVMe, there is no "virtio-nvme" in guest kernel(just u...

...) > > > > > > tcm_vhost(or vhost_scsi, host) > > > > > > LIO-scsi-target > > > > > > > > > > > > For NVMe stack, we'll have similar components: > > > > > > virtio-nvme(guest) > > > > > > vhost_nvme(host) > > > > > > LIO-NVMe-target > > > > > > > > > > > > > > > > I think it's more interesting to consider a 'vhost style' driver that > > > > > can be used with unmodified nvme host OS drivers. > &g...

...) > > > > > > tcm_vhost(or vhost_scsi, host) > > > > > > LIO-scsi-target > > > > > > > > > > > > For NVMe stack, we'll have similar components: > > > > > > virtio-nvme(guest) > > > > > > vhost_nvme(host) > > > > > > LIO-NVMe-target > > > > > > > > > > > > > > > > I think it's more interesting to consider a 'vhost style' driver that > > > > > can be used with unmodified nvme host OS drivers. > &g...

...; Play it in Qemu with: > >> > -drive file=disk.img,format=raw,if=none,id=D22 \ > >> > -device virtio-nvme-pci,drive=D22,serial=1234,num_queues=4 > >> > > >> > The goal is to have a full NVMe stack from VM guest(virtio-nvme) > >> > to host(vhost_nvme) to LIO NVMe-over-fabrics target. > >> > >> Why is a virtio-nvme guest device needed? I guess there must either > >> be NVMe-only features that you want to pass through, or you think the > >> performance will be significantly better than virtio-blk/virtio-scsi?...

...; Play it in Qemu with: > >> > -drive file=disk.img,format=raw,if=none,id=D22 \ > >> > -device virtio-nvme-pci,drive=D22,serial=1234,num_queues=4 > >> > > >> > The goal is to have a full NVMe stack from VM guest(virtio-nvme) > >> > to host(vhost_nvme) to LIO NVMe-over-fabrics target. > >> > >> Why is a virtio-nvme guest device needed? I guess there must either > >> be NVMe-only features that you want to pass through, or you think the > >> performance will be significantly better than virtio-blk/virtio-scsi?...

...request for your comments. > > > > Play it in Qemu with: > > -drive file=disk.img,format=raw,if=none,id=D22 \ > > -device virtio-nvme-pci,drive=D22,serial=1234,num_queues=4 > > > > The goal is to have a full NVMe stack from VM guest(virtio-nvme) > > to host(vhost_nvme) to LIO NVMe-over-fabrics target. > > Why is a virtio-nvme guest device needed? I guess there must either > be NVMe-only features that you want to pass through, or you think the > performance will be significantly better than virtio-blk/virtio-scsi? It simply passes through NVMe com...

...request for your comments. > > > > Play it in Qemu with: > > -drive file=disk.img,format=raw,if=none,id=D22 \ > > -device virtio-nvme-pci,drive=D22,serial=1234,num_queues=4 > > > > The goal is to have a full NVMe stack from VM guest(virtio-nvme) > > to host(vhost_nvme) to LIO NVMe-over-fabrics target. > > Why is a virtio-nvme guest device needed? I guess there must either > be NVMe-only features that you want to pass through, or you think the > performance will be significantly better than virtio-blk/virtio-scsi? It simply passes through NVMe com...

...r SCSI stack, we have: > > > > virtio-scsi(guest) > > > > tcm_vhost(or vhost_scsi, host) > > > > LIO-scsi-target > > > > > > > > For NVMe stack, we'll have similar components: > > > > virtio-nvme(guest) > > > > vhost_nvme(host) > > > > LIO-NVMe-target > > > > > > > > > > I think it's more interesting to consider a 'vhost style' driver that > > > can be used with unmodified nvme host OS drivers. > > > > > > Dr. Hannes (CC'ed) had...

...r SCSI stack, we have: > > > > virtio-scsi(guest) > > > > tcm_vhost(or vhost_scsi, host) > > > > LIO-scsi-target > > > > > > > > For NVMe stack, we'll have similar components: > > > > virtio-nvme(guest) > > > > vhost_nvme(host) > > > > LIO-NVMe-target > > > > > > > > > > I think it's more interesting to consider a 'vhost style' driver that > > > can be used with unmodified nvme host OS drivers. > > > > > > Dr. Hannes (CC'ed) had...

On Thu, 2015-09-10 at 14:02 +0000, Keith Busch wrote: > On Wed, 9 Sep 2015, Ming Lin wrote: > > 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 > > > >...

On Thu, 2015-09-10 at 14:02 +0000, Keith Busch wrote: > On Wed, 9 Sep 2015, Ming Lin wrote: > > 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 > > > >...

...th: >> >> > -drive file=disk.img,format=raw,if=none,id=D22 \ >> >> > -device virtio-nvme-pci,drive=D22,serial=1234,num_queues=4 >> >> > >> >> > The goal is to have a full NVMe stack from VM guest(virtio-nvme) >> >> > to host(vhost_nvme) to LIO NVMe-over-fabrics target. >> >> >> >> Why is a virtio-nvme guest device needed? I guess there must either >> >> be NVMe-only features that you want to pass through, or you think the >> >> performance will be significantly better than virtio-...

...(CCed), could you correct me if I'm wrong? > > > > For SCSI stack, we have: > > virtio-scsi(guest) > > tcm_vhost(or vhost_scsi, host) > > LIO-scsi-target > > > > For NVMe stack, we'll have similar components: > > virtio-nvme(guest) > > vhost_nvme(host) > > LIO-NVMe-target > > > > I think it's more interesting to consider a 'vhost style' driver that > can be used with unmodified nvme host OS drivers. > > Dr. Hannes (CC'ed) had done something like this for megasas a few years > back using spec...

...(CCed), could you correct me if I'm wrong? > > > > For SCSI stack, we have: > > virtio-scsi(guest) > > tcm_vhost(or vhost_scsi, host) > > LIO-scsi-target > > > > For NVMe stack, we'll have similar components: > > virtio-nvme(guest) > > vhost_nvme(host) > > LIO-NVMe-target > > > > I think it's more interesting to consider a 'vhost style' driver that > can be used with unmodified nvme host OS drivers. > > Dr. Hannes (CC'ed) had done something like this for megasas a few years > back using spec...

...t;> Nick(CCed), could you correct me if I'm wrong? >> >> For SCSI stack, we have: >> virtio-scsi(guest) >> tcm_vhost(or vhost_scsi, host) >> LIO-scsi-target >> >> For NVMe stack, we'll have similar components: >> virtio-nvme(guest) >> vhost_nvme(host) >> LIO-NVMe-target >> > > I think it's more interesting to consider a 'vhost style' driver that > can be used with unmodified nvme host OS drivers. > > Dr. Hannes (CC'ed) had done something like this for megasas a few years > back using specializ...

...t;> Nick(CCed), could you correct me if I'm wrong? >> >> For SCSI stack, we have: >> virtio-scsi(guest) >> tcm_vhost(or vhost_scsi, host) >> LIO-scsi-target >> >> For NVMe stack, we'll have similar components: >> virtio-nvme(guest) >> vhost_nvme(host) >> LIO-NVMe-target >> > > I think it's more interesting to consider a 'vhost style' driver that > can be used with unmodified nvme host OS drivers. > > Dr. Hannes (CC'ed) had done something like this for megasas a few years > back using specializ...

..., basically modified from virtio-blk and nvme code. As title said, request for your comments. Play it in Qemu with: -drive file=disk.img,format=raw,if=none,id=D22 \ -device virtio-nvme-pci,drive=D22,serial=1234,num_queues=4 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 .-------------------------....

..., basically modified from virtio-blk and nvme code. As title said, request for your comments. Play it in Qemu with: -drive file=disk.img,format=raw,if=none,id=D22 \ -device virtio-nvme-pci,drive=D22,serial=1234,num_queues=4 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 .-------------------------....

On Wed, 9 Sep 2015, Ming Lin wrote: > 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 > > .-----------------...

...vme code. > > As title said, request for your comments. > > Play it in Qemu with: > -drive file=disk.img,format=raw,if=none,id=D22 \ > -device virtio-nvme-pci,drive=D22,serial=1234,num_queues=4 > > The goal is to have a full NVMe stack from VM guest(virtio-nvme) > to host(vhost_nvme) to LIO NVMe-over-fabrics target. Why is a virtio-nvme guest device needed? I guess there must either be NVMe-only features that you want to pass through, or you think the performance will be significantly better than virtio-blk/virtio-scsi? At first glance it seems like the virtio_nvme guest d...