From: Ido Schimmel <idosch@mellanox.com>
To: "netdev@vger.kernel.org" <netdev@vger.kernel.org>,
"bridge@lists.linux-foundation.org"
<bridge@lists.linux-foundation.org>
Cc: "ivecera@redhat.com" <ivecera@redhat.com>,
Ido Schimmel <idosch@mellanox.com>, mlxsw <mlxsw@mellanox.com>,
"nikolay@cumulusnetworks.com" <nikolay@cumulusnetworks.com>,
"roopa@cumulusnetworks.com" <roopa@cumulusnetworks.com>,
Jiri Pirko <jiri@mellanox.com>, Petr Machata <petrm@mellanox.com>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: [PATCH net-next 00/16] mlxsw: Add VxLAN learning support
Date: Wed, 21 Nov 2018 08:02:32 +0000 [thread overview]
Message-ID: <20181121080141.16676-1-idosch@mellanox.com> (raw)
This patchset adds VxLAN learning support in the mlxsw driver.
The first five patches from Petr add the required switchdev APIs which
allow device drivers to notify the VxLAN driver about learned / aged-out
FDB entries.
First in patch #1, an unnecessary argument is dropped from
__vxlan_fdb_delete().
In patches #2-#4, the VxLAN FDB handling code is extended to make
sending the switchdev events configurable; to mark user-added entries as
such; and to make sure HW-learned FDB entries do not take over
user-added ones.
Finally in patch #5, the necessary switchdev notifications are added and
handled by VxLAN, similarly to how this is handled in the bridge driver.
Patch #6 allows changing of the VxLAN's device ageing time since it is
useful for the selftest in the last patch.
Patch #7 adds support for querying bridge port flags of a given
netdevice, as a new entry should not be learned and notified to the
bridge driver in case learning is disabled on the bridge port.
Next patches gradually add learning support in mlxsw.
The last patch adds a new test case for VxLAN learning.
Ido Schimmel (11):
vxlan: Allow changing ageing time
bridge: Allow querying bridge port flags
mlxsw: reg: Add definition of unicast tunnel record for SFN register
mlxsw: spectrum_fid: Store ifindex of NVE device in FID
mlxsw: spectrum_fid: Allow FID lookup by its index
mlxsw: spectrum_nve: Add API to resolve learned IP addresses
mlxsw: spectrum_switchdev: Process learned VxLAN FDB entries
mlxsw: spectrum_switchdev: Allow deletion of learned FDB entries
mlxsw: spectrum_nve: Allow VxLAN learning
selftests: mlxsw: Consider VxLAN learning enabled as valid
selftests: forwarding: vxlan_bridge_1d: Add learning test
Petr Machata (5):
vxlan: __vxlan_fdb_delete(): Drop unused argument vid
vxlan: vxlan_fdb_notify(): Make switchdev notification configurable
vxlan: Mark user-added FDB entries
vxlan: Don't override user-added entries with ext-learned ones
vxlan: Add hardware FDB learning
drivers/net/ethernet/mellanox/mlxsw/reg.h | 64 ++++++
.../net/ethernet/mellanox/mlxsw/spectrum.h | 8 +-
.../ethernet/mellanox/mlxsw/spectrum_fid.c | 56 ++++-
.../ethernet/mellanox/mlxsw/spectrum_nve.c | 16 +-
.../mellanox/mlxsw/spectrum_nve_vxlan.c | 8 +-
.../mellanox/mlxsw/spectrum_switchdev.c | 206 ++++++++++++++++--
drivers/net/vxlan.c | 192 ++++++++++++----
include/linux/if_bridge.h | 6 +
include/net/switchdev.h | 2 +
include/net/vxlan.h | 1 +
net/bridge/br_if.c | 12 +
.../selftests/drivers/net/mlxsw/vxlan.sh | 2 +-
.../net/forwarding/vxlan_bridge_1d.sh | 108 +++++++++
13 files changed, 606 insertions(+), 75 deletions(-)
--
2.19.1
next reply other threads:[~2018-11-21 8:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-21 8:02 Ido Schimmel [this message]
2018-11-21 8:02 ` [PATCH net-next 01/16] vxlan: __vxlan_fdb_delete(): Drop unused argument vid Ido Schimmel
2018-11-21 8:02 ` [PATCH net-next 02/16] vxlan: vxlan_fdb_notify(): Make switchdev notification configurable Ido Schimmel
2018-11-21 8:02 ` [PATCH net-next 03/16] vxlan: Mark user-added FDB entries Ido Schimmel
2018-11-21 8:02 ` [PATCH net-next 04/16] vxlan: Don't override user-added entries with ext-learned ones Ido Schimmel
2018-11-21 8:02 ` [PATCH net-next 05/16] vxlan: Add hardware FDB learning Ido Schimmel
2018-11-21 8:02 ` [PATCH net-next 06/16] vxlan: Allow changing ageing time Ido Schimmel
2018-11-21 8:02 ` [PATCH net-next 07/16] bridge: Allow querying bridge port flags Ido Schimmel
2018-11-21 8:02 ` [PATCH net-next 08/16] mlxsw: reg: Add definition of unicast tunnel record for SFN register Ido Schimmel
2018-11-21 8:02 ` [PATCH net-next 09/16] mlxsw: spectrum_fid: Store ifindex of NVE device in FID Ido Schimmel
2018-11-21 8:02 ` [PATCH net-next 10/16] mlxsw: spectrum_fid: Allow FID lookup by its index Ido Schimmel
2018-11-21 8:02 ` [PATCH net-next 11/16] mlxsw: spectrum_nve: Add API to resolve learned IP addresses Ido Schimmel
2018-11-21 8:02 ` [PATCH net-next 12/16] mlxsw: spectrum_switchdev: Process learned VxLAN FDB entries Ido Schimmel
2018-11-21 8:02 ` [PATCH net-next 13/16] mlxsw: spectrum_switchdev: Allow deletion of learned " Ido Schimmel
2018-11-21 8:02 ` [PATCH net-next 14/16] mlxsw: spectrum_nve: Allow VxLAN learning Ido Schimmel
2018-11-21 8:02 ` [PATCH net-next 15/16] selftests: mlxsw: Consider VxLAN learning enabled as valid Ido Schimmel
2018-11-21 8:02 ` [PATCH net-next 16/16] selftests: forwarding: vxlan_bridge_1d: Add learning test Ido Schimmel
2018-11-22 1:10 ` [PATCH net-next 00/16] mlxsw: Add VxLAN learning support 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=20181121080141.16676-1-idosch@mellanox.com \
--to=idosch@mellanox.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--cc=ivecera@redhat.com \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=nikolay@cumulusnetworks.com \
--cc=petrm@mellanox.com \
--cc=roopa@cumulusnetworks.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