From: Shay Drori <shayd@nvidia.com>
To: Fushuai Wang <fushuai.wang@linux.dev>, <saeedm@nvidia.com>,
<leon@kernel.org>, <tariqt@nvidia.com>, <mbloch@nvidia.com>,
<andrew+netdev@lunn.ch>, <davem@davemloft.net>,
<edumazet@google.com>, <kuba@kernel.org>, <pabeni@redhat.com>,
<parav@nvidia.com>, <moshe@nvidia.com>
Cc: <netdev@vger.kernel.org>, <linux-rdma@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <wangfushuai@baidu.com>
Subject: Re: [PATCH net v3] net/mlx5: Use effective affinity mask for IRQ selection
Date: Fri, 5 Jun 2026 15:25:27 +0300 [thread overview]
Message-ID: <086e79e1-12df-418f-8be4-a53e1081fab7@nvidia.com> (raw)
In-Reply-To: <20260605102112.91772-1-fushuai.wang@linux.dev>
On 05/06/2026 13:21, Fushuai Wang wrote:
> External email: Use caution opening links or attachments
>
>
> From: Fushuai Wang <wangfushuai@baidu.com>
>
> When a sf is created after a CPU has been taken offline, the IRQ pool may
> contain IRQs with affinity masks that include the offline CPU. Since only
> online CPUs should be considered for IRQ placement, cpumask_subset() check
> would fail because the iter_mask contains offline CPUs that are not present
> in req_mask, causing sf creation to fail.
>
> This is an example:
> 1. When mlx5 driver loads, it initializes the IRQ pools.
> For sf_ctrl_pool with ≤64 sf:
> - xa_num_irqs = {N, N} (There is only one slot)
> 2. When the first SF is created:
> - The ctrl IRQ is allocated with mask=cpu_online_mask={0-191}
> 2. We take CPU 20 offline
> 3. Existing ctl irq still have mask={0-191}
> 4. Create a new SF:
> - req_mask={0-19,21-191}
> - iter_mask={0-191}
> - {0-191} is NOT a subset of {0-19,21-191}
> - least_loaded_irq=NULL
> 5. Try to allocate a new irq via irq_pool_request_irq()
> 6. xa_alloc() fails because the pool is full(There is only one slot)
> 7. sf creation fails with error
>
> Use irq_get_effective_affinity_mask() instead, which returns the IRQ's
> actual effective affinity that already excludes offline CPUs.
>
> Fixes: 061f5b23588a ("net/mlx5: SF, Use all available cpu for setting cpu affinity")
> Suggested-by: Shay Drory <shayd@nvidia.com>
Reviewed-by: Shay Drory <shayd@nvidia.com>
> Signed-off-by: Fushuai Wang <wangfushuai@baidu.com>
> ---
> v2->v3: Separate the patchset to two patches, reverse xmas tree coding style fix.
> v1->v2: Use mlx5_irq_get_affinity_mask() api
>
> previous discussion:
> https://lore.kernel.org/all/20260603072657.10868-1-fushuai.wang@linux.dev/T/#u
> https://lore.kernel.org/all/20260604125705.21241-1-fushuai.wang@linux.dev/T/#u
>
> drivers/net/ethernet/mellanox/mlx5/core/irq_affinity.c | 5 ++++-
> 1 file changed, 4 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/net/ethernet/mellanox/mlx5/core/irq_affinity.c b/drivers/net/ethernet/mellanox/mlx5/core/irq_affinity.c
> index 994fe83da4be..a0bb8ee44e35 100644
> --- a/drivers/net/ethernet/mellanox/mlx5/core/irq_affinity.c
> +++ b/drivers/net/ethernet/mellanox/mlx5/core/irq_affinity.c
> @@ -105,9 +105,12 @@ irq_pool_find_least_loaded(struct mlx5_irq_pool *pool, const struct cpumask *req
>
> lockdep_assert_held(&pool->lock);
> xa_for_each_range(&pool->irqs, index, iter, start, end) {
> - struct cpumask *iter_mask = mlx5_irq_get_affinity_mask(iter);
> int iter_refcount = mlx5_irq_read_locked(iter);
> + const struct cpumask *iter_mask;
>
> + iter_mask = irq_get_effective_affinity_mask(mlx5_irq_get_irq(iter));
> + if (!iter_mask)
> + continue;
> if (!cpumask_subset(iter_mask, req_mask))
> /* skip IRQs with a mask which is not subset of req_mask */
> continue;
> --
> 2.36.1
>
next prev parent reply other threads:[~2026-06-05 12:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-05 10:21 [PATCH net v3] net/mlx5: Use effective affinity mask for IRQ selection Fushuai Wang
2026-06-05 12:25 ` Shay Drori [this message]
2026-06-07 8:39 ` Tariq Toukan
2026-06-09 2:10 ` 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=086e79e1-12df-418f-8be4-a53e1081fab7@nvidia.com \
--to=shayd@nvidia.com \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=fushuai.wang@linux.dev \
--cc=kuba@kernel.org \
--cc=leon@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rdma@vger.kernel.org \
--cc=mbloch@nvidia.com \
--cc=moshe@nvidia.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=parav@nvidia.com \
--cc=saeedm@nvidia.com \
--cc=tariqt@nvidia.com \
--cc=wangfushuai@baidu.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