From: "Michael S. Tsirkin" <mst@redhat.com>
To: Max Gurtovoy <mgurtovoy@nvidia.com>
Cc: virtio-comment@lists.oasis-open.org, cohuck@redhat.com,
virtio-dev@lists.oasis-open.org, jasowang@redhat.com,
parav@nvidia.com, shahafs@nvidia.com, oren@nvidia.com,
stefanha@redhat.com
Subject: Re: [PATCH v2 1/4] Add virtio Admin Virtqueue
Date: Wed, 26 Jan 2022 09:40:37 -0500 [thread overview]
Message-ID: <20220126093659-mutt-send-email-mst@kernel.org> (raw)
In-Reply-To: <20220124093918.34371-2-mgurtovoy@nvidia.com>
On Mon, Jan 24, 2022 at 11:39:15AM +0200, Max Gurtovoy wrote:
> +Regardless of device offering VIRTIO_F_IN_ORDER, admin queue command buffers
> +are used by the device in out of order manner.
Instead of special-casing AQ I'd like to see a generic capability
addressing this need. For example, TX for virtio net might benefit from
this too. And I'd like to mention, again, VIRTIO_F_PARTIAL_ORDER
proposal as one, arguably cleaner and more generic way to address this.
And if that's not adequate I'd like to address that as part of the
PARTIAL_ORDER proposal, this kind of per-queue in order was definitely
on the radar as it was formulated.
--
MST
next prev parent reply other threads:[~2022-01-26 14:40 UTC|newest]
Thread overview: 61+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 9:39 [PATCH v2 0/4] VIRTIO: Provision maximum MSI-X vectors for a VF Max Gurtovoy
2022-01-24 9:39 ` [PATCH v2 1/4] Add virtio Admin Virtqueue Max Gurtovoy
2022-01-26 14:40 ` Michael S. Tsirkin [this message]
2022-01-26 14:54 ` [virtio-comment] " Max Gurtovoy
2022-01-26 15:03 ` Michael S. Tsirkin
2022-01-26 15:16 ` [virtio-comment] " Max Gurtovoy
2022-01-27 3:56 ` Parav Pandit
2022-01-27 3:55 ` Parav Pandit
2022-01-27 3:56 ` Jason Wang
2022-01-28 12:14 ` [virtio-comment] " Cornelia Huck
2022-01-28 12:47 ` Michael S. Tsirkin
2022-01-28 15:49 ` [virtio-comment] " Cornelia Huck
2022-01-28 15:52 ` Michael S. Tsirkin
2022-01-28 16:14 ` [virtio-dev] " Cornelia Huck
2022-01-28 16:16 ` Michael S. Tsirkin
2022-01-28 16:23 ` [virtio-dev] " Cornelia Huck
2022-01-29 3:53 ` Jason Wang
2022-01-30 9:13 ` Max Gurtovoy
2022-01-30 9:40 ` Michael S. Tsirkin
2022-01-30 9:56 ` Max Gurtovoy
2022-01-30 14:41 ` Michael S. Tsirkin
2022-01-30 15:12 ` Max Gurtovoy
2022-01-30 15:30 ` Michael S. Tsirkin
2022-01-30 18:23 ` [virtio-comment] " Max Gurtovoy
2022-01-30 21:15 ` Michael S. Tsirkin
2022-01-31 9:16 ` [virtio-dev] " Cornelia Huck
2022-01-31 13:40 ` Michael S. Tsirkin
2022-01-31 14:26 ` [virtio-comment] " Cornelia Huck
2022-01-31 14:52 ` Michael S. Tsirkin
2022-01-31 15:48 ` [virtio-dev] " Cornelia Huck
2022-01-31 16:00 ` Michael S. Tsirkin
2022-01-31 16:12 ` Halil Pasic
2022-01-31 17:10 ` [virtio-dev] " Cornelia Huck
2022-01-31 17:22 ` Michael S. Tsirkin
2022-02-01 11:53 ` [virtio-dev] " Halil Pasic
2022-02-01 17:01 ` Cornelia Huck
2022-02-01 18:34 ` Michael S. Tsirkin
2022-01-31 15:47 ` Halil Pasic
2022-01-31 16:01 ` Michael S. Tsirkin
2022-01-31 16:12 ` Cornelia Huck
2022-02-09 2:27 ` Jason Wang
2022-02-09 7:46 ` Michael S. Tsirkin
2022-01-30 9:39 ` Michael S. Tsirkin
2022-01-30 11:21 ` [virtio-comment] " Max Gurtovoy
2022-01-30 14:37 ` Michael S. Tsirkin
2022-01-24 9:39 ` [virtio-comment] [PATCH v2 2/4] virtio-blk: add support for VIRTIO_F_ADMIN_VQ Max Gurtovoy
2022-01-24 9:39 ` [PATCH v2 3/4] virtio-net: " Max Gurtovoy
2022-01-24 9:39 ` [PATCH v2 4/4] Add support for MSI-X vectors configuration for PCI VFs Max Gurtovoy
2022-01-25 11:53 ` Michael S. Tsirkin
2022-01-26 13:03 ` Parav Pandit
2022-01-26 14:08 ` [virtio-comment] " Michael S. Tsirkin
2022-01-27 3:40 ` Parav Pandit
2022-01-27 12:39 ` Michael S. Tsirkin
2022-01-27 14:16 ` Parav Pandit
2022-01-27 17:28 ` Michael S. Tsirkin
2022-01-27 3:36 ` Jason Wang
2022-01-27 5:22 ` Parav Pandit
2022-01-28 3:23 ` [virtio-comment] " Jason Wang
2022-01-28 3:30 ` Parav Pandit
2022-01-28 3:35 ` Jason Wang
2022-01-28 3:45 ` Parav Pandit
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=20220126093659-mutt-send-email-mst@kernel.org \
--to=mst@redhat.com \
--cc=cohuck@redhat.com \
--cc=jasowang@redhat.com \
--cc=mgurtovoy@nvidia.com \
--cc=oren@nvidia.com \
--cc=parav@nvidia.com \
--cc=shahafs@nvidia.com \
--cc=stefanha@redhat.com \
--cc=virtio-comment@lists.oasis-open.org \
--cc=virtio-dev@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