search for: tcm_eventfd_nvm

...r on KVM host would be handling some amount of > NVMe host interface emulation in kernel code, and would be able to > decode nvme Read/Write/Flush operations and translate -> submit to > existing backend drivers. Let me call the "eventfd based LIO NVMe fabric driver" as "tcm_eventfd_nvme" Currently, LIO frontend driver(iscsi, fc, vhost-scsi etc) talk to LIO backend driver(fileio, iblock etc) with SCSI commands. Did you mean the "tcm_eventfd_nvme" driver need to translate NVMe commands to SCSI commands and then submit to backend driver? But I thought the future &q...

...r on KVM host would be handling some amount of > NVMe host interface emulation in kernel code, and would be able to > decode nvme Read/Write/Flush operations and translate -> submit to > existing backend drivers. Let me call the "eventfd based LIO NVMe fabric driver" as "tcm_eventfd_nvme" Currently, LIO frontend driver(iscsi, fc, vhost-scsi etc) talk to LIO backend driver(fileio, iblock etc) with SCSI commands. Did you mean the "tcm_eventfd_nvme" driver need to translate NVMe commands to SCSI commands and then submit to backend driver? But I thought the future &q...

...g some amount of > > NVMe host interface emulation in kernel code, and would be able to > > decode nvme Read/Write/Flush operations and translate -> submit to > > existing backend drivers. > > Let me call the "eventfd based LIO NVMe fabric driver" as > "tcm_eventfd_nvme" > > Currently, LIO frontend driver(iscsi, fc, vhost-scsi etc) talk to LIO > backend driver(fileio, iblock etc) with SCSI commands. > > Did you mean the "tcm_eventfd_nvme" driver need to translate NVMe > commands to SCSI commands and then submit to backend driver...

...; NVMe host interface emulation in kernel code, and would be able to > > > decode nvme Read/Write/Flush operations and translate -> submit to > > > existing backend drivers. > > > > Let me call the "eventfd based LIO NVMe fabric driver" as > > "tcm_eventfd_nvme" > > > > Currently, LIO frontend driver(iscsi, fc, vhost-scsi etc) talk to LIO > > backend driver(fileio, iblock etc) with SCSI commands. > > > > Did you mean the "tcm_eventfd_nvme" driver need to translate NVMe > > commands to SCSI commands and...

...; NVMe host interface emulation in kernel code, and would be able to > > > decode nvme Read/Write/Flush operations and translate -> submit to > > > existing backend drivers. > > > > Let me call the "eventfd based LIO NVMe fabric driver" as > > "tcm_eventfd_nvme" > > > > Currently, LIO frontend driver(iscsi, fc, vhost-scsi etc) talk to LIO > > backend driver(fileio, iblock etc) with SCSI commands. > > > > Did you mean the "tcm_eventfd_nvme" driver need to translate NVMe > > commands to SCSI commands and...

On Wed, 2015-09-16 at 23:10 -0700, Nicholas A. Bellinger wrote: > Hi Ming & Co, > > On Thu, 2015-09-10 at 10:28 -0700, Ming Lin wrote: > > On Thu, 2015-09-10 at 15:38 +0100, Stefan Hajnoczi wrote: > > > On Thu, Sep 10, 2015 at 6:48 AM, Ming Lin <mlin at kernel.org> wrote: > > > > These 2 patches added virtio-nvme to kernel and qemu, > > >

On Wed, 2015-09-16 at 23:10 -0700, Nicholas A. Bellinger wrote: > Hi Ming & Co, > > On Thu, 2015-09-10 at 10:28 -0700, Ming Lin wrote: > > On Thu, 2015-09-10 at 15:38 +0100, Stefan Hajnoczi wrote: > > > On Thu, Sep 10, 2015 at 6:48 AM, Ming Lin <mlin at kernel.org> wrote: > > > > These 2 patches added virtio-nvme to kernel and qemu, > > >

...; On Thu, 2015-09-17 at 17:55 -0700, Nicholas A. Bellinger wrote: <SNIP> > > IBLOCK + FILEIO + RD_MCP don't speak SCSI, they simply process I/Os with > > LBA + length based on SGL memory or pass along a FLUSH with LBA + > > length. > > > > So once the 'tcm_eventfd_nvme' driver on KVM host receives a nvme host > > hardware frame via eventfd, it would decode the frame and send along the > > Read/Write/Flush when exposing existing (non nvme native) backend > > drivers. > > Learned vhost architecture: > http://blog.vmsplice.net/2011/0...