OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio-comment message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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



> 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.


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]