From: Ido Schimmel Date: Wed, 28 Oct 2015 09:16:55 +0000 (+0100) Subject: switchdev: Make flood to CPU optional X-Git-Tag: v4.4-rc1~141^2~45^2~10 X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=371e59adcebf9953385bf46d5325ac39a53c5520;p=profile%2Fcommon%2Fplatform%2Fkernel%2Flinux-artik7.git 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: Ido Schimmel Signed-off-by: Jiri Pirko Signed-off-by: David S. Miller --- diff --git a/Documentation/networking/switchdev.txt b/Documentation/networking/switchdev.txt index ce510e1..9199413 100644 --- a/Documentation/networking/switchdev.txt +++ b/Documentation/networking/switchdev.txt @@ -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.