Donate to e Foundation | Murena handsets with /e/OS | Own a part of Murena! Learn more

Commit 371e59ad authored by Ido Schimmel's avatar Ido Schimmel Committed by David S. Miller
Browse files

switchdev: Make flood to CPU optional 



In certain use cases it is not always desirable for the switch device to
flood traffic to CPU port. Instead, only certain packet types (e.g.
STP, LACP) should be trapped to it.

Signed-off-by: default avatarIdo Schimmel <idosch@mellanox.com>
Signed-off-by: default avatarJiri Pirko <jiri@mellanox.com>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent 741af005

Documentation/networking/switchdev.txt

+2 −2
Original line number Diff line number Diff line
@@ -278,8 +278,8 @@ Flooding L2 domain 
For a given L2 VLAN domain, the switch device should flood multicast/broadcast

and unknown unicast packets to all ports in domain, if allowed by port's

current STP state.  The switch driver, knowing which ports are within which

vlan L2 domain, can program the switch device for flooding.  The packet should

also be sent to the port netdev for processing by the bridge driver.  The

vlan L2 domain, can program the switch device for flooding.  The packet may

be sent to the port netdev for processing by the bridge driver.  The

bridge should not reflood the packet to the same ports the device flooded,

otherwise there will be duplicate packets on the wire.