From: Ido Schimmel <idosch@mellanox.com>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, jiri@mellanox.com, petrm@mellanox.com,
mlxsw@mellanox.com, Ido Schimmel <idosch@mellanox.com>
Subject: [PATCH net-next 0/6] mlxsw: Support bridge router interfaces with non-default VLAN
Date: Mon, 25 Jun 2018 10:48:12 +0300 [thread overview]
Message-ID: <20180625074818.17073-1-idosch@mellanox.com> (raw)
Petr says:
When traffic is inserted on a router interface associated with an 802.1q
bridge, the VLAN that the traffic appears on is determined by PVID of
the bridge device itself. However currently mlxsw always configures such
traffic to be forwarded to VLAN 1, regardless of the bridge PVID.
Fix the problem by modifying the FID-handling code to assign such
traffic not to FID that corresponds to VLAN 1, but to a FID that
corresponds to the configured PVID. Bail out if there is no PVID. This
is implemented in patches #1 and #2.
>From that point on, also forbid any changes to bridge device PVID,
because such changes would not be reflected. This is implemented in
patches #3, #4 and #5.
Finally in patch #6, introduce tests that use bridge as a routed
interface, and test mlxsw in both the currently-supported scenario of
using PVID 1, and the newly-supported one of using a custom PVID.
Petr Machata (6):
mlxsw: spectrum_router: Propagate extack to .fid_get()
mlxsw: spectrum_router: Allocate FID according to PVID
mlxsw: spectrum_router: Publish mlxsw_sp_rif_find_by_dev()
mlxsw: spectrum_router: Add mlxsw_sp_rif_fid()
mlxsw: spectrum_switchdev: Ban PVID change if bridge has a RIF
selftests: forwarding: Test routed bridge interface
.../net/ethernet/mellanox/mlxsw/spectrum_router.c | 42 +++++--
.../net/ethernet/mellanox/mlxsw/spectrum_router.h | 3 +
.../ethernet/mellanox/mlxsw/spectrum_switchdev.c | 47 +++++++-
.../selftests/net/forwarding/router_bridge.sh | 113 ++++++++++++++++++
.../selftests/net/forwarding/router_bridge_vlan.sh | 132 +++++++++++++++++++++
5 files changed, 323 insertions(+), 14 deletions(-)
create mode 100755 tools/testing/selftests/net/forwarding/router_bridge.sh
create mode 100755 tools/testing/selftests/net/forwarding/router_bridge_vlan.sh
--
2.14.4
next reply other threads:[~2018-06-25 7:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-25 7:48 Ido Schimmel [this message]
2018-06-25 7:48 ` [PATCH net-next 1/6] mlxsw: spectrum_router: Propagate extack to .fid_get() Ido Schimmel
2018-06-25 7:48 ` [PATCH net-next 2/6] mlxsw: spectrum_router: Allocate FID according to PVID Ido Schimmel
2018-06-25 7:48 ` [PATCH net-next 3/6] mlxsw: spectrum_router: Publish mlxsw_sp_rif_find_by_dev() Ido Schimmel
2018-06-25 7:48 ` [PATCH net-next 4/6] mlxsw: spectrum_router: Add mlxsw_sp_rif_fid() Ido Schimmel
2018-06-25 7:48 ` [PATCH net-next 5/6] mlxsw: spectrum_switchdev: Ban PVID change if bridge has a RIF Ido Schimmel
2018-06-25 7:48 ` [PATCH net-next 6/6] selftests: forwarding: Test routed bridge interface Ido Schimmel
2018-06-26 9:06 ` [PATCH net-next 0/6] mlxsw: Support bridge router interfaces with non-default VLAN 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=20180625074818.17073-1-idosch@mellanox.com \
--to=idosch@mellanox.com \
--cc=davem@davemloft.net \
--cc=jiri@mellanox.com \
--cc=mlxsw@mellanox.com \
--cc=netdev@vger.kernel.org \
--cc=petrm@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