From: "Michael S. Tsirkin" <mst@redhat.com>
To: Zhu Lingshan <lingshan.zhu@intel.com>
Cc: jasowang@redhat.com, cohuck@redhat.com, sgarzare@redhat.com,
stefanha@redhat.com, nrupal.jani@intel.com,
Piotr.Uminski@intel.com, virtio-comment@lists.oasis-open.org
Subject: Re: [PATCH V2 0/5] Introduce virtio transport virtqueue
Date: Mon, 1 Aug 2022 05:48:28 -0400 [thread overview]
Message-ID: <20220801054425-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220801093216.362119-1-lingshan.zhu@intel.com>
On Mon, Aug 01, 2022 at 05:32:11PM +0800, Zhu Lingshan wrote:
> This series introduces virtio transport virtqueue as a new
> transport layer for virtio devices.
>
> This series defines the concepts of virtio management device
> and virtio managed devices.
>
> This series also defines a commands set over the transport virtqueue,
> including:
> The command to query available resources of the management device
> The commands to create / destroy the managed devices.
> The commands to config the managed devices.
> The commands to config virtqueues of the managed devices.
Is there interest in at least analysing how this interacts with the
recent admin queue proposals?
I see some similarity in what these are trying to address - for example,
feature bit provisioning - any analysis on how the two proposals
compare?
> Changes form V1:
> 1)Add a command to set per-vq asid(Jason)
> 2)Add a command to reset a virtqueue(Jason)
> 3)Add support for packed virtqueue state(Jason)
> 4)Allow nested managed devices(Jason)
> 5)Provides device feature bits in the provisioning(Jason)
> 6)Removed most of the error codes, only left OK and ERR(Jason)
> 7)“virtual devices” is renamed to “managed devices”, to be more general(Jason)
>
> Zhu Lingshan (5):
> Introduce virito transport virtqueue
> Introduce feature bit VIRTIO_F_TRANSPT_VQ_MDEV
> Introduce the commands set of the transport vq
> Describe the process to present a managed device
> Add transport vq number for virtio blk and net
>
> content.tex | 784 +++++++++++++++++++++++++++++++++++++++++++++++
> introduction.tex | 3 +
> 2 files changed, 787 insertions(+)
>
> --
> 2.35.3
next prev parent reply other threads:[~2022-08-01 9:48 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-01 9:32 [PATCH V2 0/5] Introduce virtio transport virtqueue Zhu Lingshan
2022-08-01 9:32 ` [PATCH V2 1/5] Introduce virito " Zhu Lingshan
2022-08-01 20:25 ` Michael S. Tsirkin
2022-08-02 2:54 ` Zhu, Lingshan
2022-08-01 9:32 ` [PATCH V2 2/5] Introduce feature bit VIRTIO_F_TRANSPT_VQ_MDEV Zhu Lingshan
2022-08-01 20:27 ` [virtio-comment] " Michael S. Tsirkin
2022-08-02 3:17 ` Zhu, Lingshan
2022-08-02 6:32 ` Zhu, Lingshan
2022-08-02 6:52 ` Michael S. Tsirkin
2022-08-02 11:54 ` Zhu, Lingshan
2022-08-02 12:55 ` Michael S. Tsirkin
2022-08-02 13:15 ` Zhu, Lingshan
2022-08-02 13:20 ` Michael S. Tsirkin
2022-08-02 13:32 ` Zhu, Lingshan
2022-08-02 13:37 ` Zhu, Lingshan
2022-08-01 9:32 ` [PATCH V2 3/5] Introduce the commands set of the transport vq Zhu Lingshan
2022-08-01 20:53 ` Michael S. Tsirkin
2022-08-02 13:07 ` [virtio-comment] " Zhu, Lingshan
2022-08-01 9:32 ` [PATCH V2 4/5] Describe the process to present a managed device Zhu Lingshan
2022-08-01 9:32 ` [PATCH V2 5/5] Add transport vq number for virtio blk and net Zhu Lingshan
2022-08-01 20:54 ` Michael S. Tsirkin
2022-08-01 9:48 ` Michael S. Tsirkin [this message]
2022-08-01 20:56 ` [PATCH V2 0/5] Introduce virtio transport virtqueue Michael S. Tsirkin
2022-08-02 13:18 ` [virtio-comment] " Zhu, Lingshan
2022-08-02 13:21 ` 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=20220801054425-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=Piotr.Uminski@intel.com \
--cc=cohuck@redhat.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.