Re: [virtio-comment] About the plan of Admin Queue

["Zhu, Lingshan" <lingshan.zhu@intel.com>]

On 7/4/2023 4:38 AM, Parav Pandit wrote:
>
>> From: Michael S. Tsirkin <mst@redhat.com>
>> Sent: Monday, July 3, 2023 9:05 AM
>>
>> OK it looks like at least Parav and Jason understand what's going on, maybe one
>> of you can explain:
>>
>> 1- there's a management stack that can bind an ID
>>    to a group of properties
>> 2- the proposed command then binds an ID to a VF
>> 3- after this, VF can be assigned to a VM
>>
>> Is this a fair summary?
>>
>> In that case what is gained compared to
>> configuring properties on the VF directly?
>> Why is not the ID an internal property of the management?
> For VFs I also believe we can live with an internal property.
>
> For migratable SIOV devices which are spawned by the management system has similar ID assigned by the mgmt. system.
> Having such node local ID is needed anyway.
>
> There is a struggle (scale wise) to make such ID network wide unique if each virtio device to expose such id at transport level.
Maybe you don't want a guest talking to the PF through admin queue 
directly, so there can be a wrapper for SIOV ADIs, therefore the ID is 
not a problem for migration.


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/