Linux Kernel Selftest development
 help / color / mirror / Atom feed
From: Carolina Jubran <cjubran@nvidia.com>
To: Shuah Khan <shuah@kernel.org>,
	Andrew Lunn <andrew+netdev@lunn.ch>,
	"David S . Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	"Jakub Kicinski" <kuba@kernel.org>,
	Paolo Abeni <pabeni@redhat.com>, Simon Horman <horms@kernel.org>
Cc: Gal Pressman <gal@nvidia.com>, Tariq Toukan <tariqt@nvidia.com>,
	"Cosmin Ratiu" <cratiu@nvidia.com>,
	Nimrod Oren <noren@nvidia.com>, Mark Bloch <mbloch@nvidia.com>,
	<linux-kernel@vger.kernel.org>, <linux-kselftest@vger.kernel.org>,
	<netdev@vger.kernel.org>
Subject: [PATCH v2 net 0/2] selftests: drv-net: Fix issues in devlink_rate_tc_bw.py
Date: Tue, 9 Sep 2025 13:13:51 +0300	[thread overview]
Message-ID: <20250909101353.3778751-1-cjubran@nvidia.com> (raw)

This series fixes issues in devlink_rate_tc_bw.py selftest that made
its checks unreliable and its documentation inconsistent with the
actual configuration.

V2:
- Dropped the patch that relaxed the total bandwidth check. Jakub
  suggested addressing the instability with interval-based measurement
  and by migrating to load.py. That will be handled in a follow-up.
- Link to V1: https://lore.kernel.org/netdev/20250831080641.1828455-1-cjubran@nvidia.com/

Thanks

Carolina Jubran (2):
  selftests: drv-net: Fix and clarify TC bandwidth split in
    devlink_rate_tc_bw.py
  selftests: drv-net: Fix tolerance calculation in devlink_rate_tc_bw.py

 .../drivers/net/hw/devlink_rate_tc_bw.py      | 100 ++++++++----------
 1 file changed, 43 insertions(+), 57 deletions(-)

-- 
2.38.1


             reply	other threads:[~2025-09-09 10:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-09 10:13 Carolina Jubran [this message]
2025-09-09 10:13 ` [PATCH v2 net 1/2] selftests: drv-net: Fix and clarify TC bandwidth split in devlink_rate_tc_bw.py Carolina Jubran
2025-09-10  8:34   ` Simon Horman
2025-09-09 10:13 ` [PATCH v2 net 2/2] selftests: drv-net: Fix tolerance calculation " Carolina Jubran
2025-09-10  8:35   ` Simon Horman
2025-09-10  8:36 ` [PATCH v2 net 0/2] selftests: drv-net: Fix issues " Simon Horman

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=20250909101353.3778751-1-cjubran@nvidia.com \
    --to=cjubran@nvidia.com \
    --cc=andrew+netdev@lunn.ch \
    --cc=cratiu@nvidia.com \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=horms@kernel.org \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-kselftest@vger.kernel.org \
    --cc=mbloch@nvidia.com \
    --cc=netdev@vger.kernel.org \
    --cc=noren@nvidia.com \
    --cc=pabeni@redhat.com \
    --cc=shuah@kernel.org \
    --cc=tariqt@nvidia.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