Re: [PATCH] platform/surface: acpi-notify: add WQ_PERCPU to alloc_workqueue users

[Marco Crivellari]

On Wed, Nov 19, 2025 at 11:38 AM Ilpo Järvinen
<ilpo.jarvinen@xxxxxxxxxxxxxxx> wrote:
> [...]
> So after refactoring, WQ_UNBOUND cannot be specified as it has been
> removed AND the default behavior is "unbound", not "per-cpu", right?
> So it should be other way around, e.g.:
>
> The refactoring is going to alter the behavior of alloc_workqueue() to be
> unbound by default.

Yes, it makes sense. I changed that part.

This is the updated version:

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")

The refactoring is going to alter the default behavior of
alloc_workqueue() to be unbound by default.

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. For more details see the Link tag below.

In order to keep alloc_workqueue() behavior identical, explicitly request
WQ_PERCPU.


Thanks!


-- 

Marco Crivellari

L3 Support Engineer, Technology & Product