On Tue, Apr 18, 2023 at 4:29 AM Parav Pandit <pa...@nvidia.com> wrote: > > > > From: Michael S. Tsirkin <m...@redhat.com> > > Sent: Monday, April 17, 2023 4:27 PM > > On Mon, Apr 17, 2023 at 05:23:30PM +0000, Parav Pandit wrote: > > > > Things might be simplified if we use separate queues for admin, > > > > transport and legacy. > > > > > > > Do you mean say we have three AQs, AQ_1, AQ_2, and AQ_3; > > > AQ_1 of the PF used by admin work as SIOV device create, SRIOV MSIX > > configuration. > > > AQ_2 of the PF used for transporting legacy config access of the PCI > > > VF > > > AQ_3 of the PF for some transport work. > > > > > > If yes, sounds find to me. > > > > Latest proposal simply leaves the split between AQs up to the driver. > > Seems the most flexible. > Yes. It is. Different opcode range and multiple AQs enable to do so.
Right, so it would be some facility that makes the transport commands of modern and legacy are mutually exclusive. Thanks > > 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-subscr...@lists.oasis-open.org > Unsubscribe: virtio-comment-unsubscr...@lists.oasis-open.org > List help: virtio-comment-h...@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/ > --------------------------------------------------------------------- To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
