From: Ido Schimmel <idosch@idosch.org>
To: netdev@vger.kernel.org
Cc: davem@davemloft.net, kuba@kernel.org, dsahern@gmail.com,
jiri@nvidia.com, mlxsw@nvidia.com,
Ido Schimmel <idosch@nvidia.com>
Subject: [PATCH net-next 0/8] mlxsw: Add support for nexthop objects
Date: Thu, 19 Nov 2020 15:08:40 +0200 [thread overview]
Message-ID: <20201119130848.407918-1-idosch@idosch.org> (raw)
From: Ido Schimmel <idosch@nvidia.com>
This patch set adds support for nexthop objects in mlxsw. Nexthop
objects are treated as another front-end for programming nexthops, in
addition to the existing IPv4 and IPv6 front-ends.
Patch #1 registers a listener to the nexthop notification chain and
parses the nexthop information into the existing mlxsw data structures
that are already used by the IPv4 and IPv6 front-ends. Blackhole
nexthops are currently rejected. Support will be added in a follow-up
patch set.
Patch #2 extends mlxsw to resolve its internal nexthop objects from the
nexthop identifier encoded in the FIB info of the notified routes.
Patch #3 finally removes the limitation of rejecting routes that use
nexthop objects.
Patch #4 adds a selftest.
Patches #5-#8 add generic forwarding selftests that can be used with
veth pairs or physical loopbacks.
Ido Schimmel (8):
mlxsw: spectrum_router: Add support for nexthop objects
mlxsw: spectrum_router: Enable resolution of nexthop groups from
nexthop objects
mlxsw: spectrum_router: Allow programming routes with nexthop objects
selftests: mlxsw: Add nexthop objects configuration tests
selftests: forwarding: Do not configure nexthop objects twice
selftests: forwarding: Test IPv4 routes with IPv6 link-local nexthops
selftests: forwarding: Add device-only nexthop test
selftests: forwarding: Add multipath tunneling nexthop test
.../ethernet/mellanox/mlxsw/spectrum_router.c | 498 +++++++++++++++++-
.../ethernet/mellanox/mlxsw/spectrum_router.h | 1 +
.../selftests/drivers/net/mlxsw/rtnetlink.sh | 189 +++++++
.../net/forwarding/gre_multipath_nh.sh | 356 +++++++++++++
.../net/forwarding/router_mpath_nh.sh | 12 +-
.../selftests/net/forwarding/router_nh.sh | 160 ++++++
6 files changed, 1201 insertions(+), 15 deletions(-)
create mode 100755 tools/testing/selftests/net/forwarding/gre_multipath_nh.sh
create mode 100755 tools/testing/selftests/net/forwarding/router_nh.sh
--
2.28.0
next reply other threads:[~2020-11-19 13:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-19 13:08 Ido Schimmel [this message]
2020-11-19 13:08 ` [PATCH net-next 1/8] mlxsw: spectrum_router: Add support for nexthop objects Ido Schimmel
2020-11-19 13:08 ` [PATCH net-next 2/8] mlxsw: spectrum_router: Enable resolution of nexthop groups from " Ido Schimmel
2020-11-19 13:08 ` [PATCH net-next 3/8] mlxsw: spectrum_router: Allow programming routes with " Ido Schimmel
2020-11-19 13:08 ` [PATCH net-next 4/8] selftests: mlxsw: Add nexthop objects configuration tests Ido Schimmel
2020-11-19 13:08 ` [PATCH net-next 5/8] selftests: forwarding: Do not configure nexthop objects twice Ido Schimmel
2020-11-19 13:08 ` [PATCH net-next 6/8] selftests: forwarding: Test IPv4 routes with IPv6 link-local nexthops Ido Schimmel
2020-11-19 13:08 ` [PATCH net-next 7/8] selftests: forwarding: Add device-only nexthop test Ido Schimmel
2020-11-19 13:08 ` [PATCH net-next 8/8] selftests: forwarding: Add multipath tunneling " Ido Schimmel
2020-11-20 23:30 ` [PATCH net-next 0/8] mlxsw: Add support for nexthop objects patchwork-bot+netdevbpf
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=20201119130848.407918-1-idosch@idosch.org \
--to=idosch@idosch.org \
--cc=davem@davemloft.net \
--cc=dsahern@gmail.com \
--cc=idosch@nvidia.com \
--cc=jiri@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
/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