On Tue, Jul 25, 2017 at 7:45 AM, Jakub Kicinski <kubak...@wp.pl> wrote:
> This is even worse. We already have two naming conventions in the > kernel, mlx5 uses "%d" for legacy reasons. nfp uses pf%dvf%d for vfs, To make it clear, in mlx5 this is used only for the offloads/switchdev mode and not for legacy mode, in the latter mode, a VF probed to VM doesn't have host side representation so there's no where to use that. Or. > which is better for two reasons: (a) it works with multi-PF devices; > (b) naming something representor from switchdev perspective is > pointless, you're not calling the external port netdev a physical port > representor, even though it has the exact same relation to the port as > with VFs (i.e. egressing traffic on the netdev will cause the switch > to send to the given port).
