linux-nvme.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: mlin@kernel.org (Ming Lin)
Subject: [PATCH] Move nvme driver source into subdirectory and move pci specifics from core into separate file
Date: Fri, 9 Oct 2015 10:38:40 -0700	[thread overview]
Message-ID: <CAF1ivSa4zCLHenbwT3GNk2gkWWPQwM_G5M_FtrEY9rVq8n7iVg@mail.gmail.com> (raw)
In-Reply-To: <20150926161121.GB30551@infradead.org>

On Sat, Sep 26, 2015@9:11 AM, Christoph Hellwig <hch@infradead.org> wrote:
> On Fri, Sep 25, 2015@10:32:36PM -0700, Ming Lin wrote:
>> >  a) move files to a new directory.  My suggestion for that would be
>> >     driver/nvme/host/ as I have a software NVMe controller
>> >     implementation under development which I'd like to also add under
>> >     a different subdirectory of drivers/nvme.
>>
>> What's the "software NVMe controller"? Is it the initiator for NVMe
>> over fabrics?
>
> It's a software implementation of the NVMe subsystem and controller
> interface.  It could be frontended by a future fabrics implementation,
> a virtio-nvme implementation, a nvme-loop implementation or with some
> additional work maybe even a Linux-based PCIe target device.

Hi Christoph,

I have been writing vhost-nvme driver for a while.
http://www.minggr.net/cgit/cgit.cgi/linux/commit/?h=vhost-nvme/v1

Seems I have to do similar submission/completion queue simulation
in vhost-nvme as in qemu/nvme.c.

Will the "software NVMe controller" do these simulation?
If yes, could you share a draft version then I can try build vhost-nvme
on top of it?

Thanks.

  reply	other threads:[~2015-10-09 17:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-24 21:27 [PATCH] Move nvme driver source into subdirectory and move pci specifics from core into separate file J Freyensee
2015-09-25  0:02 ` Christoph Hellwig
2015-09-25 15:12   ` J Freyensee
2015-09-26 16:09     ` Christoph Hellwig
2015-09-26  5:32   ` Ming Lin
2015-09-26 16:11     ` Christoph Hellwig
2015-10-09 17:38       ` Ming Lin [this message]
2015-10-10  7:30         ` Christoph Hellwig

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=CAF1ivSa4zCLHenbwT3GNk2gkWWPQwM_G5M_FtrEY9rVq8n7iVg@mail.gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).