From: Fushuai Wang <fushuai.wang@linux.dev>
To: shayd@nvidia.com
Cc: andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com,
fushuai.wang@linux.dev, kuba@kernel.org, leon@kernel.org,
linux-kernel@vger.kernel.org, linux-rdma@vger.kernel.org,
mbloch@nvidia.com, moshe@nvidia.com, netdev@vger.kernel.org,
pabeni@redhat.com, parav@nvidia.com, saeedm@nvidia.com,
tariqt@nvidia.com, wangfushuai@baidu.com
Subject: Re: [PATCH 2/2] net/mlx5: Only consider online CPUs in affinity subset check
Date: Thu, 4 Jun 2026 20:54:42 +0800 [thread overview]
Message-ID: <20260604125442.20673-1-fushuai.wang@linux.dev> (raw)
In-Reply-To: <7018a27a-29fb-4c8e-84cf-dc90d1b3bd9c@nvidia.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=y, Size: 1692 bytes --]
> > From: Fushuai Wang <wangfushuai@baidu.com>
> >
> > When an 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.
>
> Thank for the patch!
>
> can you please provide a full example? for simplicity, lets say the SF
> pool is of size of 2 IRQs.
>
Sure, here are the AI summarized steps:
1. When mlx5 driver loads, it initializes the IRQ pools.
For sf_ctrl_pool with ≤64 SFs:
- 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
> >
> > Filter the affinity mask to only include online CPUs before checking if it's
> > a subset of the requested mask,
>
> won't this cause the affinity mask to be empty, which is kind of missing
> the point of this API... :(
Yes, I didn't realize this.
> can you check if irq_get_effective_affinity_mask() will solve the issue?
>
Yes, I tested that irq_get_effective_affinity_mask can solve the issue.
I will send a v2 shortly.
--
Regards,
WANG
prev parent reply other threads:[~2026-06-04 12:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 7:26 [PATCH 0/2] net/mlx5: Only consider online CPUs in affinity subset check Fushuai Wang
2026-06-03 7:26 ` [PATCH 1/2] net/mlx5: Simplify cpumask operations in comp_irq_request_sf() Fushuai Wang
2026-06-04 5:57 ` Shay Drori
2026-06-03 7:26 ` [PATCH 2/2] net/mlx5: Only consider online CPUs in affinity subset check Fushuai Wang
2026-06-04 5:53 ` Shay Drori
2026-06-04 12:54 ` Fushuai Wang [this message]
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=20260604125442.20673-1-fushuai.wang@linux.dev \
--to=fushuai.wang@linux.dev \
--cc=andrew+netdev@lunn.ch \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--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=shayd@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