All of lore.kernel.org
 help / color / mirror / Atom feed
From: Petr Machata <petrm@nvidia.com>
To: Jakub Kicinski <kuba@kernel.org>
Cc: <davem@davemloft.net>, <netdev@vger.kernel.org>,
	<edumazet@google.com>, <pabeni@redhat.com>,
	<michael.chan@broadcom.com>, <shuah@kernel.org>,
	<ecree.xilinx@gmail.com>, <przemyslaw.kitszel@intel.com>,
	<ahmed.zaki@intel.com>, <andrew@lunn.ch>, <willemb@google.com>,
	<pavan.chebbi@broadcom.com>, <petrm@nvidia.com>, <gal@nvidia.com>,
	<jdamato@fastly.com>, <donald.hunter@gmail.com>
Subject: Re: [PATCH net-next v3 12/12] selftests: drv-net: rss_ctx: test dumping RSS contexts
Date: Thu, 8 Aug 2024 12:05:57 +0200	[thread overview]
Message-ID: <87sevfmipy.fsf@nvidia.com> (raw)
In-Reply-To: <20240806193317.1491822-13-kuba@kernel.org>


Jakub Kicinski <kuba@kernel.org> writes:

> Add a test for dumping RSS contexts. Make sure indir table
> and key are sane when contexts are created with various
> combination of inputs. Test the dump filtering by ifname
> and start-context.
>
> Signed-off-by: Jakub Kicinski <kuba@kernel.org>

Reviewed-by: Petr Machata <petrm@nvidia.com>

  reply	other threads:[~2024-08-08 10:07 UTC|newest]

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

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=87sevfmipy.fsf@nvidia.com \
    --to=petrm@nvidia.com \
    --cc=ahmed.zaki@intel.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=donald.hunter@gmail.com \
    --cc=ecree.xilinx@gmail.com \
    --cc=edumazet@google.com \
    --cc=gal@nvidia.com \
    --cc=jdamato@fastly.com \
    --cc=kuba@kernel.org \
    --cc=michael.chan@broadcom.com \
    --cc=netdev@vger.kernel.org \
    --cc=pabeni@redhat.com \
    --cc=pavan.chebbi@broadcom.com \
    --cc=przemyslaw.kitszel@intel.com \
    --cc=shuah@kernel.org \
    --cc=willemb@google.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.