From: Tejun Heo <tj@kernel.org>
To: Marco Crivellari <marco.crivellari@suse.com>
Cc: linux-kernel@vger.kernel.org,
Lai Jiangshan <jiangshanlai@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>
Subject: Re: [PATCH 3/3] workqueue: WQ_PERCPU added to alloc_workqueue users
Date: Fri, 5 Sep 2025 07:25:24 -1000 [thread overview]
Message-ID: <aLsdBIY01140Vyy_@slm.duckdns.org> (raw)
In-Reply-To: <20250905091325.112168-4-marco.crivellari@suse.com>
Hello,
The patch doesn't apply to wq/for-6.18 and...
> diff --git a/kernel/workqueue.c b/kernel/workqueue.c
> index 89839eebb359..d33ca6acc5a5 100644
> --- a/kernel/workqueue.c
> +++ b/kernel/workqueue.c
> @@ -7819,22 +7819,23 @@ void __init workqueue_init_early(void)
> ordered_wq_attrs[i] = attrs;
> }
>
> - system_wq = alloc_workqueue("events", 0, 0);
> - system_percpu_wq = alloc_workqueue("events", 0, 0);
> - system_highpri_wq = alloc_workqueue("events_highpri", WQ_HIGHPRI, 0);
> - system_long_wq = alloc_workqueue("events_long", 0, 0);
> + system_wq = alloc_workqueue("events", WQ_PERCPU, 0);
> + system_percpu_wq = alloc_workqueue("events", WQ_PERCPU, 0);
> + system_highpri_wq = alloc_workqueue("events_highpri",
> + WQ_HIGHPRI | WQ_PERCPU, 0);
> + system_long_wq = alloc_workqueue("events_long", WQ_PERCPU, 0);
> system_unbound_wq = alloc_workqueue("events_unbound", WQ_UNBOUND, WQ_MAX_ACTIVE);
> system_dfl_wq = alloc_workqueue("events_unbound", WQ_UNBOUND, WQ_MAX_ACTIVE);
> system_freezable_wq = alloc_workqueue("events_freezable",
> - WQ_FREEZABLE, 0);
> + WQ_FREEZABLE | WQ_PERCPU, 0);
> system_power_efficient_wq = alloc_workqueue("events_power_efficient",
> WQ_POWER_EFFICIENT, 0);
> system_freezable_power_efficient_wq = alloc_workqueue("events_freezable_pwr_efficient",
> - WQ_FREEZABLE | WQ_POWER_EFFICIENT,
> - 0);
> - system_bh_wq = alloc_workqueue("events_bh", WQ_BH, 0);
> + WQ_FREEZABLE | WQ_POWER_EFFICIENT, 0);
Isn't this missing WQ_PERCPU for system_freezable_power_efficient_wq?
Thanks.
--
tejun
next prev parent reply other threads:[~2025-09-05 17:25 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-05 9:13 [PATCH 0/3] workqueue: replace wq users and add WQ_PERCPU to alloc_workqueue() users Marco Crivellari
2025-09-05 9:13 ` [PATCH 1/3] workqueue: replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
2025-09-05 9:13 ` [PATCH 2/3] workqueue: replace use of system_wq with system_percpu_wq Marco Crivellari
2025-09-05 17:24 ` Tejun Heo
2025-09-09 10:25 ` Marco Crivellari
2025-09-05 9:13 ` [PATCH 3/3] workqueue: WQ_PERCPU added to alloc_workqueue users Marco Crivellari
2025-09-05 17:25 ` Tejun Heo [this message]
2025-09-08 12:25 ` Marco Crivellari
2025-09-08 13:11 ` 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=aLsdBIY01140Vyy_@slm.duckdns.org \
--to=tj@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.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