From: "Michael S. Tsirkin" <mst@redhat.com>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: 侯英乐 <houyingle@sudoinfotech.com>,
"Stefan Hajnoczi" <stefanha@redhat.com>,
virtio-comment <virtio-comment@lists.oasis-open.org>,
"Christoph Hellwig" <hch@lst.de>,
"Keith Busch" <kbusch@kernel.org>,
"Kevin Wolf" <kwolf@redhat.com>,
"Klaus Jensen" <k.jensen@samsung.com>,
sgarzare <sgarzare@redhat.com>
Subject: Re: [virtio-comment] About adding a new device type virtio-nvme
Date: Wed, 18 Jan 2023 08:29:45 -0500 [thread overview]
Message-ID: <20230118082858-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <feb36edc-44bd-8604-ac3b-333eddb05222@nvidia.com>
On Wed, Jan 18, 2023 at 01:27:35PM +0200, Max Gurtovoy wrote:
> What I don't understand is why we can't start merging the infrastructure we
> worked on almost 2 years in parallel to unrelated vDPA efforts.
Is all this pertinent to the virtio specification in some way?
--
MST
This publicly archived list offers a means to provide input to the
OASIS Virtual I/O Device (VIRTIO) TC.
In order to verify user consent to the Feedback License terms and
to minimize spam in the list archive, subscription is required
before posting.
Subscribe: virtio-comment-subscribe@lists.oasis-open.org
Unsubscribe: virtio-comment-unsubscribe@lists.oasis-open.org
List help: virtio-comment-help@lists.oasis-open.org
List archive: https://lists.oasis-open.org/archives/virtio-comment/
Feedback License: https://www.oasis-open.org/who/ipr/feedback_license.pdf
List Guidelines: https://www.oasis-open.org/policies-guidelines/mailing-lists
Committee: https://www.oasis-open.org/committees/virtio/
Join OASIS: https://www.oasis-open.org/join/
next prev parent reply other threads:[~2023-01-18 13:29 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-11 3:21 [virtio-comment] About adding a new device type virtio-nvme 侯英乐
2023-01-11 15:16 ` Stefan Hajnoczi
2023-01-17 2:04 ` 侯英乐
2023-01-17 8:32 ` David Hildenbrand
2023-01-17 9:30 ` 侯英乐
[not found] ` <202301171730174296359@sudoinfotech.com>
2023-01-17 9:41 ` 侯英乐
2023-01-17 15:34 ` Stefan Hajnoczi
2023-01-17 15:47 ` David Hildenbrand
2023-01-18 2:38 ` 侯英乐
2023-01-18 2:15 ` 侯英乐
2023-01-18 14:08 ` Stefan Hajnoczi
2023-01-19 8:31 ` 侯英乐
2023-01-18 14:14 ` Stefan Hajnoczi
2023-01-19 3:40 ` Jason Wang
2023-01-19 16:59 ` Stefan Hajnoczi
2023-01-19 9:03 ` 侯英乐
2023-01-19 17:03 ` Stefan Hajnoczi
2023-01-19 3:38 ` Jason Wang
2023-01-19 7:22 ` 侯英乐
2023-01-17 16:01 ` Stefan Hajnoczi
[not found] ` <20230117162114.GA24976@lst.de>
2023-01-17 16:53 ` Stefan Hajnoczi
2023-01-18 11:22 ` Michael S. Tsirkin
2023-01-18 2:49 ` 侯英乐
2023-02-05 12:33 ` Michael S. Tsirkin
2023-02-09 3:28 ` 侯英乐
2023-02-17 3:01 ` Parav Pandit
2023-01-19 11:42 ` Michael S. Tsirkin
2023-01-29 3:32 ` 侯英乐
2023-01-30 20:30 ` Stefan Hajnoczi
2023-01-17 17:19 ` Max Gurtovoy
2023-01-18 3:23 ` 侯英乐
2023-01-18 10:09 ` Max Gurtovoy
2023-01-18 11:12 ` Michael S. Tsirkin
2023-01-18 11:27 ` Max Gurtovoy
2023-01-18 13:29 ` Michael S. Tsirkin [this message]
2023-01-19 10:19 ` 侯英乐
2023-01-19 10:33 ` Max Gurtovoy
2023-01-19 11:02 ` 侯英乐
2023-01-19 17:15 ` Stefan Hajnoczi
2023-01-18 10:28 ` Michael S. Tsirkin
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=20230118082858-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=hch@lst.de \
--cc=houyingle@sudoinfotech.com \
--cc=k.jensen@samsung.com \
--cc=kbusch@kernel.org \
--cc=kwolf@redhat.com \
--cc=mgurtovoy@nvidia.com \
--cc=sgarzare@redhat.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.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