From: Petr Machata <petrm@nvidia.com>
To: "David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
<netdev@vger.kernel.org>
Cc: Ido Schimmel <idosch@nvidia.com>, Petr Machata <petrm@nvidia.com>,
Danielle Ratson <danieller@nvidia.com>, <mlxsw@nvidia.com>
Subject: [PATCH net-next 0/8] selftests: New selftests for out-of-order-operations patches in mlxsw
Date: Mon, 31 Jul 2023 17:47:14 +0200 [thread overview]
Message-ID: <cover.1690815746.git.petrm@nvidia.com> (raw)
In the past, the mlxsw driver made the assumption that the user applies
configuration in a bottom-up manner. Thus netdevices needed to be added to
the bridge before IP addresses were configured on that bridge or SVI added
on top of it, because whatever happened before a netdevice was mlxsw upper
was generally ignored by mlxsw. Recently, several patch series were pushed
to introduce the bookkeeping and replays necessary to offload the full
state, not just the immediate configuration step.
In this patchset, introduce new selftests that directly exercise the out of
order code paths in mlxsw.
- Patch #1 adds new tests into the existing selftest router_bridge.sh.
- Patches #2-#5 add new generic selftests.
- Patches #6-#8 add new mlxsw-specific selftests.
Petr Machata (8):
selftests: router_bridge: Add remastering tests
selftests: router_bridge_1d: Add a new selftest
selftests: router_bridge_vlan_upper: Add a new selftest
selftests: router_bridge_lag: Add a new selftest
selftests: router_bridge_1d_lag: Add a new selftest
selftests: mlxsw: rif_lag: Add a new selftest
selftests: mlxsw: rif_lag_vlan: Add a new selftest
selftests: mlxsw: rif_bridge: Add a new selftest
.../selftests/drivers/net/mlxsw/rif_bridge.sh | 183 ++++++++
.../selftests/drivers/net/mlxsw/rif_lag.sh | 136 ++++++
.../drivers/net/mlxsw/rif_lag_vlan.sh | 146 +++++++
.../testing/selftests/net/forwarding/Makefile | 4 +
.../selftests/net/forwarding/router_bridge.sh | 26 ++
.../net/forwarding/router_bridge_1d.sh | 185 ++++++++
.../net/forwarding/router_bridge_1d_lag.sh | 408 ++++++++++++++++++
.../net/forwarding/router_bridge_lag.sh | 323 ++++++++++++++
.../forwarding/router_bridge_vlan_upper.sh | 169 ++++++++
9 files changed, 1580 insertions(+)
create mode 100755 tools/testing/selftests/drivers/net/mlxsw/rif_bridge.sh
create mode 100755 tools/testing/selftests/drivers/net/mlxsw/rif_lag.sh
create mode 100755 tools/testing/selftests/drivers/net/mlxsw/rif_lag_vlan.sh
create mode 100755 tools/testing/selftests/net/forwarding/router_bridge_1d.sh
create mode 100755 tools/testing/selftests/net/forwarding/router_bridge_1d_lag.sh
create mode 100755 tools/testing/selftests/net/forwarding/router_bridge_lag.sh
create mode 100755 tools/testing/selftests/net/forwarding/router_bridge_vlan_upper.sh
--
2.41.0
next reply other threads:[~2023-07-31 15:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-31 15:47 Petr Machata [this message]
2023-07-31 15:47 ` [PATCH net-next 1/8] selftests: router_bridge: Add remastering tests Petr Machata
2023-07-31 15:47 ` [PATCH net-next 2/8] selftests: router_bridge_1d: Add a new selftest Petr Machata
2023-07-31 15:47 ` [PATCH net-next 3/8] selftests: router_bridge_vlan_upper: " Petr Machata
2023-07-31 15:47 ` [PATCH net-next 4/8] selftests: router_bridge_lag: " Petr Machata
2023-07-31 15:47 ` [PATCH net-next 5/8] selftests: router_bridge_1d_lag: " Petr Machata
2023-07-31 15:47 ` [PATCH net-next 6/8] selftests: mlxsw: rif_lag: " Petr Machata
2023-07-31 15:47 ` [PATCH net-next 7/8] selftests: mlxsw: rif_lag_vlan: " Petr Machata
2023-07-31 15:47 ` [PATCH net-next 8/8] selftests: mlxsw: rif_bridge: " Petr Machata
2023-08-02 8:20 ` [PATCH net-next 0/8] selftests: New selftests for out-of-order-operations patches in mlxsw 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=cover.1690815746.git.petrm@nvidia.com \
--to=petrm@nvidia.com \
--cc=danieller@nvidia.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--cc=mlxsw@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.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).