From: Jiri Pirko <jiri@resnulli.us>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, idosch@mellanox.com, eladr@mellanox.com,
yotamg@mellanox.com, ogerlitz@mellanox.com, sagir@mellanox.com
Subject: [patch net-next 02/12] switchdev: Make flood to CPU optional
Date: Wed, 28 Oct 2015 10:16:55 +0100 [thread overview]
Message-ID: <1446023825-7162-3-git-send-email-jiri@resnulli.us> (raw)
In-Reply-To: <1446023825-7162-1-git-send-email-jiri@resnulli.us>
From: Ido Schimmel <idosch@mellanox.com>
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 <idosch@mellanox.com>
Signed-off-by: Jiri Pirko <jiri@mellanox.com>
---
Documentation/networking/switchdev.txt | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
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.
--
1.9.3
next prev parent reply other threads:[~2015-10-28 9:17 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-28 9:16 [patch net-next 00/12] mlxsw: driver update Jiri Pirko
2015-10-28 9:16 ` [patch net-next 01/12] switchdev: Add support for flood control Jiri Pirko
2015-10-28 9:16 ` Jiri Pirko [this message]
2015-10-28 9:16 ` [patch net-next 03/12] mlxsw: spectrum: move "bridged" bool to u8 flags Jiri Pirko
2015-10-28 9:16 ` [patch net-next 04/12] mlxsw: spectrum: Add support for VLAN ranges in flooding configuration Jiri Pirko
2015-10-28 9:16 ` [patch net-next 05/12] mlxsw: spectrum: Add support for flood control Jiri Pirko
2015-10-28 9:16 ` [patch net-next 06/12] mlxsw: reg: Fix description for reg_sfd_uc_sub_port Jiri Pirko
2015-10-28 9:17 ` [patch net-next 07/12] mlxsw: reg: Fix desription typos of couple of SFN items Jiri Pirko
2015-10-28 9:17 ` [patch net-next 08/12] mlxsw: reg: Avoid unnecessary line wrap for mlxsw_reg_sfd_uc_unpack Jiri Pirko
2015-10-28 9:17 ` [patch net-next 09/12] mlxsw: spectrum: Fix ageing time value Jiri Pirko
2015-10-28 9:17 ` [patch net-next 10/12] mlxsw: Put constant on the right side of comparisons Jiri Pirko
2015-10-28 9:17 ` [patch net-next 11/12] mlxsw: Put braces on all arms of branch statement Jiri Pirko
2015-10-28 9:17 ` [patch net-next 12/12] mlxsw: spectrum: Make mlxsw_sp_port_switchdev_ops static Jiri Pirko
2015-10-30 3:27 ` [patch net-next 00/12] mlxsw: driver update David Miller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1446023825-7162-3-git-send-email-jiri@resnulli.us \
--to=jiri@resnulli.us \
--cc=davem@davemloft.net \
--cc=eladr@mellanox.com \
--cc=idosch@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=ogerlitz@mellanox.com \
--cc=sagir@mellanox.com \
--cc=yotamg@mellanox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).