From: Christoph Hellwig <hch@lst.de>
To: Michal Wnukowski <wnukowski@google.com>
Cc: Linus Torvalds <torvalds@linux-foundation.org>,
keith.busch@linux.intel.com, Jens Axboe <axboe@fb.com>,
Sagi Grimberg <sagi@grimberg.me>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
linux-nvme <linux-nvme@lists.infradead.org>,
Keith Busch <keith.busch@intel.com>,
yigitfiliz@google.com, Christoph Hellwig <hch@lst.de>
Subject: Re: [PATCH] Bugfix for handling of shadow doorbell buffer.
Date: Fri, 17 Aug 2018 09:10:09 +0200 [thread overview]
Message-ID: <20180817071009.GB11383@lst.de> (raw)
In-Reply-To: <d57e77d8-88e2-b92a-9545-7118de4d8065@google.com>
On Tue, Aug 14, 2018 at 06:35:16PM -0700, Michal Wnukowski wrote:
>
> The other side in this case is not actual controller hardware, but
> virtual one (the regular hardware should rely on normal MMIO
> doorbells).
There could very much be real hardware there. We've made it clear
in the spec that while a typical use case is a virtualized controller
there is nothing peventing hardware implementations. There have
been previous hardware prototypes to use very similar tricks, e.g.:
https://www.usenix.org/node/179878
prev parent reply other threads:[~2018-08-17 7:09 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-14 22:17 Michal Wnukowski
2018-08-14 22:57 ` Keith Busch
2018-08-14 23:16 ` Linus Torvalds
2018-08-14 23:49 ` Keith Busch
2018-08-15 1:35 ` Michal Wnukowski
2018-08-15 2:02 ` Linus Torvalds
2018-08-15 22:51 ` [PATCH v2] " Michal Wnukowski
2018-08-16 14:15 ` Keith Busch
2018-08-16 21:20 ` Sagi Grimberg
2018-08-17 7:07 ` Christoph Hellwig
2018-08-20 20:09 ` Michal Wnukowski
2018-08-17 7:10 ` Christoph Hellwig [this message]
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=20180817071009.GB11383@lst.de \
--to=hch@lst.de \
--cc=axboe@fb.com \
--cc=keith.busch@intel.com \
--cc=keith.busch@linux.intel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-nvme@lists.infradead.org \
--cc=sagi@grimberg.me \
--cc=torvalds@linux-foundation.org \
--cc=wnukowski@google.com \
--cc=yigitfiliz@google.com \
/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
all inboxes | Powered by JetHome®