From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail-wr1-f50.google.com (mail-wr1-f50.google.com [209.85.221.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C86C8264617 for ; Tue, 10 Feb 2026 14:33:51 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=209.85.221.50 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770734033; cv=none; b=C5PbeBWbzvfwrwdB3SAh2jrUrFhU5NGXivZujWSdWdFojfEJjoI4G1cZPF4rdIkaRvzCXmQ43phV9gc+wql7l0uwdLa1wtWoCklcecqKPHDd1hNSYN7cgB8QlIvPG1i9AQLAwjity+/g/8G/t4OIjCfZLs7ujY72XagvI0EMhHs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1770734033; c=relaxed/simple; bh=wcCQQZgfUf8/LYbgv3mZy6Plfj0gLATysGwplnqs62k=; h=From:To:Cc:Subject:Date:Message-ID:MIME-Version; b=PUo0VEDiHyP838xjDlnTNzkxFlnY1aqDchRoE/oi6KWZ1sSDuHUx1WjSQ1GMslvZNPJeRrH4om2Ya5laH8ZNiSuFEbFMDAL1foU9gqUT88naZhizU4CkpOrGZfC4qf1N5ZSif9Om87qiyUKT+CH6AFaK9rEbwOlSGJygfGDAWnQ= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=suse.com; spf=pass smtp.mailfrom=suse.com; dkim=pass (2048-bit key) header.d=suse.com header.i=@suse.com header.b=Xsrlyv/J; arc=none smtp.client-ip=209.85.221.50 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=quarantine dis=none) header.from=suse.com Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=suse.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=suse.com header.i=@suse.com header.b="Xsrlyv/J" Received: by mail-wr1-f50.google.com with SMTP id ffacd0b85a97d-4359228b7c6so2749788f8f.2 for ; Tue, 10 Feb 2026 06:33:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=suse.com; s=google; t=1770734029; x=1771338829; darn=vger.kernel.org; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:from:to:cc:subject:date:message-id:reply-to; bh=5kplIjn4dF3J0IHV7D4b8N2dtG1YTdjm/lTb/P7a40E=; b=Xsrlyv/JtjQC6ikeZkmjx6tCjyJ/QZ+/E1FPDpYPAQjlH33sbpcRh0CLxyxg/I5Xsw LP9lTKv/8mM0jcT7v4hYByWBU71WaCX7N5+6HaT52YGjFn13I43k3MJq18KvM6aht7G+ 88MbmgaxMHzk+75/cUJObwGjiRmVZxm5hqPN3mp7LAhZdtUpPX9bqJMUf8enq2hpSWKe s4KzYGPhd8IYaC22/P09My+HejuedDxQD6UCCZovatBAVCy6MnOMedlTwUL41RUnnBmq QGbrmhyOZHlHaseojm1Rg7vUCWkTTukleFqOsgf9gvj1K3DJDVYmIPbPUdsReYCi03x7 ZK6Q== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1770734029; x=1771338829; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-gg:x-gm-message-state:from:to:cc:subject:date :message-id:reply-to; bh=5kplIjn4dF3J0IHV7D4b8N2dtG1YTdjm/lTb/P7a40E=; b=F6c2nM8gPsXJrfbEAI4e2p38Xc3ll1fa7yCkjA/Y3pujKCq0q35UxFr2K7Ah8ZFsmI taBbiNFtq3jr9Rc7mfx209cntGIUd/CoAUKllejXgwuTPi8l30sM2M3swrWwsSwf5ULj bGjhd/G9ls1KW0xnj82oSW7shOO/BpDE6YvcO95TzdNjIKqGzok3AxpzYOkZ32Wdhrrn knyfL9KpFEtVbT6e2lYwlOGRkgFYB6If2htO4s+b/NlEU8XqROQs96E2tEahk/qgpJFA S4nx8kK2bk3e1kwbloJ98ZHxEtgsCxaXe3U5smul2k08GPOIRlWAdzyi7xeXPXjxNFSO Vxsg== X-Gm-Message-State: AOJu0YyX40QQhW0u339+wViiZ7e69aBKv63OAJMSlBMPSGtEMF8ASMju vCXMy5gFVbA6XJl1kyrQVV8/68eGFAc1OzbrpVl2TGr4T5g4ejzYKo/CQuAQXZ03SQ92nMTZy+d e3pj+ X-Gm-Gg: AZuq6aKGdn2HMCpSy+K7Qv42MmqMHxaHYzeB+Lql+xBJ1MbahmhPANple8kYEnQytGU G4fdx9hvzdFlufmkInx4tcB3X8K79PJjDHEUURH41UiS4SW383syqU5NEU2JnleWL9Wwg9wFI+f XVACeG0m3UB5dENecKIWNForFMqqB2NhHqx9+LB7f8rgdPVLTfHnPgfaoX6pDe8zTNS5OrvdGZL MZQ0/QbG7EWFUTXQkCcwcN3myxA/2er/8YyKqFW99A10BS9X2xt29D31Ox62VghLYxslOxn46W5 JFdOjNtaBaGPEEjASliu35s5yYj7brEKxhxt2DdULDbIrwBewCR9e9ldubGwS4LXmdujrYORwb6 +Q+XTq+TV1u4HldGZHy8M4S3UTOxvY3Rxoanlz+lZds7S+E/5D8A8H/cCzpxZ12bqDcA4OE/vqW KBndGS3iZtCjfx6nOcpc6HW0vY X-Received: by 2002:a05:6000:2dca:b0:437:673f:e069 with SMTP id ffacd0b85a97d-437673fe2ecmr14263570f8f.59.1770734029528; Tue, 10 Feb 2026 06:33:49 -0800 (PST) Received: from linux ([2a00:6d43:105:c401:e307:1a37:2e76:ce91]) by smtp.gmail.com with ESMTPSA id ffacd0b85a97d-4376d3a32basm18265323f8f.14.2026.02.10.06.33.48 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 10 Feb 2026 06:33:49 -0800 (PST) From: Marco Crivellari To: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org Cc: Tejun Heo , Lai Jiangshan , Frederic Weisbecker , Sebastian Andrzej Siewior , Marco Crivellari , Michal Hocko , Miri Korenblit , Johannes Berg Subject: [PATCH v3 0/3] Replace uses of system_wq and system_unbound_wq Date: Tue, 10 Feb 2026 15:33:29 +0100 Message-ID: <20260210143332.206146-1-marco.crivellari@suse.com> X-Mailer: git-send-email 2.52.0 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Transfer-Encoding: 8bit Hi, === Current situation: problems === Let's consider a nohz_full system with isolated CPUs: wq_unbound_cpumask is set to the housekeeping CPUs, for !WQ_UNBOUND the local CPU is selected. This leads to different scenarios if a work item is scheduled on an isolated CPU where "delay" value is 0 or greater then 0: schedule_delayed_work(, 0); This will be handled by __queue_work() that will queue the work item on the current local (isolated) CPU, while: schedule_delayed_work(, 1); Will move the timer on an housekeeping CPU, and schedule the work there. Currently if a user enqueue a work item using schedule_delayed_work() the used wq is "system_wq" (per-cpu wq) while queue_delayed_work() use WORK_CPU_UNBOUND (used when a cpu is not specified). The same applies to schedule_work() that is using system_wq and queue_work(), that makes use again of WORK_CPU_UNBOUND. This lack of consistency cannot be addressed without refactoring the API. === Recent changes to the WQ API === The following, address the recent changes in the Workqueue API: - commit 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq") - commit 930c2ea566af ("workqueue: Add new WQ_PERCPU flag") The old workqueues will be removed in a future release cycle. === Introduced Changes by this series === 1) [P 1-2-3] Replace uses of system_unbound_wq and system_wq Switch to using system_dfl_wq and system_percpu_wq because system_unbound_wq and system_wq are going away as part of a workqueue restructuring. No intended behavior changes: system_wq -> system_percpu_wq Thanks! --- Changes in v3: - fix nvm -> mvm in patch 3 subject - rebased on v6.19 Changes in v2: - improved commit logs - P3: wrong commit log was about system_unbound_wq; subject changed with system_wq. Marco Crivellari (3): wifi: iwlwifi: replace use of system_unbound_wq with system_dfl_wq wifi: iwlwifi: fw: replace use of system_unbound_wq with system_dfl_wq wifi: iwlwifi: mvm: replace use of system_wq with system_percpu_wq drivers/net/wireless/intel/iwlwifi/fw/dbg.c | 4 ++-- drivers/net/wireless/intel/iwlwifi/iwl-trans.h | 2 +- drivers/net/wireless/intel/iwlwifi/mvm/tdls.c | 6 +++--- 3 files changed, 6 insertions(+), 6 deletions(-) -- 2.52.0