Displaying 7 results from an estimated 7 matches for "br_multicast_flood".
2023 Mar 20
2
[Bridge] Multicast: handling of STA disconnect
...mediately? If not, can we do this to take quick action to reduce
> > overhead of memory and driver?
> >
> > I have an idea on this. Can we mark this port group (MDB entry) as
> > INACTIVE from the WiFi disconnect event and skip forwarding the stream
> > to this port in br_multicast_flood by applying the check? I can share
> > the patch on this.
> >
> > Thanks,
> > UjjaL Roy
>
> Hi,
> Fast leave and EHT (as that's v3's fast leave version) are about quickly converging when
> a leave is received (e.g. when there are no listeners to quickly r...
2023 Mar 20
1
[Bridge] Multicast: handling of STA disconnect
..._eht handling this scenario to take any action
immediately? If not, can we do this to take quick action to reduce
overhead of memory and driver?
I have an idea on this. Can we mark this port group (MDB entry) as
INACTIVE from the WiFi disconnect event and skip forwarding the stream
to this port in br_multicast_flood by applying the check? I can share
the patch on this.
Thanks,
UjjaL Roy
2023 Mar 20
1
[Bridge] Multicast: handling of STA disconnect
...take any action
> immediately? If not, can we do this to take quick action to reduce
> overhead of memory and driver?
>
> I have an idea on this. Can we mark this port group (MDB entry) as
> INACTIVE from the WiFi disconnect event and skip forwarding the stream
> to this port in br_multicast_flood by applying the check? I can share
> the patch on this.
>
> Thanks,
> UjjaL Roy
Hi,
Fast leave and EHT (as that's v3's fast leave version) are about quickly converging when
a leave is received (e.g. when there are no listeners to quickly remove the mdb). They
don't deal wi...
2018 Jan 10
1
soft lockup after set multicast_router of bridge and it's port to 2
...> /sys/devices/virtual/net/bond2/brport/multicast_router
Then soft lockup occured:
Message from syslogd at node-0 at Jan 9 15:47:12 ...
kernel:BUG: soft lockup - CPU#0 stuck for 61s! [swapper:0]
And the call trace is
RIP: 0010:[<ffffffffa04f3608>] [<ffffffffa04f3608>] br_multicast_flood+0x88/0x140 [bridge]
RSP: 0018:ffff88013bc038f0 EFLAGS: 00000246
RAX: ffff88404f816020 RBX: ffff88013bc03940 RCX: ffff88204e40a640
RDX: ffff882002b9ce01 RSI: ffff882002b9ce80 RDI: 0000000000000000
RBP: ffffffff8100bb93 R08: 0000000000000001 R09: 00000000ff09f4a1
R10: ffff88202c8...
2023 May 19
2
[Bridge] [PATCH net-next 1/5] skbuff: bridge: Add layer 2 miss indication
...*p;
+ BR_INPUT_SKB_CB(skb)->miss = 1;
+
list_for_each_entry_rcu(p, &br->port_list, list) {
/* Do not flood unicast traffic to ports that turn it off, nor
* other traffic if flood off, except for traffic we originate
@@ -295,6 +299,7 @@ void br_multicast_flood(struct net_bridge_mdb_entry *mdst,
allow_mode_include = false;
} else {
p = NULL;
+ BR_INPUT_SKB_CB(skb)->miss = 1;
}
while (p || rp) {
Then copy it to skb->l2_miss at the very end where the cache line
containing...
2023 May 09
5
[Bridge] [RFC PATCH net-next 0/5] Add layer 2 miss indication and filtering
tl;dr
=====
This patchset adds a single bit to the skb to indicate that a packet
encountered a layer 2 miss in the bridge and extends flower to match on
this metadata. This is required for non-DF (Designated Forwarder)
filtering in EVPN multi-homing which prevents decapsulated BUM packets
from being forwarded multiple times to the same multi-homed host.
Background
==========
In a typical EVPN
2023 May 18
5
[Bridge] [PATCH net-next 0/5] Add layer 2 miss indication and filtering
tl;dr
=====
This patchset adds a single bit to the skb to indicate that a packet
encountered a layer 2 miss in the bridge and extends flower to match on
this metadata. This is required for non-DF (Designated Forwarder)
filtering in EVPN multi-homing which prevents decapsulated BUM packets
from being forwarded multiple times to the same multi-homed host.
Background
==========
In a typical EVPN