From: Petr Machata <petrm@nvidia.com>
To: <netdev@vger.kernel.org>
Cc: "David S. Miller" <davem@davemloft.net>,
Jakub Kicinski <kuba@kernel.org>,
Ido Schimmel <idosch@nvidia.com>, Petr Machata <petrm@nvidia.com>
Subject: [PATCH net-next 0/6] mlxsw: PFC and headroom selftests
Date: Wed, 30 Sep 2020 12:49:06 +0200 [thread overview]
Message-ID: <cover.1601462261.git.petrm@nvidia.com> (raw)
Recent changes in the headroom management code made it clear that an
automated way of testing this functionality is needed. This patchset brings
two tests: a synthetic headroom behavior test, which verifies mechanics of
headroom management. And a PFC test, which verifies whether this behavior
actually translates into a working lossless configuration.
Both of these tests rely on mlnx_qos[1], a tool that interfaces with Linux
DCB API. The tool was originally written to work with Mellanox NICs, but
does not actually rely on anything Mellanox-specific, and can be used for
mlxsw as well as for any other NIC-like driver. Unlike Open LLDP it does
support buffer commands and permits a fire-and-forget approach to
configuration, which makes it very handy for writing of selftests.
Patches #1-#3 extend the selftest devlink_lib.sh in various ways. Patch #4
then adds a helper wrapper for mlnx_qos to mlxsw's qos_lib.sh.
Patch #5 adds a test for management of port headroom.
Patch #6 adds a PFC test.
[1] https://github.com/Mellanox/mlnx-tools/
Petr Machata (6):
selftests: forwarding: devlink_lib: Split devlink_..._set() into save
& set
selftests: forwarding: devlink_lib: Add devlink_cell_size_get()
selftests: forwarding: devlink_lib: Support port-less topologies
selftests: mlxsw: qos_lib: Add a wrapper for running mlnx_qos
selftests: mlxsw: Add headroom handling test
selftests: mlxsw: Add a PFC test
.../drivers/net/mlxsw/qos_ets_strict.sh | 9 +
.../drivers/net/mlxsw/qos_headroom.sh | 379 ++++++++++++++++
.../selftests/drivers/net/mlxsw/qos_lib.sh | 14 +
.../drivers/net/mlxsw/qos_mc_aware.sh | 5 +
.../selftests/drivers/net/mlxsw/qos_pfc.sh | 403 ++++++++++++++++++
.../selftests/drivers/net/mlxsw/sch_ets.sh | 6 +
.../drivers/net/mlxsw/sch_red_core.sh | 1 +
.../selftests/net/forwarding/devlink_lib.sh | 72 +++-
8 files changed, 876 insertions(+), 13 deletions(-)
create mode 100755 tools/testing/selftests/drivers/net/mlxsw/qos_headroom.sh
create mode 100755 tools/testing/selftests/drivers/net/mlxsw/qos_pfc.sh
--
2.20.1
next reply other threads:[~2020-09-30 10:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-30 10:49 Petr Machata [this message]
2020-09-30 10:49 ` [PATCH net-next 1/6] selftests: forwarding: devlink_lib: Split devlink_..._set() into save & set Petr Machata
2020-09-30 10:49 ` [PATCH net-next 2/6] selftests: forwarding: devlink_lib: Add devlink_cell_size_get() Petr Machata
2020-09-30 10:49 ` [PATCH net-next 3/6] selftests: forwarding: devlink_lib: Support port-less topologies Petr Machata
2020-09-30 10:49 ` [PATCH net-next 4/6] selftests: mlxsw: qos_lib: Add a wrapper for running mlnx_qos Petr Machata
2020-09-30 10:49 ` [PATCH net-next 5/6] selftests: mlxsw: Add headroom handling test Petr Machata
2020-09-30 10:49 ` [PATCH net-next 6/6] selftests: mlxsw: Add a PFC test Petr Machata
2020-09-30 21:07 ` [PATCH net-next 0/6] mlxsw: PFC and headroom selftests 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=cover.1601462261.git.petrm@nvidia.com \
--to=petrm@nvidia.com \
--cc=davem@davemloft.net \
--cc=idosch@nvidia.com \
--cc=kuba@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).