From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, jasowang@redhat.com,
cohuck@redhat.com, sgarzare@redhat.com, stefanha@redhat.com,
nrupal.jani@intel.com, Piotr.Uminski@intel.com,
hang.yuan@intel.com, virtio@lists.oasis-open.org,
Jiri Pirko <jiri@nvidia.com>,
Zhu Lingshan <lingshan.zhu@intel.com>,
pasic@linux.ibm.com, Shahaf Shuler <shahafs@nvidia.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: [virtio-comment] Re: [PATCH v11 04/10] admin: introduce virtio admin virtqueues
Date: Mon, 10 Apr 2023 09:22:45 -0400 [thread overview]
Message-ID: <20230410092104-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <2ebedc33-1fa8-1fe5-67eb-8d657cf932db@nvidia.com>
On Thu, Apr 06, 2023 at 12:08:03AM -0400, Parav Pandit wrote:
>
>
> On 4/3/2023 11:03 AM, Michael S. Tsirkin wrote:
> > The admin virtqueues will be the first interface used to issue admin commands.
> >
> The admin virtqueue
>
> > Currently the virtio specification defines control virtqueue to manipulate
> > features and configuration of the device it operates on:
> > virtio-net, virtio-scsi, etc all have existing control virtqueues. However,
> > control virtqueue commands are device type specific, which makes it very
> > difficult to extend for device agnostic commands.
> >
> > Keeping the device-specific virtqueue separate from the admin virtqueue
> > is simpler and has fewer potential problems.
>
> > I don't think creating
> > common infrastructure for device-specific control virtqueues across
> > device types worthwhile or within the scope of this patch series.
> > > To support this requirement in a more generic way, this patch introduces
> > a new admin virtqueue interface.
> > The admin virtqueue can be seen as the virtqueue analog to a transport.
> > The admin queue thus does nothing device type-specific (net, scsi, etc)
> > and instead focuses on transporting the admin commands.
> >
> > We also support more than one admin virtqueue, for QoS and
> > scalability requirements.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> >
> > ---
> > explain ordering of commands as suggested by Stefan
> > dropped Max's S.O.B
> > reword commit log as suggested by David
> > minor wording fixes suggested by David
> > ---
> > admin.tex | 75 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> > content.tex | 7 +++--
> > 2 files changed, 80 insertions(+), 2 deletions(-)
> >
> > diff --git a/admin.tex b/admin.tex
> > index c869a1a..f201bcd 100644
> > --- a/admin.tex
> > +++ b/admin.tex
> > @@ -182,3 +182,78 @@ \subsection{Group administration commands}\label{sec:Basic Facilities of a Virti
> > \field{command_specific_data} and \field{command_specific_result}
> > depends on these structures and is described separately or is
> > implicit in the structure description.
> > +
> > +\section{Administration Virtqueues}\label{sec:Basic Facilities of a Virtio Device / Administration Virtqueues}
> > +
> > +An administration virtqueue of an owner device is used to submit
> > +group administration commands. An owner device can have more
> > +than one administration virtqueue.
> > +
> > +If VIRTIO_F_ADMIN_VQ has been negotiated, an owner device exposes one
> > +or more adminstration virtqueues. The number and locations of the
> > +administration virtqueues are exposed by the owner device in a transport
> > +specific manner.
> > +
> > +The driver queues requests to an arbitrary administration
> The driver enqueues
Not sure why - these are synonims - and this variant is more popular:
[mst@tuck virtio]$ git grep 'The driver queues'
admin.tex:The driver queues requests to an arbitrary administration
content.tex:The driver queues requests to the virtqueues, and they are used by
content.tex:The driver queues requests to an arbitrary request queue, and
virtio-gpio.tex:\item The driver queues \field{struct virtio_gpio_request} and
virtio-i2c.tex:The driver queues requests to the virtqueue, and they are used by the
virtio-vsock.tex:The driver queues outgoing packets on the tx virtqueue and incoming packet
[mst@tuck virtio]$ git grep 'The driver enqueues'
virtio-fs.tex:The driver enqueues normal requests on an arbitrary request queue. High
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/
WARNING: multiple messages have this Message-ID (diff)
From: "Michael S. Tsirkin" <mst@redhat.com>
To: Parav Pandit <parav@nvidia.com>
Cc: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, jasowang@redhat.com,
cohuck@redhat.com, sgarzare@redhat.com, stefanha@redhat.com,
nrupal.jani@intel.com, Piotr.Uminski@intel.com,
hang.yuan@intel.com, virtio@lists.oasis-open.org,
Jiri Pirko <jiri@nvidia.com>,
Zhu Lingshan <lingshan.zhu@intel.com>,
pasic@linux.ibm.com, Shahaf Shuler <shahafs@nvidia.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: [virtio-dev] Re: [PATCH v11 04/10] admin: introduce virtio admin virtqueues
Date: Mon, 10 Apr 2023 09:22:45 -0400 [thread overview]
Message-ID: <20230410092104-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <2ebedc33-1fa8-1fe5-67eb-8d657cf932db@nvidia.com>
On Thu, Apr 06, 2023 at 12:08:03AM -0400, Parav Pandit wrote:
>
>
> On 4/3/2023 11:03 AM, Michael S. Tsirkin wrote:
> > The admin virtqueues will be the first interface used to issue admin commands.
> >
> The admin virtqueue
>
> > Currently the virtio specification defines control virtqueue to manipulate
> > features and configuration of the device it operates on:
> > virtio-net, virtio-scsi, etc all have existing control virtqueues. However,
> > control virtqueue commands are device type specific, which makes it very
> > difficult to extend for device agnostic commands.
> >
> > Keeping the device-specific virtqueue separate from the admin virtqueue
> > is simpler and has fewer potential problems.
>
> > I don't think creating
> > common infrastructure for device-specific control virtqueues across
> > device types worthwhile or within the scope of this patch series.
> > > To support this requirement in a more generic way, this patch introduces
> > a new admin virtqueue interface.
> > The admin virtqueue can be seen as the virtqueue analog to a transport.
> > The admin queue thus does nothing device type-specific (net, scsi, etc)
> > and instead focuses on transporting the admin commands.
> >
> > We also support more than one admin virtqueue, for QoS and
> > scalability requirements.
> >
> > Signed-off-by: Michael S. Tsirkin <mst@redhat.com>
> >
> > ---
> > explain ordering of commands as suggested by Stefan
> > dropped Max's S.O.B
> > reword commit log as suggested by David
> > minor wording fixes suggested by David
> > ---
> > admin.tex | 75 +++++++++++++++++++++++++++++++++++++++++++++++++++++
> > content.tex | 7 +++--
> > 2 files changed, 80 insertions(+), 2 deletions(-)
> >
> > diff --git a/admin.tex b/admin.tex
> > index c869a1a..f201bcd 100644
> > --- a/admin.tex
> > +++ b/admin.tex
> > @@ -182,3 +182,78 @@ \subsection{Group administration commands}\label{sec:Basic Facilities of a Virti
> > \field{command_specific_data} and \field{command_specific_result}
> > depends on these structures and is described separately or is
> > implicit in the structure description.
> > +
> > +\section{Administration Virtqueues}\label{sec:Basic Facilities of a Virtio Device / Administration Virtqueues}
> > +
> > +An administration virtqueue of an owner device is used to submit
> > +group administration commands. An owner device can have more
> > +than one administration virtqueue.
> > +
> > +If VIRTIO_F_ADMIN_VQ has been negotiated, an owner device exposes one
> > +or more adminstration virtqueues. The number and locations of the
> > +administration virtqueues are exposed by the owner device in a transport
> > +specific manner.
> > +
> > +The driver queues requests to an arbitrary administration
> The driver enqueues
Not sure why - these are synonims - and this variant is more popular:
[mst@tuck virtio]$ git grep 'The driver queues'
admin.tex:The driver queues requests to an arbitrary administration
content.tex:The driver queues requests to the virtqueues, and they are used by
content.tex:The driver queues requests to an arbitrary request queue, and
virtio-gpio.tex:\item The driver queues \field{struct virtio_gpio_request} and
virtio-i2c.tex:The driver queues requests to the virtqueue, and they are used by the
virtio-vsock.tex:The driver queues outgoing packets on the tx virtqueue and incoming packet
[mst@tuck virtio]$ git grep 'The driver enqueues'
virtio-fs.tex:The driver enqueues normal requests on an arbitrary request queue. High
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscribe@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-help@lists.oasis-open.org
next prev parent reply other threads:[~2023-04-10 13:22 UTC|newest]
Thread overview: 116+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-03 15:02 [virtio-comment] [PATCH v11 00/10] Introduce device group and device management Michael S. Tsirkin
2023-04-03 15:02 ` [virtio-dev] " Michael S. Tsirkin
2023-04-03 15:03 ` [virtio-comment] [PATCH v11 01/10] virtio: document forward compatibility guarantees Michael S. Tsirkin
2023-04-03 15:03 ` [virtio-dev] " Michael S. Tsirkin
2023-04-06 7:15 ` [virtio-comment] " Zhu, Lingshan
2023-04-06 7:15 ` [virtio-dev] " Zhu, Lingshan
2023-04-03 15:03 ` [virtio-comment] [PATCH v11 02/10] admin: introduce device group and related concepts Michael S. Tsirkin
2023-04-03 15:03 ` [virtio-dev] " Michael S. Tsirkin
2023-04-04 11:38 ` [virtio-comment] " Stefan Hajnoczi
2023-04-04 11:38 ` [virtio-dev] " Stefan Hajnoczi
2023-04-06 3:42 ` [virtio-comment] " Parav Pandit
2023-04-06 3:42 ` [virtio-dev] " Parav Pandit
2023-04-10 13:23 ` [virtio-comment] " Michael S. Tsirkin
2023-04-10 13:23 ` [virtio-dev] " Michael S. Tsirkin
2023-04-10 16:42 ` [virtio-comment] " Parav Pandit
2023-04-10 16:42 ` [virtio-dev] " Parav Pandit
2023-04-24 16:30 ` [virtio-comment] " Michael S. Tsirkin
2023-04-24 16:30 ` [virtio-dev] " Michael S. Tsirkin
2023-04-24 16:45 ` [virtio-comment] RE: [virtio] " Parav Pandit
2023-04-24 16:45 ` [virtio-dev] " Parav Pandit
2023-04-24 20:32 ` [virtio-comment] " Michael S. Tsirkin
2023-04-24 20:32 ` [virtio-dev] " Michael S. Tsirkin
2023-04-06 7:16 ` [virtio-comment] Re: [virtio-dev] " Zhu, Lingshan
2023-04-06 7:16 ` Zhu, Lingshan
2023-04-03 15:03 ` [virtio-comment] [PATCH v11 03/10] admin: introduce group administration commands Michael S. Tsirkin
2023-04-03 15:03 ` [virtio-dev] " Michael S. Tsirkin
2023-04-04 11:50 ` [virtio-comment] " Stefan Hajnoczi
2023-04-04 11:50 ` [virtio-dev] " Stefan Hajnoczi
2023-04-06 3:58 ` [virtio-comment] " Parav Pandit
2023-04-06 3:58 ` [virtio-dev] " Parav Pandit
2023-04-06 7:16 ` [virtio-comment] " Zhu, Lingshan
2023-04-06 7:16 ` [virtio-dev] " Zhu, Lingshan
2023-04-03 15:03 ` [virtio-comment] [PATCH v11 04/10] admin: introduce virtio admin virtqueues Michael S. Tsirkin
2023-04-03 15:03 ` [virtio-dev] " Michael S. Tsirkin
2023-04-04 11:58 ` [virtio-comment] " Stefan Hajnoczi
2023-04-04 11:58 ` [virtio-dev] " Stefan Hajnoczi
2023-04-06 4:08 ` [virtio-comment] " Parav Pandit
2023-04-06 4:08 ` [virtio-dev] " Parav Pandit
2023-04-10 13:22 ` Michael S. Tsirkin [this message]
2023-04-10 13:22 ` Michael S. Tsirkin
2023-04-10 14:22 ` [virtio-comment] " Parav Pandit
2023-04-10 14:22 ` [virtio-dev] " Parav Pandit
2023-04-10 20:04 ` [virtio-comment] " Michael S. Tsirkin
2023-04-10 20:04 ` [virtio-dev] " Michael S. Tsirkin
2023-04-11 13:39 ` [virtio-comment] " Parav Pandit
2023-04-11 13:39 ` [virtio-dev] " Parav Pandit
2023-04-11 14:01 ` [virtio-comment] " Michael S. Tsirkin
2023-04-11 14:01 ` [virtio-dev] " Michael S. Tsirkin
2023-04-11 15:46 ` [virtio-comment] " Parav Pandit
2023-04-11 15:46 ` [virtio-dev] " Parav Pandit
2023-04-06 7:17 ` [virtio-comment] Re: [virtio-dev] " Zhu Lingshan
2023-04-06 7:17 ` Zhu Lingshan
2023-04-03 15:03 ` [virtio-comment] [PATCH v11 05/10] pci: add admin vq registers to virtio over pci Michael S. Tsirkin
2023-04-03 15:03 ` [virtio-dev] " Michael S. Tsirkin
2023-04-04 12:52 ` [virtio-comment] " Stefan Hajnoczi
2023-04-04 12:52 ` [virtio-dev] " Stefan Hajnoczi
2023-04-06 4:14 ` [virtio-comment] " Parav Pandit
2023-04-06 4:14 ` [virtio-dev] " Parav Pandit
2023-04-24 15:36 ` [virtio-comment] " Michael S. Tsirkin
2023-04-24 15:36 ` [virtio-dev] " Michael S. Tsirkin
2023-04-06 7:17 ` [virtio-comment] Re: [virtio] " Zhu, Lingshan
2023-04-06 7:17 ` [virtio-dev] " Zhu, Lingshan
2023-04-03 15:03 ` [virtio-comment] [PATCH v11 06/10] mmio: document ADMIN_VQ as reserved Michael S. Tsirkin
2023-04-03 15:03 ` [virtio-dev] " Michael S. Tsirkin
2023-04-03 15:54 ` [virtio-comment] " Parav Pandit
2023-04-03 15:54 ` [virtio-dev] " Parav Pandit
2023-04-24 15:38 ` [virtio-comment] " Michael S. Tsirkin
2023-04-24 15:38 ` [virtio-dev] " Michael S. Tsirkin
2023-04-06 7:18 ` [virtio-comment] " Zhu Lingshan
2023-04-06 7:18 ` [virtio-dev] " Zhu Lingshan
2023-04-03 15:03 ` [virtio-comment] [PATCH v11 07/10] ccw: " Michael S. Tsirkin
2023-04-03 15:03 ` [virtio-dev] " Michael S. Tsirkin
2023-04-03 15:55 ` [virtio-comment] " Parav Pandit
2023-04-03 15:55 ` [virtio-dev] " Parav Pandit
2023-04-03 17:29 ` [virtio-comment] " Michael S. Tsirkin
2023-04-03 17:29 ` [virtio-dev] " Michael S. Tsirkin
2023-04-06 4:15 ` [virtio-comment] " Parav Pandit
2023-04-06 4:15 ` [virtio-dev] " Parav Pandit
2023-04-06 7:18 ` [virtio-comment] Re: [virtio-dev] " Zhu Lingshan
2023-04-06 7:18 ` Zhu Lingshan
2023-04-03 15:03 ` [virtio-comment] [PATCH v11 08/10] admin: command list discovery Michael S. Tsirkin
2023-04-03 15:03 ` [virtio-dev] " Michael S. Tsirkin
2023-04-04 12:57 ` [virtio-comment] " Stefan Hajnoczi
2023-04-04 12:57 ` [virtio-dev] " Stefan Hajnoczi
2023-04-06 4:27 ` [virtio-comment] " Parav Pandit
2023-04-06 4:27 ` [virtio-dev] " Parav Pandit
2023-04-24 16:13 ` [virtio-comment] " Michael S. Tsirkin
2023-04-24 16:13 ` [virtio-dev] " Michael S. Tsirkin
2023-04-06 7:20 ` [virtio-comment] Re: [virtio-dev] " Zhu Lingshan
2023-04-06 7:20 ` Zhu Lingshan
2023-04-06 14:05 ` [virtio-comment] " Parav Pandit
2023-04-06 14:05 ` Parav Pandit
2023-04-07 2:01 ` [virtio-comment] " Zhu, Lingshan
2023-04-07 2:01 ` Zhu, Lingshan
2023-04-07 7:34 ` [virtio-comment] " Michael S. Tsirkin
2023-04-07 7:34 ` Michael S. Tsirkin
2023-04-03 15:03 ` [virtio-comment] [PATCH v11 09/10] admin: conformance clauses Michael S. Tsirkin
2023-04-03 15:03 ` [virtio-dev] " Michael S. Tsirkin
2023-04-04 13:03 ` [virtio-comment] " Stefan Hajnoczi
2023-04-04 13:03 ` [virtio-dev] " Stefan Hajnoczi
2023-04-06 7:30 ` [virtio-comment] Re: [virtio] " Zhu, Lingshan
2023-04-06 7:30 ` [virtio-dev] " Zhu, Lingshan
2023-04-24 16:17 ` [virtio-comment] " Michael S. Tsirkin
2023-04-24 16:17 ` [virtio-dev] " Michael S. Tsirkin
2023-04-03 15:04 ` [virtio-comment] [PATCH v11 10/10] ccw: document more reserved features Michael S. Tsirkin
2023-04-03 15:04 ` [virtio-dev] " Michael S. Tsirkin
2023-04-06 7:31 ` [virtio-comment] " Zhu Lingshan
2023-04-06 7:31 ` [virtio-dev] " Zhu Lingshan
2023-04-03 15:59 ` [virtio-comment] Re: [PATCH v11 00/10] Introduce device group and device management Parav Pandit
2023-04-03 15:59 ` [virtio-dev] " Parav Pandit
2023-04-03 16:39 ` [virtio-comment] " Cornelia Huck
2023-04-03 16:39 ` [virtio-dev] " Cornelia Huck
2023-04-03 17:31 ` [virtio-comment] " Michael S. Tsirkin
2023-04-03 17:31 ` [virtio-dev] " Michael S. Tsirkin
2023-04-04 8:10 ` [virtio-comment] " Cornelia Huck
2023-04-04 8:10 ` [virtio-dev] " Cornelia Huck
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=20230410092104-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=jiri@nvidia.com \
--cc=lingshan.zhu@intel.com \
--cc=mgurtovoy@nvidia.com \
--cc=nrupal.jani@intel.com \
--cc=parav@nvidia.com \
--cc=pasic@linux.ibm.com \
--cc=sgarzare@redhat.com \
--cc=shahafs@nvidia.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@lists.oasis-open.org \
--cc=virtio@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.