From: "Michael S. Tsirkin" <mst@redhat.com>
To: "Zhu, Lingshan" <lingshan.zhu@intel.com>
Cc: Jason Wang <jasowang@redhat.com>,
Cornelia Huck <cohuck@redhat.com>,
Stefano Garzarella <sgarzare@redhat.com>,
Stefan Hajnoczi <stefanha@redhat.com>,
nrupal.jani@intel.com, "Uminski, Piotr" <Piotr.Uminski@intel.com>,
hang.yuan@intel.com, virtio-comment@lists.oasis-open.org
Subject: Re: [virtio-comment] [PATCH V3 RESEND 1/4] Introduce virito transport virtqueue
Date: Tue, 9 Aug 2022 05:12:31 -0400 [thread overview]
Message-ID: <20220809050941-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <1f82b84c-db9d-69c1-6a41-a4573036ce0c@intel.com>
On Tue, Aug 09, 2022 at 04:36:43PM +0800, Zhu, Lingshan wrote:
> > > +
> > > +A device that offers feature bit VIRTIO_F_TRANSPT_VQ and a transport virtqueue is a management device.
> > > +It processes the commands through the transport virtqueue commands.
> > I think we need to be verbose here, e.g what did those transport
> > virtqueue commands do? What's the relationship between management
> > device and managed device?
> I will add an overview of the transport virtqueue commands here, and a
> description of the relationship in the "managed device" section.
Transport is fine but management of devices is clearly something
nvidia's patches do. So I think it's best to reuse the concept of device
groups for this, from Max's patchset. Let's not replicate that work at
least. I promised Max to help a bit with wording so I'll soon send a
revision of his patchset, the generic part about device group
from which you should be able to reuse.
--
MST
next prev parent reply other threads:[~2022-08-09 9:12 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-05 9:53 [virtio-comment] [PATCH V3 RESEND 0/4] Introduce virtio transport virtqueue Zhu Lingshan
2022-08-05 9:53 ` [virtio-comment] [PATCH V3 RESEND 1/4] Introduce virito " Zhu Lingshan
2022-08-08 9:12 ` Jason Wang
2022-08-09 8:36 ` Zhu, Lingshan
2022-08-09 9:12 ` Michael S. Tsirkin [this message]
2022-08-09 9:19 ` Zhu, Lingshan
2022-08-09 9:21 ` Jason Wang
2022-08-09 9:28 ` Zhu, Lingshan
2022-08-09 9:31 ` Jason Wang
2022-08-09 9:35 ` Michael S. Tsirkin
2022-08-09 9:37 ` Jason Wang
2022-08-09 9:43 ` Zhu, Lingshan
2022-08-09 9:33 ` Michael S. Tsirkin
2022-08-09 9:29 ` Michael S. Tsirkin
2022-08-09 9:43 ` Zhu, Lingshan
2022-08-09 20:57 ` Michael S. Tsirkin
2022-08-09 9:28 ` Jason Wang
2022-08-09 21:03 ` Michael S. Tsirkin
2022-08-10 7:41 ` Jason Wang
2022-08-10 9:04 ` Michael S. Tsirkin
2022-08-05 9:53 ` [virtio-comment] [PATCH V3 RESEND 2/4] Introduce the commands set of the transport vq Zhu Lingshan
2022-08-08 10:04 ` Jason Wang
2022-08-09 13:09 ` Zhu, Lingshan
2022-08-10 1:56 ` Jason Wang
2022-08-10 8:49 ` Zhu, Lingshan
2022-08-10 12:58 ` Michael S. Tsirkin
2022-08-16 5:55 ` Zhu, Lingshan
2022-08-16 6:21 ` Michael S. Tsirkin
2022-08-16 8:53 ` Zhu, Lingshan
2022-08-10 9:34 ` Michael S. Tsirkin
2022-08-16 9:02 ` Zhu, Lingshan
2022-08-05 9:53 ` [virtio-comment] [PATCH V3 RESEND 3/4] Describe the process to present a managed device Zhu Lingshan
2022-08-05 9:53 ` [virtio-comment] [PATCH V3 RESEND 4/4] Add transport vq number for virtio blk and net Zhu Lingshan
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=20220809050941-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=Piotr.Uminski@intel.com \
--cc=cohuck@redhat.com \
--cc=hang.yuan@intel.com \
--cc=jasowang@redhat.com \
--cc=lingshan.zhu@intel.com \
--cc=nrupal.jani@intel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.