From: Petr Machata <petrm@xxxxxxxxxxxx> Date: Thu, 22 Nov 2018 23:27:52 +0000 > An offloading driver may need to have access to switchdev events on > ports that aren't directly under its control. An example is a VXLAN port > attached to a bridge offloaded by a driver. The driver needs to know > about VLANs configured on the VXLAN device. However the VXLAN device > isn't stashed between the bridge and a front-panel-port device (such as > is the case e.g. for LAG devices), so the usual switchdev ops don't > reach the driver. > > VXLAN is likely not the only device type like this: in theory any L2 > tunnel device that needs offloading will prompt requirement of this > sort. > > A way to fix this is to give up the notion of port object addition / > deletion as a switchdev operation, which assumes somewhat tight coupling > between the message producer and consumer. And instead send the message > over a notifier chain. ... Series applied, thank you. _______________________________________________ devel mailing list devel@xxxxxxxxxxxxxxxxxxxxxx http://driverdev.linuxdriverproject.org/mailman/listinfo/driverdev-devel
