> Hi 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. > > > performed. With a pure software bridge, it is not required. All > > mulitcast frames are passed to the brX interface, and the network > > If mglist (again the boolean) is false then they won't be passed up. > > > 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 ? I would like to avoid this complexity as well. I will take a look at mglist. Thanks for the hint. Andrew
