From: Mete Durlu <meted@linux.ibm.com>
To: Marco Crivellari <marco.crivellari@suse.com>,
linux-kernel@vger.kernel.org, linux-s390@vger.kernel.org
Cc: Tejun Heo <tj@kernel.org>, Lai Jiangshan <jiangshanlai@gmail.com>,
Frederic Weisbecker <frederic@kernel.org>,
Sebastian Andrzej Siewior <bigeasy@linutronix.de>,
Michal Hocko <mhocko@suse.com>,
Alexander Gordeev <agordeev@linux.ibm.com>,
Vasily Gorbik <gor@linux.ibm.com>,
Heiko Carstens <hca@linux.ibm.com>
Subject: Re: [PATCH v2 3/3] s390: replace use of system_wq with system_dfl_wq
Date: Wed, 24 Sep 2025 10:05:26 +0200 [thread overview]
Message-ID: <72d10c3f-c036-4813-a256-9d7adba4bfec@linux.ibm.com> (raw)
In-Reply-To: <20250917153859.363593-4-marco.crivellari@suse.com>
On 9/17/25 5:38 PM, Marco Crivellari wrote:
> 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 consistentcy cannot be addressed without refactoring the API.
>
> system_wq is a per-CPU worqueue (replaced by system_percpu_wq), but the
> current code does not benefit from it. Because of that, system_wq has been
> replaced by system_dfl_wq, the new unbound workqueue.
That sounds right. Thanks!
> The old wq will be kept for a few release cylces.
>
> Suggested-by: Tejun Heo <tj@kernel.org>
> Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
> ---
> arch/s390/kernel/hiperdispatch.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/arch/s390/kernel/hiperdispatch.c b/arch/s390/kernel/hiperdispatch.c
> index e7b66d046e8d..2507bc3f7757 100644
> --- a/arch/s390/kernel/hiperdispatch.c
> +++ b/arch/s390/kernel/hiperdispatch.c
> @@ -191,7 +191,7 @@ int hd_enable_hiperdispatch(void)
> return 0;
> if (hd_online_cores <= hd_entitled_cores)
> return 0;
> - mod_delayed_work(system_wq, &hd_capacity_work, HD_DELAY_INTERVAL * hd_delay_factor);
> + mod_delayed_work(system_dfl_wq, &hd_capacity_work, HD_DELAY_INTERVAL * hd_delay_factor);
> hd_update_capacities();
> return 1;
> }
Thank you for making the change from *_percpu_wq to *_dfl_wq.
I am not sure if its too late but you can have my r-b
Reviewed-by: Mete Durlu <meted@linux.ibm.com>
next prev parent reply other threads:[~2025-09-24 8:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-17 15:38 [PATCH v2 0/3] s390: replace wq users and add WQ_PERCPU to alloc_workqueue() users Marco Crivellari
2025-09-17 15:38 ` [PATCH v2 1/3] drivers/s390: WQ_PERCPU added to alloc_workqueue users Marco Crivellari
2025-09-17 15:38 ` [PATCH v2 2/3] s390/diag324: replace use of system_wq with system_percpu_wq Marco Crivellari
2025-09-17 15:38 ` [PATCH v2 3/3] s390: replace use of system_wq with system_dfl_wq Marco Crivellari
2025-09-24 8:05 ` Mete Durlu [this message]
2025-09-24 8:11 ` Marco Crivellari
2025-09-24 9:03 ` [PATCH v2 0/3] s390: replace wq users and add WQ_PERCPU to alloc_workqueue() users Heiko Carstens
2025-09-24 9:05 ` 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=72d10c3f-c036-4813-a256-9d7adba4bfec@linux.ibm.com \
--to=meted@linux.ibm.com \
--cc=agordeev@linux.ibm.com \
--cc=bigeasy@linutronix.de \
--cc=frederic@kernel.org \
--cc=gor@linux.ibm.com \
--cc=hca@linux.ibm.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-s390@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.