netdev - Avoiding bridge flood of multicast when L2 switch is used

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Tue, 14 Jun 2016 16:12:32 -0400
From:	Murali Karicheri <m-karicheri2@...com>
To:	"open list:TI NETCP ETHERNET DRIVER" <netdev@...r.kernel.org>,
	<john.r.fastabend@...el.com>,
	Florian Fainelli <f.fainelli@...il.com>
Subject: Avoiding bridge flood of multicast when L2 switch is used

netdev experts,

When there is a L2 switch underneath the network interface a flooding of
multicast at the bridge interface results in one copy of this going through each
of the slave resulting in multiple multicast packets reaching the underlying switch.
L2 switch also duplicates the multicast packet on each egress port as done
in software bridge. This is undesirable as it reduces the available bandwidth to
half when multicast packets are involved.

Is there something that can be done to avoid software bridge flooding mulicast
through a ip command or similar or to be done in the network driver? I have a TODO
item to add dsa support in our netcp driver. If this is already solved by dsa, I can
handle it as part of this work. 

Thanks in advance for your response! 
-- 
Murali Karicheri
Linux Kernel, Keystone