From: Thomas Zimmermann <tzimmermann@suse.de>
To: Marco Crivellari <marco.crivellari@suse.com>,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.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>,
Maarten Lankhorst <maarten.lankhorst@linux.intel.com>,
Maxime Ripard <mripard@kernel.org>,
David Airlie <airlied@gmail.com>, Simona Vetter <simona@ffwll.ch>
Subject: Re: [PATCH 0/3] replace system_unbound_wq and system_wq with the new wqs
Date: Wed, 4 Feb 2026 12:58:40 +0100 [thread overview]
Message-ID: <a68bac38-ac0e-4ad6-8b70-72b09811a21e@suse.de> (raw)
In-Reply-To: <20251030162043.292468-1-marco.crivellari@suse.com>
Hi
Am 30.10.25 um 17:20 schrieb Marco Crivellari:
> 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_wq and system_unbound_wq
>
> system_wq is a per-CPU workqueue, but his name is not clear.
> system_unbound_wq is to be used when locality is not required.
>
> Because of that, system_wq has been replaced with system_percpu_wq, and
> system_unbound_wq has been replaced with system_dfl_wq.
From the description, I've found it hard to see if there's a change in
semantics here. But this series is effectively about renaming AFAICT. If so,
Reviewed-by: Thomas Zimmermann <tzimmermann@suse.de>
for all patches.
Best regards
Thomas
>
> Thanks!
>
>
> Marco Crivellari (3):
> drm/atomic-helper: replace use of system_unbound_wq with system_dfl_wq
> drm/probe-helper: replace use of system_wq with system_percpu_wq
> drm/self_refresh: replace use of system_wq with system_percpu_wq
>
> drivers/gpu/drm/drm_atomic_helper.c | 6 +++---
> drivers/gpu/drm/drm_probe_helper.c | 2 +-
> drivers/gpu/drm/drm_self_refresh_helper.c | 2 +-
> 3 files changed, 5 insertions(+), 5 deletions(-)
>
--
--
Thomas Zimmermann
Graphics Driver Developer
SUSE Software Solutions Germany GmbH
Frankenstr. 146, 90461 Nürnberg, Germany, www.suse.com
GF: Jochen Jaser, Andrew McDonald, Werner Knoblich, (HRB 36809, AG Nürnberg)
next prev parent reply other threads:[~2026-02-04 11:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-30 16:20 Marco Crivellari
2025-10-30 16:20 ` [PATCH 1/3] drm/atomic-helper: replace use of system_unbound_wq with system_dfl_wq Marco Crivellari
2025-10-30 16:20 ` [PATCH 2/3] drm/probe-helper: replace use of system_wq with system_percpu_wq Marco Crivellari
2025-10-30 16:20 ` [PATCH 3/3] drm/self_refresh: " Marco Crivellari
2025-12-02 13:21 ` [PATCH 0/3] replace system_unbound_wq and system_wq with the new wqs Marco Crivellari
2026-02-04 10:58 ` Marco Crivellari
2026-02-04 11:58 ` Thomas Zimmermann [this message]
2026-02-04 13:36 ` Marco Crivellari
2026-02-05 7:22 ` Thomas Zimmermann
2026-02-05 9:01 ` 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=a68bac38-ac0e-4ad6-8b70-72b09811a21e@suse.de \
--to=tzimmermann@suse.de \
--cc=airlied@gmail.com \
--cc=bigeasy@linutronix.de \
--cc=dri-devel@lists.freedesktop.org \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@linux.intel.com \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=mripard@kernel.org \
--cc=simona@ffwll.ch \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®