From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Message-ID: <128c6de4-2e48-be65-684b-e8ab29099e3c@intel.com> Date: Tue, 2 Aug 2022 21:21:57 +0800 MIME-Version: 1.0 Subject: Re: [virtio-comment] Re: [PATCH V2 0/5] Introduce virtio transport virtqueue References: <20220801093216.362119-1-lingshan.zhu@intel.com> <20220801165438-mutt-send-email-mst@kernel.org> From: "Zhu, Lingshan" In-Reply-To: <20220801165438-mutt-send-email-mst@kernel.org> Content-Language: en-US Content-Type: text/plain; charset="utf-8"; format="flowed" Content-Transfer-Encoding: 8bit To: "Michael S. Tsirkin" 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 List-ID: On 8/2/2022 4:56 AM, Michael S. Tsirkin wrote: > 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. > > Overall I'm happy with the progress made here. Pls keep iterating. Sure, will do, thanks! > I would like to see whether we can unify this with the admin > queue work somehow. The technology is different (SIOV vs SRIOV) > but there are also similarities. > > Do you care to review some patches from the admin queue proposals maybe? IMHO, I think this transport vq series focus on introducing a new virtio transport layer for hyper scaling, like SIOV. And the admin vq proposal looks focusing on administration, to control the sub-devices. so maybe the transport vq and the admin vq are works in parallel. > > >> 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. >> >> 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 > > 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/ >