Linux RDMA and InfiniBand development
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Tariq Toukan" <tariqt@nvidia.com>
Cc: linux-rdma@vger.kernel.org
Subject: Re: [PATCH net-next 3/5] net/mlx5e: resize non-default RSS indirection tables on channel change
Date: Fri, 30 Oct 2026 04:53:51 +0000	[thread overview]
Message-ID: <sashiko-outbox-18387@kernel.org> (raw)
In-Reply-To: <20260511172719.330490-4-tariqt@nvidia.com>

> From: Yael Chemla <ychemla@nvidia.com>
> 
> When the channel count changes and the RQT size changes with it, a
> problem arise for non-default RSS contexts. The driver-side indirection
> table grows actual_table_size without filling the new entries; stale
> entries from a prior larger configuration may be re-exposed, causing
> mlx5e_calc_indir_rqns() to WARN on an out-of-range index.
> 
> Replace mlx5e_rss_params_indir_modify_actual_size() with
> mlx5e_rss_ctx_resize(), which fills new entries by replicating
> the existing pattern, matching what ethtool_rxfh_ctxs_resize() does
> for the same case. And restrict the loop to non-default contexts.
> 
> Call ethtool_rxfh_ctxs_can_resize() before acquiring state_lock to
> validate that all non-default contexts can be resized, and
> ethtool_rxfh_ctxs_resize() after releasing it to fold or unfold their
> indirection tables. Both functions acquire rss_lock internally and
> cannot be called under state_lock. RTNL, held by all set_channels
> callers, serialises context creation and deletion making the pre-lock
> check safe.
> 
> Guard both ethtool calls on mlx5e_rx_res_rss_cnt() > 1: skip the
> validation and resize when no non-default contexts exist. This
> naturally covers representors and IPoIB, which share
> mlx5e_ethtool_set_channels() but cannot have non-default RSS contexts.
> 
> Signed-off-by: Yael Chemla <ychemla@nvidia.com>
> Reviewed-by: Nimrod Oren <noren@nvidia.com>
> Signed-off-by: Tariq Toukan <tariqt@nvidia.com>

Sashiko has reviewed this patch and found no issues.

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20260511172719.330490-1-tariqt@nvidia.com?part=3


  reply	other threads:[~2026-10-30  4:53 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-05-11 17:27 [PATCH net-next 0/5] net/mlx5e: improve RSS indirection table sizing and resizing Tariq Toukan
2026-05-11 17:27 ` [PATCH net-next 1/5] net/mlx5e: remove channel count limit for XOR8 RSS hash Tariq Toukan
2026-10-30  4:53   ` sashiko-bot
2026-05-11 17:27 ` [PATCH net-next 2/5] net/mlx5e: advertise max RSS indirection table size to ethtool Tariq Toukan
2026-05-11 17:27 ` [PATCH net-next 3/5] net/mlx5e: resize non-default RSS indirection tables on channel change Tariq Toukan
2026-10-30  4:53   ` sashiko-bot [this message]
2026-05-11 17:27 ` [PATCH net-next 4/5] net/mlx5e: resize configured default RSS context table " Tariq Toukan
2026-10-30  4:53   ` sashiko-bot
2026-05-11 17:27 ` [PATCH net-next 5/5] net/mlx5e: increase RSS indirection table spread factor Tariq Toukan
2026-05-14  2:20 ` [PATCH net-next 0/5] net/mlx5e: improve RSS indirection table sizing and resizing 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=sashiko-outbox-18387@kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=linux-rdma@vger.kernel.org \
    --cc=sashiko-reviews@lists.linux.dev \
    --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