> From: Jakub Kicinski <kuba@xxxxxxxxxx> > Sent: Friday, November 20, 2020 7:05 AM > > On Wed, 18 Nov 2020 22:12:22 -0800 Saeed Mahameed wrote: > > > Right, devices of other subsystems are fine, I don't care. > > > > But a netdev will be loaded on SF automatically just through the > > current driver design and modularity, since SF == VF and our netdev is > > abstract and doesn't know if it runs on a PF/VF/SF .. we literally > > have to add code to not load a netdev on a SF. why ? :/ > > A netdev is fine, but the examples so far don't make it clear (to me) if it's > expected/supported to spawn _multiple_ netdevs from a single "vdpa > parentdev". We do not create Netdev from vdpa parentdev. >From vdpa parentdev, only vdpa device(s) are created which is 'struct device' residing in /sys/bus/vdpa/<device>. Currently such vdpa device is already created on mlx5_vpa.ko driver load, however user has no way to inspect, stats, get/set features of this device, hence the vdpa tool.
