> From: Jiri Pirko <j...@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.
>
> >
> >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.
---------------------------------------------------------------------
To unsubscribe, e-mail: virtio-dev-unsubscr...@lists.oasis-open.org
For additional commands, e-mail: virtio-dev-h...@lists.oasis-open.org
