Re: [PATCH RFC net-next 00/10] MC Flood disable and snooping

[Joseph Huang]

Hi Andrew,

On 4/4/2024 6:11 PM, Andrew Lunn wrote:
> On Thu, Apr 04, 2024 at 05:35:41PM -0400, Joseph Huang wrote:
> > Hi Andrew,
> >
> > On 4/2/2024 8:43 AM, Andrew Lunn wrote:
> > > On Mon, Apr 01, 2024 at 08:10:59PM -0400, Joseph Huang wrote:
> > > > There is a use case where one would like to enable multicast snooping
> > > > on a bridge but disable multicast flooding on all bridge ports so that
> > > > registered multicast traffic will only reach the intended recipients and
> > > > unregistered multicast traffic will be dropped. However, with existing
> > > > bridge ports' mcast_flood flag implementation, it doesn't work as desired.
> > > >
> > > > This patchset aims to make multicast snooping work even when multicast
> > > > flooding is disabled on the bridge ports, without changing the semantic of
> > > > the mcast_flood flag too much. Patches 1 to 4 attempt to address this issue.
> > > >
> > > > Also, in a network where more than one multicast snooping capable bridges
> > > > are interconnected without multicast routers being present, multicast
> > > > snooping fails if:
> > > >
> > > >    1. The source is not directly attached to the Querier
> > > >    2. The listener is beyond the mrouter port of the bridge where the
> > > >       source is directly attached
> > > >    3. A hardware offloading switch is involved
> > >
> > > I've not studied the details here, but that last point makes me think
> > > the offload driver is broken. There should not be any difference
> > > between software bridging and hardware bridging. The whole idea is
> > > that you take what Linux can do in software and accelerate it by
> > > offloading to hardware. Doing acceleration should not change the
> > > behaviour.
> >
> > In patch 10 I gave a little more detail about the fix, but basically this is
> > what happened.
> >
> > Assuming we have a soft bridge like the following:
> >
> >              bp1 +------------+
> >    Querier <---- |   bridge   |
> >                  +------------+
> >                 bp2 |      | bp3
> >                     |      |
> >                     v      v
> >              MC Source    MC Listener
> >
> > Here bp1 is the mrouter port, bp2 is connected to the multicast source, and
> > bp3 is connected to the multicast listener who wishes to receive multicast
> > traffic for that group.
> >
> > After some Query/Report exchange, the snooping code in the bridge is going
> > to learn about the Listener from bp3, and is going to create an MDB group
> > which includes bp3 as the sole member. When the bridge receives a multicast
> > packet for that group from bp2, the bridge will do a look up to find the
> > members of that group (in this case, bp3) and forward the packet to every
> > single member in that group. At the same time, the bridge will also forward
> > the packet to every mrouter port so that listeners beyond mrouter ports can
> > receive that multicast packet as well.
> >
> > Now consider the same scenario, but with a hardware-offloaded switch:
> >
> >                  +------------+
> >                  |   bridge   |
> >                  +------------+
> >                        ^
> >                        |
> >                        | p6 (Host CPU port)
> >           p1/bp1 +------------+
> >    Querier <---- |     sw     |
> >                  +------------+
> >              p2/bp2 |      | p3/bp3
> >                     |      |
> >                     v      v
> >              MC Source    MC Listener
> >
> > Same Query/Report exchange, same MDB group, except that this time around the
> > MDB group will be offloaded to the switch as well. So in the switch's ATU we
> > will now have an entry for the multicast group and with p3 being the only
> > member of that ATU. When the multicast packet arrives at the switch from p2,
> > the switch will do an ATU lookup, and forward the packet to p3 only. This
> > means that the Host CPU (p6) will not get a copy of the packet, and so the
> > soft bridge will not have the opportunity to forward that packet to the
> > mrouter port. This is what patch 10 attempts to address.
> >
> > One possible solution of course is to add p6 to every MDB group, however
> > that's probably not very desirable. Besides, it will be more efficient if
> > the packet is forwarded to the mrouter port by the switch in hardware (i.e.,
> > offload mrouter forwarding), vs. being forwarded in the bridge by software.
>
> Thanks for the explanation. So i think the key part which you said
> above is:
>
>    At the same time, the bridge will also forward the packet to every
>    mrouter port so that listeners beyond mrouter ports can receive that
>    multicast packet as well.
>
> How does the bridge know about the mrouter port? It seems like the

The bridge learns about the existence of the Querier by the reception of 
Queries. The bridge will mark the port which it received Queries from as 
the mrouter port.

> bridge needs to pass that information down to the switch. Is the

The bridge does pass that information down to switchdev. Patch 5 adds 
DSA handling of that event as well. Patches 9 and 10 adds the support in 
the mv88e6xxx driver.

> mrouter itself performing a join on the group when it has members of
> the group on the other side of it?

You hit a key point here. The Querier does not send Report (not with 
IGMPv2 anyway), so the bridge will never add the mrouter port to any MDB 
group. That's why patch 10 is needed. Prestera driver does something 
similar (which is what patches 6,7, and 10 are modeled after).

> 	Andrew