Discussion of the VIRTIO specification
 help / color / mirror / Atom feed
From: "Zhu, Lingshan" <lingshan.zhu@intel.com>
To: Xuan Zhuo <xuanzhuo@linux.alibaba.com>
Cc: virtio-comment@lists.oasis-open.org,
	"Michael S. Tsirkin" <mst@redhat.com>
Subject: Re: [virtio-comment] About the plan of Admin Queue
Date: Fri, 30 Jun 2023 14:19:47 +0800	[thread overview]
Message-ID: <b95673d9-21e5-0fea-abdf-c0f8389e5cee@intel.com> (raw)
In-Reply-To: <1688104464.531018-1-xuanzhuo@linux.alibaba.com>



On 6/30/2023 1:54 PM, Xuan Zhuo wrote:
> On Tue, 20 Jun 2023 16:11:12 +0800, "Zhu, Lingshan" <lingshan.zhu@intel.com> wrote:
>>
>> On 6/20/2023 2:44 PM, Xuan Zhuo wrote:
>>> Hi,
>>>
>>> hi, I would want to know some plans and progress about admin queue.
>>>
>>> At the current spec, it seems that there is only one framework and no
>>> specific commands. I'd like to know if anyone is currently working on this and
>>> what the plans are.
>>>
>>> We also faced some similar issues, and we think admin queue is a good way to
>>> manage sr-iov.
>>>
>>>
>>> Thanks.
>> I plan to rebase original transport vq on admin vq.
>>
>> https://lists.oasis-open.org/archives/virtio-comment/202208/msg00140.html
>
> I review the patch, that is for S-IOV, right?
Yes, for SIOV and other similar devices
>
> I think it is good.
>
> I would if all is configured by the transport vq/admin vq from the OS?
For SIOV ADIs, this transport vq is the transport layer, so they are 
configured by the OS through transport vq.
>
> Can we create a managed dev from the backend?
>
> Such as, the DPU sends a command to the driver, then the driver creates a new
> managed dev.
I think the group owner, usually the PCI PF is the management device.

Thanks
>
> Thanks.
>
>
>> Thanks,
>> Zhu Lingshan
>>>
>>>
>>>
>>> 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/
>>>
>>
>> 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/
>>
> 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/
>


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/


  reply	other threads:[~2023-06-30  6:20 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-06-20  6:44 [virtio-comment] About the plan of Admin Queue Xuan Zhuo
2023-06-20  8:11 ` Zhu, Lingshan
2023-06-30  5:54   ` Xuan Zhuo
2023-06-30  6:19     ` Zhu, Lingshan [this message]
2023-06-30  7:46       ` Xuan Zhuo
2023-06-30  7:54         ` Zhu, Lingshan
2023-06-30  7:56           ` Xuan Zhuo
2023-06-30  8:32             ` Zhu, Lingshan
2023-06-30  9:07               ` Zhu, Lingshan
2023-06-30  9:14               ` Xuan Zhuo
2023-06-30 10:33                 ` Zhu, Lingshan
2023-06-30 11:35                   ` Parav Pandit
2023-07-03  4:29                     ` Zhu, Lingshan
2023-07-03  5:54                       ` Xuan Zhuo
2023-07-03  8:01                         ` Zhu, Lingshan
2023-07-03  8:21                           ` Xuan Zhuo
2023-07-03  8:23                             ` Zhu, Lingshan
2023-07-27  2:30                       ` Xuan Zhuo
2023-07-27  3:56                         ` Zhu, Lingshan
2023-07-27  6:09                           ` Xuan Zhuo
2023-07-27  6:17                             ` Zhu, Lingshan
2023-07-27  6:20                               ` Xuan Zhuo
2023-07-27  8:03                                 ` Jason Wang
2023-07-27  8:07                                   ` Xuan Zhuo
2023-07-27  8:28                                     ` Jason Wang
2023-07-27  8:30                                       ` Xuan Zhuo
2023-07-27  8:56                                         ` Jason Wang
2023-07-27  9:01                                           ` Xuan Zhuo
     [not found]                                       ` <aafe1885-0ec2-66ca-4511-f2606bc881ee@gmail.com>
2023-08-02  6:13                                         ` Xuan Zhuo
2023-08-02  6:15                                         ` Jason Wang
2023-08-02  6:34                                           ` Xuan Zhuo
2023-08-02  6:53                                             ` Jason Wang
2023-08-02  6:55                                               ` Xuan Zhuo
2023-07-28  6:09                                   ` Xuan Zhuo
2023-07-31  1:20                                     ` Jason Wang
2023-07-31  2:02                                       ` Parav Pandit
2023-07-03  8:10     ` Jason Wang
2023-07-03  8:20       ` Xuan Zhuo
2023-07-03 13:05         ` Michael S. Tsirkin
2023-07-03 13:06           ` Parav Pandit
2023-07-03 20:38           ` Parav Pandit
2023-07-04  3:48             ` Zhu, Lingshan
2023-07-04 12:11           ` Xuan Zhuo
2023-07-04 12:14           ` Xuan Zhuo
2023-07-04 13:15             ` Parav Pandit
2023-07-05  4:30               ` Xuan Zhuo
2023-07-05  4:35                 ` Parav Pandit
2023-07-05  4:36                   ` Xuan Zhuo
2023-07-05  4:38               ` Xuan Zhuo

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=b95673d9-21e5-0fea-abdf-c0f8389e5cee@intel.com \
    --to=lingshan.zhu@intel.com \
    --cc=mst@redhat.com \
    --cc=virtio-comment@lists.oasis-open.org \
    --cc=xuanzhuo@linux.alibaba.com \
    /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