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: Amit Cohen <amcohen@nvidia.com>, Ido Schimmel <idosch@nvidia.com>,
<linux-kselftest@vger.kernel.org>, Shuah Khan <shuah@kernel.org>,
"Petr Machata" <petrm@nvidia.com>, <mlxsw@nvidia.com>
Subject: [PATCH net-next 0/5] selftests: mlxsw: Stabilize RED tests
Date: Mon, 7 Oct 2024 18:26:04 +0200 [thread overview]
Message-ID: <cover.1728316370.git.petrm@nvidia.com> (raw)
Tweak the mlxsw-specific RED selftests to increase stability on
Spectrum-3 and Spectrum-4 machines.
Petr Machata (5):
selftests: mlxsw: sch_red_ets: Increase required backlog
selftests: mlxsw: sch_red_core: Increase backlog size tolerance
selftests: mlxsw: sch_red_core: Sleep before querying queue depth
selftests: mlxsw: sch_red_core: Send more packets for drop tests
selftests: mlxsw: sch_red_core: Lower TBF rate
.../drivers/net/mlxsw/sch_red_core.sh | 28 +++++++++++--------
.../drivers/net/mlxsw/sch_red_ets.sh | 8 +++---
2 files changed, 20 insertions(+), 16 deletions(-)
--
2.45.0
next reply other threads:[~2024-10-07 16:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-07 16:26 Petr Machata [this message]
2024-10-07 16:26 ` [PATCH net-next 1/5] selftests: mlxsw: sch_red_ets: Increase required backlog Petr Machata
2024-10-07 16:26 ` [PATCH net-next 2/5] selftests: mlxsw: sch_red_core: Increase backlog size tolerance Petr Machata
2024-10-07 16:26 ` [PATCH net-next 3/5] selftests: mlxsw: sch_red_core: Sleep before querying queue depth Petr Machata
2024-10-07 16:26 ` [PATCH net-next 4/5] selftests: mlxsw: sch_red_core: Send more packets for drop tests Petr Machata
2024-10-07 16:26 ` [PATCH net-next 5/5] selftests: mlxsw: sch_red_core: Lower TBF rate Petr Machata
2024-10-08 23:20 ` [PATCH net-next 0/5] selftests: mlxsw: Stabilize RED tests 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.1728316370.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=linux-kselftest@vger.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).