Re: [PATCH RFC WIP 0/5] IGMP snooping for local traffic
From: Nikolay Aleksandrov <hidden>
Date: 2017-08-26 22:40:41
Also in:
bridge
On 27.08.2017 01:17, Nikolay Aleksandrov wrote:
On 26/08/17 23:56, Andrew Lunn wrote:quoted
This is a WIP patchset i would like comments on from bridge, switchdev and hardware offload people. The linux bridge supports IGMP snooping. It will listen to IGMP reports on bridge ports and keep track of which groups have been joined on an interface. It will then forward multicast based on this group membership. When the bridge adds or removed groups from an interface, it uses switchdev to request the hardware add an mdb to a port, so the hardware can perform the selective forwarding between ports. What is not covered by the current bridge code, is IGMP joins/leaves from the host on the brX interface. No such monitoring isHi Andrew, Have you taken a look at mglist (the boolean, probably needs a rename) ? It is for exactly that purpose, to track which groups the bridge is interested in. I assume I'm forgetting or missing something here.quoted
performed. With a pure software bridge, it is not required. All mulitcast frames are passed to the brX interface, and the networkIf mglist (again the boolean) is false then they won't be passed up.quoted
stack filters them, as it does for any interface. However, when hardware offload is involved, things change. We should program the hardware to only send multcast packets to the host when the host has in interest in them.Granted the boolean mglist might need some changes (esp. with host group leave) but I think it can be used to program switchdev for host join/leave, can't we adjust its behaviour instead of introducing this complexity and avoid many headaches ?quoted
Thus we need to perform IGMP snooping on the brX interface, just like any other interface of the bridge. However, currently the brX interface is missing all the needed data structures to do this. There is no net_bridge_port structure for the brX interface. This strucuture is created when an interface is added to the bridge. But the brX interface is not a member of the bridge. So this patchset makes the brX interface a first class member of the bridge. When the brX interface is opened, the interface is added to the bridge. A net_bridge_port is allocated for it, and IGMP snooping is performed as usual.I have actually discussed this idea long time ago with Vlad and it has very nice upsides (most important one removing br/port checks everywhere) but it blows up fast with special cases for the bridge and things look very similar. You'll need to rework the whole bridge and turn every bridge special case into either a port generic one or again bridge-specific special case but with a check for the new flag. I will not point out every bug that comes out of this, but registering the bridge rx handler to itself is simply wrong on many levels and breaks many setups.
This was a digression about making the bridge a proper port of itself (e.g. port 0, linked and all), it is only tangential to this implementation as it doesn't link the new port.
quoted
There are some complexities here. Some assumptions are broken, like the master interface of a port interface is the bridge interface. The brX interface cannot be its own master. The use of netdev_master_upper_dev_get() within the bridge code has been changed to reflecit this. The bridge receive handler needs to not process frames for the brX interface, etc. The interface downward to the hardware is also an issue. The code presented here is a hack and needs to change. But that is secondary and can be solved once it is agreed how the bridge needs to change to support this use case.Definitely agree with this statement. :-)quoted
Comment welcome and wanted. Andrew Andrew Lunn (5): net: rtnetlink: Handle bridge port without upper device net: bridge: Skip receive handler on brX interface net: bridge: Make the brX interface a member of the bridge net: dsa: HACK: Handle MDB add/remove for none-switch ports net: dsa: Don't include CPU port when adding MDB to a port include/linux/if_bridge.h | 1 + net/bridge/br_device.c | 12 ++++++++++-- net/bridge/br_if.c | 37 ++++++++++++++++++++++++------------- net/bridge/br_input.c | 4 ++++ net/bridge/br_mdb.c | 2 -- net/bridge/br_multicast.c | 7 ++++--- net/bridge/br_private.h | 1 + net/core/rtnetlink.c | 23 +++++++++++++++++++++-- net/dsa/port.c | 19 +++++++++++++++++-- net/dsa/switch.c | 2 +- 10 files changed, 83 insertions(+), 25 deletions(-)