Linux-NVME Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: mlin@kernel.org (Ming Lin)
Subject: [RFC] Multi level NVMe stack
Date: Wed, 29 Jul 2015 16:55:18 -0700	[thread overview]
Message-ID: <1438214118.24174.9.camel@ssi> (raw)

Hi,

I'm working on a virtio-nvme driver.
NVMe over Fabrics initiator will probably be available some time.

I wonder does it make sense to have a multi level NVMe stack(similar as
SCSI). So we can re-use the NVMe core code.

                        .-------------------------.
                        | /dev/nvme0n1 register   |
  Upper level           | NVMe protocol process   |
                        |                         |
                        '-------------------------'



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

Thanks,
Ming

             reply	other threads:[~2015-07-29 23:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29 23:55 Ming Lin [this message]
2015-07-30 14:52 ` [RFC] Multi level NVMe stack Christoph Hellwig
2015-07-31 17:04   ` Ming Lin
2015-08-18 23:11     ` Ming Lin

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=1438214118.24174.9.camel@ssi \
    --to=mlin@kernel.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