[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-ID: <20241007214408.501013-1-anthony.l.nguyen@intel.com>
Date: Mon, 7 Oct 2024 14:44:07 -0700
From: Tony Nguyen <anthony.l.nguyen@...el.com>
To: intel-wired-lan@...ts.osuosl.org
Cc: Frederic Weisbecker <frederic@...nel.org>,
przemyslaw.kitszel@...el.com,
larysa.zaremba@...el.com,
netdev@...r.kernel.org,
linux-kernel@...r.kernel.org
Subject: [RESEND PATCH iwl-next] ice: Unbind the workqueue
From: Frederic Weisbecker <frederic@...nel.org>
The ice workqueue doesn't seem to rely on any CPU locality and should
therefore be able to run on any CPU. In practice this is already
happening through the unbound ice_service_timer that may fire anywhere
and queue the workqueue accordingly to any CPU.
Make this official so that the ice workqueue is only ever queued to
housekeeping CPUs on nohz_full.
Signed-off-by: Frederic Weisbecker <frederic@...nel.org>
---
Resend of: https://lore.kernel.org/all/20240922222420.18009-1-frederic@kernel.org/
- Added IWL and netdev lists
drivers/net/ethernet/intel/ice/ice_main.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/net/ethernet/intel/ice/ice_main.c b/drivers/net/ethernet/intel/ice/ice_main.c
index 179631921611..b819e7f9d97d 100644
--- a/drivers/net/ethernet/intel/ice/ice_main.c
+++ b/drivers/net/ethernet/intel/ice/ice_main.c
@@ -5904,7 +5904,7 @@ static int __init ice_module_init(void)
ice_adv_lnk_speed_maps_init();
- ice_wq = alloc_workqueue("%s", 0, 0, KBUILD_MODNAME);
+ ice_wq = alloc_workqueue("%s", WQ_UNBOUND, 0, KBUILD_MODNAME);
if (!ice_wq) {
pr_err("Failed to create workqueue\n");
return status;
--
2.42.0
Powered by blists - more mailing lists