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: mlxsw <mlxsw@mellanox.com>,
"nikolay@cumulusnetworks.com" <nikolay@cumulusnetworks.com>,
"roopa@cumulusnetworks.com" <roopa@cumulusnetworks.com>,
Ido Schimmel <idosch@mellanox.com>,
Jiri Pirko <jiri@mellanox.com>, Petr Machata <petrm@mellanox.com>,
"davem@davemloft.net" <davem@davemloft.net>
Subject: [Bridge] [PATCH net-next 0/8] mlxsw: Add VxLAN support with VLAN-aware bridges
Date: Wed, 28 Nov 2018 20:06:56 +0000 [thread overview]
Message-ID: <20181128200558.31343-1-idosch@mellanox.com> (raw)
Commit 53e50a6ec24d ("Merge branch 'mlxsw-Add-VxLAN-support'") added
mlxsw support for VxLAN when the VxLAN device was enslaved to
VLAN-unaware bridges. This patchset extends mlxsw to also support VxLAN
with VLAN-aware bridges.
With VLAN-aware bridges, the VxLAN device's VNI is mapped to the VLAN
that is configured as 'pvid untagged' on the corresponding bridge port.
To prevent ambiguity, mlxsw forbids configurations in which the same
VLAN is configured as 'pvid untagged' on multiple VxLAN devices.
Patches #1-#2 add the necessary APIs in mlxsw and the bridge driver.
Patches #3-#4 perform small refactoring in order to prepare mlxsw for
VLAN-aware support.
Patch #5 finally enables the enslavement of VxLAN devices to a
VLAN-aware bridge. Among other things, it extends mlxsw to handle
switchdev notifications about VLAN add / delete on a VxLAN device
enslaved to an offloaded VLAN-aware bridge.
Patches #6-#8 add selftests to test the new functionality.
Ido Schimmel (8):
net: bridge: Extend br_vlan_get_pvid() for bridge ports
mlxsw: spectrum_fid: Add API to lookup 802.1Q FIDs without creating
them
mlxsw: spectrum_switchdev: Unify VxLAN leave function
mlxsw: spectrum_switchdev: Prepare function for VLAN-aware bridges
mlxsw: spectrum: Enable VxLAN enslavement to VLAN-aware bridges
selftests: mlxsw: Consider VLAN-aware bridges as valid
selftests: mlxsw: Add a test for VxLAN configuration with a VLAN-aware
bridge
selftests: forwarding: Add VxLAN test with a VLAN-aware bridge
.../net/ethernet/mellanox/mlxsw/spectrum.c | 53 +-
.../net/ethernet/mellanox/mlxsw/spectrum.h | 26 +-
.../ethernet/mellanox/mlxsw/spectrum_fid.c | 6 +
.../mellanox/mlxsw/spectrum_switchdev.c | 407 +++++++--
net/bridge/br_vlan.c | 6 +-
.../selftests/drivers/net/mlxsw/vxlan.sh | 206 ++++-
.../net/forwarding/vxlan_bridge_1q.sh | 790 ++++++++++++++++++
.../forwarding/vxlan_bridge_1q_port_8472.sh | 10 +
8 files changed, 1441 insertions(+), 63 deletions(-)
create mode 100755 tools/testing/selftests/net/forwarding/vxlan_bridge_1q.sh
create mode 100755 tools/testing/selftests/net/forwarding/vxlan_bridge_1q_port_8472.sh
--
2.19.1
next reply other threads:[~2018-11-28 20:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-28 20:06 Ido Schimmel [this message]
2018-11-28 20:06 ` [Bridge] [PATCH net-next 1/8] net: bridge: Extend br_vlan_get_pvid() for bridge ports Ido Schimmel
2018-11-28 20:06 ` [Bridge] [PATCH net-next 2/8] mlxsw: spectrum_fid: Add API to lookup 802.1Q FIDs without creating them Ido Schimmel
2018-11-28 20:07 ` [Bridge] [PATCH net-next 3/8] mlxsw: spectrum_switchdev: Unify VxLAN leave function Ido Schimmel
2018-11-28 20:07 ` [Bridge] [PATCH net-next 4/8] mlxsw: spectrum_switchdev: Prepare function for VLAN-aware bridges Ido Schimmel
2018-11-28 20:07 ` [Bridge] [PATCH net-next 5/8] mlxsw: spectrum: Enable VxLAN enslavement to " Ido Schimmel
2018-11-28 20:07 ` [Bridge] [PATCH net-next 6/8] selftests: mlxsw: Consider VLAN-aware bridges as valid Ido Schimmel
2018-11-28 20:07 ` [Bridge] [PATCH net-next 7/8] selftests: mlxsw: Add a test for VxLAN configuration with a VLAN-aware bridge Ido Schimmel
2018-11-28 20:07 ` [Bridge] [PATCH net-next 8/8] selftests: forwarding: Add VxLAN test " Ido Schimmel
2018-12-01 1:08 ` [Bridge] [PATCH net-next 0/8] mlxsw: Add VxLAN support with VLAN-aware bridges 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=20181128200558.31343-1-idosch@mellanox.com \
--to=idosch@mellanox.com \
--cc=bridge@lists.linux-foundation.org \
--cc=davem@davemloft.net \
--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