From: Frederic Weisbecker <frederic@kernel.org>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>, Kalle Valo <kvalo@codeaurora.org>,
Andrew Morton <akpm@linux-foundation.org>
Subject: Re: [PATCH 1/2] ath6kl: add WQ_PERCPU to alloc_workqueue users
Date: Thu, 5 Mar 2026 18:20:59 +0100 [thread overview]
Message-ID: <aam7e3bAFBVOUnFX@localhost.localdomain> (raw)
In-Reply-To: <CAAofZF5oAd18VV6ipoJDjiWvCeRxUh5KtdEZvPQ_DS71X_Vkzw@mail.gmail.com>
Le Thu, Mar 05, 2026 at 05:44:04PM +0100, Marco Crivellari a écrit :
> On Thu, Nov 13, 2025 at 5:12 PM Marco Crivellari
> <marco.crivellari@suse.com> wrote:
> >
> > Currently if a user enqueues 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.
> > For more details see the Link tag below.
> >
> > alloc_workqueue() treats all queues as per-CPU by default, while unbound
> > workqueues must opt-in via WQ_UNBOUND.
> >
> > This default is suboptimal: most workloads benefit from unbound queues,
> > allowing the scheduler to place worker threads where they’re needed and
> > reducing noise when CPUs are isolated.
> >
> > This continues the effort to refactor workqueue APIs, which began with
> > the introduction of new workqueues and a new alloc_workqueue flag in:
> >
> > commit 128ea9f6ccfb ("workqueue: Add system_percpu_wq and system_dfl_wq")
> > commit 930c2ea566af ("workqueue: Add new WQ_PERCPU flag")
> >
> > This change adds a new WQ_PERCPU flag to explicitly request
> > alloc_workqueue() to be per-cpu when WQ_UNBOUND has not been specified.
> >
> > With the introduction of the WQ_PERCPU flag (equivalent to !WQ_UNBOUND),
> > any alloc_workqueue() caller that doesn’t explicitly specify WQ_UNBOUND
> > must now use WQ_PERCPU.
> >
> > Once migration is complete, WQ_UNBOUND can be removed and unbound will
> > become the implicit default.
> >
> > Suggested-by: Tejun Heo <tj@kernel.org>
> > Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
> > Link: https://lore.kernel.org/all/20250221112003.1dSuoGyc@linutronix.de/
> > ---
> > drivers/net/wireless/ath/ath6kl/usb.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/net/wireless/ath/ath6kl/usb.c b/drivers/net/wireless/ath/ath6kl/usb.c
> > index 38bb501fc553..bfb21725d779 100644
> > --- a/drivers/net/wireless/ath/ath6kl/usb.c
> > +++ b/drivers/net/wireless/ath/ath6kl/usb.c
> > @@ -637,7 +637,7 @@ static struct ath6kl_usb *ath6kl_usb_create(struct usb_interface *interface)
> > ar_usb = kzalloc(sizeof(struct ath6kl_usb), GFP_KERNEL);
> > if (ar_usb == NULL)
> > return NULL;
> > - ar_usb->wq = alloc_workqueue("ath6kl_wq", 0, 0);
> > + ar_usb->wq = alloc_workqueue("ath6kl_wq", WQ_PERCPU, 0);
> > if (!ar_usb->wq) {
> > kfree(ar_usb);
> > return NULL;
>
> [ Cc-ing Andrew Morton ]
>
> Hello Andrew,
>
> This file is orphaned. Can you help me in order to have this patch merged?
>
> Thank you!
>
Reviewed-by: Frederic Weisbecker <frederic@kernel.org>
--
Frederic Weisbecker
SUSE Labs
next prev parent reply other threads:[~2026-03-05 17:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 16:12 [PATCH 0/2] add WQ_PERCPU to alloc_workqueue Marco Crivellari
2025-11-13 16:12 ` [PATCH 1/2] ath6kl: add WQ_PERCPU to alloc_workqueue users Marco Crivellari
2026-03-05 16:44 ` Marco Crivellari
2026-03-05 17:20 ` Frederic Weisbecker [this message]
2025-11-13 16:12 ` [PATCH 2/2] cw1200: " Marco Crivellari
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=aam7e3bAFBVOUnFX@localhost.localdomain \
--to=frederic@kernel.org \
--cc=akpm@linux-foundation.org \
--cc=bigeasy@linutronix.de \
--cc=jiangshanlai@gmail.com \
--cc=kvalo@codeaurora.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=tj@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.