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>, Amit Cohen <amcohen@nvidia.com>,
"Shuah Khan" <shuah@kernel.org>, Petr Machata <petrm@nvidia.com>,
<mlxsw@nvidia.com>
Subject: [PATCH net-next 0/4] selftests: mlxsw: Add ordering tests for unified bridge model
Date: Wed, 17 Aug 2022 17:28:24 +0200 [thread overview]
Message-ID: <cover.1660747162.git.petrm@nvidia.com> (raw)
Amit Cohen writes:
Commit 798661c73672 ("Merge branch 'mlxsw-unified-bridge-conversion-part-6'")
converted mlxsw driver to use unified bridge model. In the legacy model,
when a RIF was created / destroyed, it was firmware's responsibility to
update it in the relevant FID classification records. In the unified bridge
model, this responsibility moved to software.
This set adds tests to check the order of configuration for the following
classifications:
1. {Port, VID} -> FID
2. VID -> FID
3. VNI -> FID (after decapsulation)
In addition, in the legacy model, software is responsible to update a
table which is used to determine the packet's egress VID. Add a test to
check that the order of configuration does not impact switch behavior.
See more details in the commit messages.
Note that the tests supposed to pass also using the legacy model, they
are added now as with the new model they test the driver and not the
firmware.
Patch set overview:
Patch #1 adds test for {Port, VID} -> FID
Patch #2 adds test for VID -> FID
Patch #3 adds test for VNI -> FID
Patch #4 adds test for egress VID classification
Amit Cohen (4):
selftests: mlxsw: Add ingress RIF configuration test for 802.1D bridge
selftests: mlxsw: Add ingress RIF configuration test for 802.1Q bridge
selftests: mlxsw: Add ingress RIF configuration test for VXLAN
selftests: mlxsw: Add egress VID classification test
.../net/mlxsw/egress_vid_classification.sh | 273 +++++++++++++++
.../drivers/net/mlxsw/ingress_rif_conf_1d.sh | 264 +++++++++++++++
.../drivers/net/mlxsw/ingress_rif_conf_1q.sh | 264 +++++++++++++++
.../net/mlxsw/ingress_rif_conf_vxlan.sh | 311 ++++++++++++++++++
4 files changed, 1112 insertions(+)
create mode 100755 tools/testing/selftests/drivers/net/mlxsw/egress_vid_classification.sh
create mode 100755 tools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_1d.sh
create mode 100755 tools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_1q.sh
create mode 100755 tools/testing/selftests/drivers/net/mlxsw/ingress_rif_conf_vxlan.sh
--
2.35.3
next reply other threads:[~2022-08-17 15:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-17 15:28 Petr Machata [this message]
2022-08-17 15:28 ` [PATCH net-next 1/4] selftests: mlxsw: Add ingress RIF configuration test for 802.1D bridge Petr Machata
2022-08-17 15:28 ` [PATCH net-next 2/4] selftests: mlxsw: Add ingress RIF configuration test for 802.1Q bridge Petr Machata
2022-08-17 15:28 ` [PATCH net-next 3/4] selftests: mlxsw: Add ingress RIF configuration test for VXLAN Petr Machata
2022-08-17 15:28 ` [PATCH net-next 4/4] selftests: mlxsw: Add egress VID classification test Petr Machata
2022-08-19 4:00 ` [PATCH net-next 0/4] selftests: mlxsw: Add ordering tests for unified bridge model 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.1660747162.git.petrm@nvidia.com \
--to=petrm@nvidia.com \
--cc=amcohen@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 \
--cc=shuah@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;
as well as URLs for NNTP newsgroup(s).