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>,
"Amit Cohen" <amcohen@nvidia.com>, <mlxsw@nvidia.com>
Subject: [PATCH net-next 0/5] mlxsw: Adjust QOS tests for Spectrum-4 testing
Date: Wed, 14 Sep 2022 13:21:47 +0200 [thread overview]
Message-ID: <cover.1663152826.git.petrm@nvidia.com> (raw)
Amit writes:
Quality Of Service tests create congestion and verify the switch behavior.
To create congestion, they need to have more traffic than the port can
handle, so some of them force 1Gbps speed.
The tests assume that 1Gbps speed is supported. Spectrum-4 ASIC will not
support this speed in all ports, so to be able to run QOS tests there,
some adjustments are required.
Patch set overview:
Patch #1 adjusts qos_ets_strict, qos_mc_aware and sch_ets tests.
Patch #2 adjusts RED tests.
Patch #3 extends devlink_lib to support querying maximum pool size.
Patch #4 adds a test which can be used instead of qos_burst and do not
assume that 1Gbps speed is supported.
Patch #5 removes qos_burst test.
Amit Cohen (5):
selftests: mlxsw: Use shapers in QOS tests instead of forcing speed
selftests: mlxsw: Use shapers in QOS RED tests instead of forcing
speed
selftests: devlink_lib: Add function for querying maximum pool size
selftests: mlxsw: Add QOS test for maximum use of descriptors
selftests: mlxsw: Remove qos_burst test
.../selftests/drivers/net/mlxsw/mlxsw_lib.sh | 14 +
.../selftests/drivers/net/mlxsw/qos_burst.sh | 480 ------------------
.../drivers/net/mlxsw/qos_ets_strict.sh | 5 +-
.../drivers/net/mlxsw/qos_max_descriptors.sh | 282 ++++++++++
.../drivers/net/mlxsw/qos_mc_aware.sh | 9 +-
.../selftests/drivers/net/mlxsw/sch_ets.sh | 15 +-
.../drivers/net/mlxsw/sch_red_core.sh | 23 +-
.../drivers/net/mlxsw/sch_red_ets.sh | 4 +-
.../drivers/net/mlxsw/sch_red_root.sh | 4 +-
.../selftests/net/forwarding/devlink_lib.sh | 5 +
10 files changed, 332 insertions(+), 509 deletions(-)
delete mode 100755 tools/testing/selftests/drivers/net/mlxsw/qos_burst.sh
create mode 100755 tools/testing/selftests/drivers/net/mlxsw/qos_max_descriptors.sh
--
2.35.3
next reply other threads:[~2022-09-14 11:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-14 11:21 Petr Machata [this message]
2022-09-14 11:21 ` [PATCH net-next 1/5] selftests: mlxsw: Use shapers in QOS tests instead of forcing speed Petr Machata
2022-09-14 11:21 ` [PATCH net-next 2/5] selftests: mlxsw: Use shapers in QOS RED " Petr Machata
2022-09-14 11:21 ` [PATCH net-next 3/5] selftests: devlink_lib: Add function for querying maximum pool size Petr Machata
2022-09-14 11:21 ` [PATCH net-next 4/5] selftests: mlxsw: Add QOS test for maximum use of descriptors Petr Machata
2022-09-14 11:21 ` [PATCH net-next 5/5] selftests: mlxsw: Remove qos_burst test Petr Machata
2022-09-20 1:10 ` [PATCH net-next 0/5] mlxsw: Adjust QOS tests for Spectrum-4 testing 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.1663152826.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 \
/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).