virtualization.lists.linux-foundation.org archive mirror
 help / color / mirror / Atom feed
From: Ming Lin <mlin@kernel.org>
To: linux-nvme@lists.infradead.org,
	virtualization@lists.linux-foundation.org
Cc: Ming Lin <mlin@kernel.org>, Christoph Hellwig <hch@lst.de>
Subject: [RFC PATCH 0/2] virtio nvme
Date: Wed,  9 Sep 2015 22:48:30 -0700	[thread overview]
Message-ID: <1441864112-12765-1-git-send-email-mlin@kernel.org> (raw)

Hi all,

These 2 patches added virtio-nvme to kernel and qemu,
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

                        .-------------------------.
                        | NVMe device register    |
  Upper level           | NVMe protocol process   |
                        |                         |
                        '-------------------------'



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

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

Code also available at:
http://www.minggr.net/cgit/cgit.cgi/linux/commit/?h=virtio-nvme/v1
http://www.minggr.net/cgit/cgit.cgi/qemu/log/?h=virtio-nvme/v1

Thanks,
Ming

             reply	other threads:[~2015-09-10  5:48 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-10  5:48 Ming Lin [this message]
2015-09-10  5:48 ` [RFC PATCH 1/2] virtio_nvme(kernel): virtual NVMe driver using virtio Ming Lin
2015-09-10  5:48 ` [RFC PATCH 2/2] virtio-nvme(qemu): NVMe device " Ming Lin
2015-09-10 14:02 ` [RFC PATCH 0/2] virtio nvme Keith Busch
2015-09-10 17:02   ` Ming Lin
2015-09-11  4:55     ` Ming Lin
2015-09-11 17:46     ` J Freyensee
2015-09-10 14:38 ` Stefan Hajnoczi
2015-09-10 17:28   ` Ming Lin
2015-09-11  7:48     ` Stefan Hajnoczi
2015-09-11 17:21       ` Ming Lin
2015-09-11 17:53         ` Stefan Hajnoczi
2015-09-11 18:54           ` Ming Lin
2015-09-17  6:10     ` Nicholas A. Bellinger
     [not found]     ` <1442470241.23132.77.camel@haakon3.risingtidesystems.com>
2015-09-17 18:18       ` Ming Lin
     [not found]       ` <CAF1ivSaOZwjg3OEdj+miXsWwbpf-Y-tmN7wmjZooxTPDQ5r9tg@mail.gmail.com>
2015-09-17 21:43         ` Nicholas A. Bellinger
2015-09-17 23:31       ` Ming Lin
     [not found]       ` <1442532687.4750.6.camel@ssi>
2015-09-18  0:55         ` Nicholas A. Bellinger
     [not found]         ` <1442537752.11959.35.camel@haakon3.risingtidesystems.com>
2015-09-18 18:12           ` Ming Lin
     [not found]           ` <1442599957.11660.8.camel@ssi>
2015-09-18 21:09             ` Nicholas A. Bellinger
2015-09-18 23:05               ` Ming Lin
2015-09-23 22:58               ` Ming Lin
2015-09-27  5:01                 ` Nicholas A. Bellinger
     [not found]                 ` <1443330116.15432.57.camel@haakon3.risingtidesystems.com>
2015-09-27  6:49                   ` Ming Lin
2015-09-28  5:58                   ` Hannes Reinecke

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1441864112-12765-1-git-send-email-mlin@kernel.org \
    --to=mlin@kernel.org \
    --cc=hch@lst.de \
    --cc=linux-nvme@lists.infradead.org \
    --cc=virtualization@lists.linux-foundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).