From: Fushuai Wang <fushuai.wang@linux.dev>
To: 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,
shayd@nvidia.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: [PATCH 0/2] net/mlx5: Only consider online CPUs in affinity subset check
Date: Wed, 3 Jun 2026 15:26:55 +0800 [thread overview]
Message-ID: <20260603072657.10868-1-fushuai.wang@linux.dev> (raw)
From: Fushuai Wang <wangfushuai@baidu.com>
Hi all,
When an SF is created after a CPU has been taken offline, the IRQ affinity
check fails because existing IRQs in the pool may have affinity masks that
include the now-offline CPU. This causes SF creation to fail even though
suitable online CPUs are available.
This series fixes this issue and includes a small cleanup:
Patch 1 folds cpumask_copy() into cpumask_andnot() for better code clarity
in comp_irq_request_sf().
Patch 2 filters affinity masks to only consider online CPUs before the subset
check, ensuring SF creation succeeds when CPUs have been taken offline.
--WANG
Fushuai Wang (2):
net/mlx5: Simplify cpumask operations in comp_irq_request_sf()
net/mlx5: Only consider online CPUs in affinity subset check
drivers/net/ethernet/mellanox/mlx5/core/eq.c | 3 +--
.../net/ethernet/mellanox/mlx5/core/irq_affinity.c | 14 ++++++++++++--
2 files changed, 13 insertions(+), 4 deletions(-)
--
2.36.1
next reply other threads:[~2026-06-03 7:28 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-06-03 7:26 Fushuai Wang [this message]
2026-06-03 7:26 ` [PATCH 1/2] net/mlx5: Simplify cpumask operations in comp_irq_request_sf() Fushuai Wang
2026-06-03 7:26 ` [PATCH 2/2] net/mlx5: Only consider online CPUs in affinity subset check Fushuai Wang
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=20260603072657.10868-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