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

 


Help: OASIS Mailing Lists Help | MarkMail Help

virtio message

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


Subject: Re: [virtio-comment] Re: [virtio] [PATCH v10 04/10] admin: introduce virtio admin virtqueues


Thu, Mar 09, 2023 at 01:36:00PM CET, parav@nvidia.com wrote:
>
>
>> From: Jiri Pirko <jiri@nvidia.com>
>> Sent: Thursday, March 9, 2023 2:37 AM
>
>
>> >We want the ability to program/provision the virtio feature bits and virtio
>> config space parameters of the VF through PF.
>> >These are host-facing parameters that usually migrate from one to another
>> host when a VF migrates.
>> 
>> Here is where we lack to have separate "devlink function" entity, independend
>> of "devlink port" :/ I mean, for MAC config and irq vectors.
>> What other host facing parmeters you have in mind. VLAN of "ip vf" is
>> definitelly one of them, I have to emphasize.
>> 
>It is not.
>
>Virtio feature bits defined by the virtio spec.
>Virtio config space fields present in the each virtio device specific spec.

If those are only virtio-specifig things, I'm good.

Mac is part of Virtio_net config space. Good.



>
>> 
>> >
>
>> >virtio net doesn't implement it either and I don't see any user asking for it
>> either.
>> >All users have migrated to using tc mechanism for long time now.
>> 
>> Okay, so the bottom line is, we should take care of host facing config of VF, but
>> we should not care about network plug of VF - that stays out of the scope.
>Right.

Good.


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