On Mon, Dec 13, 2021 at 04:28:24PM +0100, Horatiu Vultur wrote: > The 12/13/2021 14:29, Vladimir Oltean wrote: > > > > On Mon, Dec 13, 2021 at 03:26:56PM +0100, Horatiu Vultur wrote: > > > > They are independent of each other. You deduce the interface on which > > > > the notifier was emitted using switchdev_notifier_info_to_dev() and act > > > > upon it, if lan966x_netdevice_check() is true. The notifier handling > > > > code itself is stateless, all the state is per port / per switch. > > > > If you register one notifier handler per switch, lan966x_netdevice_check() > > > > would return true for each notifier handler instance, and you would > > > > handle each event twice, would you not? > > > > > > That is correct, I will get the event twice which is a problem in the > > > lan966x. The function lan966x_netdevice_check should be per instance, in > > > this way each instance can filter the events. > > > The reason why I am putting the notifier_block inside lan966x is to be > > > able to get to the instance of lan966x even if I get a event that is not > > > for lan966x port. > > > > That isn't a problem, every netdevice notifier still sees all events. > > Yes, that is correct. > Sorry maybe I am still confused, but some things are still not right. > > So lets say there are two lan966x instances(A and B) and each one has 2 > ports(ethA0, ethA1, ethB0, ethB1). > So with the current behaviour, if for example ethA0 is added in vlan > 100, then we get two callbacks for each lan966x instance(A and B) because > each of them registered. And because of lan966x_netdevice_check() is true > for ethA0 will do twice the work. > And you propose to have a singleton notifier so we get only 1 callback > and will be fine for this case. But if you add for example the bridge in > vlan 200 then I will never be able to get to the lan966x instance which > is needed in this case. I'm not sure what you mean by "you add the bridge in vlan 200" with respect to netdevice notifiers. Create an 8021q upper with VID 200 on top of a bridge (as that would generate a NETDEV_CHANGEUPPER)? If there's a netdevice event on a bridge, the singleton netdevice event handler can see if it is a bridge (netif_is_bridge_master), and if it is, it can crawl through the bridge's lower interfaces using netdev_for_each_lower_dev to see if there is any lan966x interface beneath it. If there isn't, nothing to do. Otherwise, you get the opportunity to do something for each port under that bridge. Maybe I'm not understanding what you're trying to accomplish that's different? > That is why if the lan966x_netdevice_check would be per instance, then > we can filter like before, we still get call twice but then we filter for > each instance. We get the lan966x instance from notifier_block and then > we can check if the port netdev_ops is the same as the lan966x > netdev_ops. > > And in the other case we will still be able to get to the lan966x instance > in case the bridge is added in a vlan. > > > DSA intercepts a lot of events which aren't directly emitted for its own > > interfaces. You don't gain much by having one more, if anything. > > > > > > notifier handlers should be registered as singletons, like other drivers > > > > do. > > > > > > It looks like not all the other driver register them as singletone. For > > > example: prestera, mlx5, sparx5. (I just have done a git grep for > > > register_switchdev_notifier, I have not looked in details at the > > > implementation). > > > > Not all driver writers may have realized that it is an issue that needs > > to be thought of. > > -- > /Horatiu
