From: "Michael S. Tsirkin" <mst@redhat.com>
To: Cornelia Huck <cohuck@redhat.com>
Cc: virtio-comment@lists.oasis-open.org,
virtio-dev@lists.oasis-open.org, jasowang@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,
Zhu Lingshan <lingshan.zhu@intel.com>,
pasic@linux.ibm.com, Shahaf Shuler <shahafs@nvidia.com>,
Parav Pandit <parav@nvidia.com>,
Max Gurtovoy <mgurtovoy@nvidia.com>
Subject: Re: [PATCH v8 4/9] admin: introduce virtio admin virtqueues
Date: Wed, 23 Nov 2022 04:32:08 -0500 [thread overview]
Message-ID: <20221123043058-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <87mt8inhla.fsf@redhat.com>
On Wed, Nov 23, 2022 at 10:30:25AM +0100, Cornelia Huck wrote:
> On Tue, Nov 22 2022, "Michael S. Tsirkin" <mst@redhat.com> wrote:
>
> > On Tue, Nov 22, 2022 at 02:14:23PM +0100, Cornelia Huck wrote:
> >> On Sun, Nov 20 2022, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> >> > +Administration virtqueues exists for a certain owner device if
> >> > +VIRTIO_F_ADMIN_VQ feature has been negotiated. The index of the
> >> > +first administration virtqueue and their number is exposed by the
> >> > +owner device in a transport specific manner.
> >>
> >> (Do we always expect admin virtqueues to use a range of indices, i.e. no
> >> holes? That seems a bit limiting.)
> >
> > For the device?
> > I frankly feel it's enough, yea.
>
> About how many admin virtqueues per device are we thinking for current
> use cases, anyway? If it's usually just one or two, the range would not
> really be limiting.
I think it's one or two for now, yes. E.g. we could use
one for SRIOV and one for the (TBD) SIOV.
> >
> >> What about
> >>
> >> "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 is exposed by the owner device in a transport
> >> specific manner."
> >
> >
> >
> >
> >> > +
> >> > +The driver submits commands by queueing them to an arbitrary
> >> > +administration virtqueue, and they are processed by the
> >> > +device in the order in which they are queued. It is the
> >> > +responsibility of the driver to ensure ordering for commands
> >> > +placed on different administration virtqueues, because they will
> >> > +be executed with no order constraints.
> >>
> >> Are all admin vqs supposed to be equal? Could a device expose e.g. a
> >> high prio admin vq and a normal prio admin vq?
> >
> >
> > ATM yes, for priority we'll need a separate capability. Work on top?
>
> Ok, if we don't need it now, we can add it later.
next prev parent reply other threads:[~2022-11-23 9:32 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-21 1:25 [PATCH v8 0/9] Introduce device group and device management Michael S. Tsirkin
2022-11-21 1:25 ` [PATCH v8 1/9] virtio: document forward compatibility guarantees Michael S. Tsirkin
2022-11-21 15:24 ` [virtio] " Cornelia Huck
2022-11-22 20:26 ` Michael S. Tsirkin
2022-11-23 9:21 ` [virtio-dev] " Cornelia Huck
2022-11-23 9:28 ` Michael S. Tsirkin
2022-11-21 1:25 ` [PATCH v8 2/9] admin: introduce device group and related concepts Michael S. Tsirkin
2022-11-22 12:11 ` [virtio] " Cornelia Huck
2022-11-22 20:17 ` Michael S. Tsirkin
2022-11-23 9:26 ` [virtio-comment] " Cornelia Huck
2022-11-21 1:25 ` [PATCH v8 3/9] admin: introduce group administration commands Michael S. Tsirkin
2022-11-22 12:43 ` [virtio-dev] " Cornelia Huck
2022-11-21 1:25 ` [PATCH v8 4/9] admin: introduce virtio admin virtqueues Michael S. Tsirkin
2022-11-22 13:14 ` [virtio-comment] " Cornelia Huck
2022-11-22 19:31 ` Michael S. Tsirkin
2022-11-23 9:30 ` [virtio-dev] " Cornelia Huck
2022-11-23 9:32 ` Michael S. Tsirkin [this message]
2022-11-23 9:54 ` Cornelia Huck
2022-11-21 1:25 ` [PATCH v8 5/9] pci: add admin vq registers to virtio over pci Michael S. Tsirkin
2022-11-22 14:46 ` [virtio-dev] " Cornelia Huck
2022-11-22 19:23 ` Michael S. Tsirkin
2022-11-23 9:36 ` [virtio-comment] " Cornelia Huck
2022-11-23 9:38 ` Michael S. Tsirkin
2022-11-21 1:25 ` [PATCH v8 6/9] mmio: document ADMIN_VQ as reserved Michael S. Tsirkin
2022-11-21 1:25 ` [PATCH v8 7/9] ccw: " Michael S. Tsirkin
2022-11-21 15:53 ` [virtio] " Cornelia Huck
2022-11-21 16:48 ` Michael S. Tsirkin
2022-11-21 17:09 ` Michael S. Tsirkin
2022-11-22 8:50 ` [virtio-dev] " Cornelia Huck
2022-11-22 9:51 ` Michael S. Tsirkin
2022-11-21 1:25 ` [PATCH v8 8/9] admin: command list discovery Michael S. Tsirkin
2022-11-21 11:06 ` Uminski, Piotr
2022-12-15 9:09 ` [virtio-comment] " Michael S. Tsirkin
2022-12-15 9:52 ` Uminski, Piotr
2022-12-24 18:17 ` Michael S. Tsirkin
2022-11-22 15:25 ` [virtio] " Cornelia Huck
2022-11-22 19:17 ` Michael S. Tsirkin
2022-11-23 9:51 ` [virtio] " Cornelia Huck
2022-11-23 10:00 ` Michael S. Tsirkin
2022-11-23 10:09 ` [virtio] " Cornelia Huck
2022-11-23 10:16 ` Michael S. Tsirkin
2022-11-23 10:33 ` [virtio] " Cornelia Huck
2022-11-23 11:21 ` Michael S. Tsirkin
2022-11-21 1:25 ` [PATCH v8 9/9] admin: conformance clauses Michael S. Tsirkin
2022-11-22 16:06 ` [virtio] " Cornelia Huck
2022-11-22 19:20 ` Michael S. Tsirkin
2022-11-23 9:52 ` [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=20221123043058-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=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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox