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


On Mon, 3 Jul 2023 09:05:09 -0400, "Michael S. Tsirkin" <mst@redhat.com> wrote:
> 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?

I have been thinking about this question for a long time, and there maybe is a
gap of understanding here.

In our scenario, we should have two roles, one is the user and the other is the
vendor's management software. Do you think that the management
software is running on the host, and it manages the DPU?

But in the scenario I mentioned, the vendor's management software runs on
the DPU, and all hosts belong to the user.

The problem we want to solve is that this user may want 1000 network cards. So
it must use VFs as a network cards. It cannot and will not configure detailed
NIC properties based on the admin queue.

I don't know if I found the key to the problem.

Thanks.



> Why is not the ID an internal property of the management?
>
> --
> MST
>


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