Netdev List
 help / color / mirror / Atom feed
From: Joe Damato <jdamato@fastly.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: davem@davemloft.net, netdev@vger.kernel.org, edumazet@google.com,
	pabeni@redhat.com, dxu@dxuuu.xyz, ecree.xilinx@gmail.com,
	przemyslaw.kitszel@intel.com, donald.hunter@gmail.com,
	gal.pressman@linux.dev, tariqt@nvidia.com,
	willemdebruijn.kernel@gmail.com
Subject: Re: [PATCH net-next 01/12] selftests: drv-net: rss_ctx: add identifier to traffic comments
Date: Fri, 2 Aug 2024 12:23:41 +0100	[thread overview]
Message-ID: <ZqzBvTmsmhPoLb_f@LQ3V64L9R2> (raw)
In-Reply-To: <20240802001801.565176-2-kuba@kernel.org>

On Thu, Aug 01, 2024 at 05:17:50PM -0700, Jakub Kicinski wrote:
> Include the "name" of the context in the comment for traffic
> checks. Makes it easier to reason about which context failed
> when we loop over 32 contexts (it may matter if we failed in
> first vs last, for example).
> 
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>
> ---
>  tools/testing/selftests/drivers/net/hw/rss_ctx.py | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/tools/testing/selftests/drivers/net/hw/rss_ctx.py b/tools/testing/selftests/drivers/net/hw/rss_ctx.py
> index 011508ca604b..1da6b214f4fe 100755
> --- a/tools/testing/selftests/drivers/net/hw/rss_ctx.py
> +++ b/tools/testing/selftests/drivers/net/hw/rss_ctx.py
> @@ -90,10 +90,10 @@ from lib.py import ethtool, ip, defer, GenerateTraffic, CmdExitFailure
>      ksft_ge(directed, 20000, f"traffic on {name}: " + str(cnts))
>      if params.get('noise'):
>          ksft_lt(sum(cnts[i] for i in params['noise']), directed / 2,
> -                "traffic on other queues:" + str(cnts))
> +                f"traffic on other queues ({name})':" + str(cnts))
>      if params.get('empty'):
>          ksft_eq(sum(cnts[i] for i in params['empty']), 0,
> -                "traffic on inactive queues: " + str(cnts))
> +                f"traffic on inactive queues ({name}): " + str(cnts))
>  
>  
>  def test_rss_key_indir(cfg):

Reviewed-by: Joe Damato <jdamato@fastly.com>

  reply	other threads:[~2024-08-02 11:23 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-02  0:17 [PATCH net-next 00/12] ethtool: rss: driver tweaks and netlink context dumps Jakub Kicinski
2024-08-02  0:17 ` [PATCH net-next 01/12] selftests: drv-net: rss_ctx: add identifier to traffic comments Jakub Kicinski
2024-08-02 11:23   ` Joe Damato [this message]
2024-08-02  0:17 ` [PATCH net-next 02/12] eth: mvpp2: implement new RSS context API Jakub Kicinski
2024-08-02  0:17 ` [PATCH net-next 03/12] eth: mlx5: allow disabling queues when RSS contexts exist Jakub Kicinski
2024-08-02 11:27   ` Joe Damato
2024-08-02  0:17 ` [PATCH net-next 04/12] ethtool: make ethtool_ops::cap_rss_ctx_supported optional Jakub Kicinski
2024-08-02 11:35   ` Joe Damato
2024-08-02  0:17 ` [PATCH net-next 05/12] eth: remove .cap_rss_ctx_supported from updated drivers Jakub Kicinski
2024-08-02 11:41   ` Joe Damato
2024-08-02  0:17 ` [PATCH net-next 06/12] ethtool: rss: don't report key if device doesn't support it Jakub Kicinski
2024-08-02 11:58   ` Joe Damato
2024-08-02  0:17 ` [PATCH net-next 07/12] ethtool: rss: move the device op invocation out of rss_prepare_data() Jakub Kicinski
2024-08-02 13:15   ` Joe Damato
2024-08-02  0:17 ` [PATCH net-next 08/12] ethtool: rss: report info about additional contexts from XArray Jakub Kicinski
2024-08-02 13:18   ` Joe Damato
2024-08-02  0:17 ` [PATCH net-next 09/12] ethtool: rss: support dumping RSS contexts Jakub Kicinski
2024-08-02  0:17 ` [PATCH net-next 10/12] ethtool: rss: support skipping contexts during dump Jakub Kicinski
2024-08-02  0:18 ` [PATCH net-next 11/12] netlink: specs: decode indirection table as u32 array Jakub Kicinski
2024-08-02  0:18 ` [PATCH net-next 12/12] selftests: drv-net: rss_ctx: test dumping RSS contexts Jakub Kicinski

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=ZqzBvTmsmhPoLb_f@LQ3V64L9R2 \
    --to=jdamato@fastly.com \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=dxu@dxuuu.xyz \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=gal.pressman@linux.dev \
    --cc=kuba@kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=tariqt@nvidia.com \
    --cc=willemdebruijn.kernel@gmail.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