From: Hans de Goede <hansg@kernel.org>
To: Marco Crivellari <marco.crivellari@suse.com>,
linux-kernel@vger.kernel.org,
platform-driver-x86@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>,
Corentin Chary <corentin.chary@gmail.com>,
"Luke D . Jones" <luke@ljones.dev>,
Denis Benato <denis.benato@linux.dev>,
Ilpo Jarvinen <ilpo.jarvinen@linux.intel.com>
Subject: Re: [RFC PATCH] platform/x86: asus-tf103c-dock: Move long delayed work on system_dfl_long_wq
Date: Thu, 7 May 2026 16:42:09 +0200 [thread overview]
Message-ID: <3af8e050-9934-45ca-8e5e-1e6a69909637@kernel.org> (raw)
In-Reply-To: <20260507143953.342654-1-marco.crivellari@suse.com>
Hi,
On 7-May-26 16:39, Marco Crivellari wrote:
> Currently the code enqueue work items using {queue|mod}_delayed_work(),
> using system_long_wq. This workqueue should be used when long works are
> expected and it is a per-cpu workqueue.
>
> The function(s) end up calling __queue_delayed_work(), which set a global
> timer that could fire anywhere, enqueuing the work where the timer fired.
>
> Unbound works could benefit from scheduler task placement, to optimize
> performance and power consumption. Long work shouldn't stick to a single
> CPU.
>
> Recently, a new unbound workqueue specific for long running work has
> been added:
>
> c116737e972e ("workqueue: Add system_dfl_long_wq for long unbound works")
>
> Since the workqueue work doesn't rely on per-cpu variables, there is no
> obvious reason that justify the use of a per-cpu workqueue. So change
> system_long_wq with system_dfl_long_wq so that the work may benefit from
> scheduler task placement.
>
> Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
Thanks, patch looks good to me:
Reviewed-by: Hans de Goede <johannes.goede@oss.qualcomm.com>
Regards,
Hans
> ---
> drivers/platform/x86/asus-tf103c-dock.c | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/platform/x86/asus-tf103c-dock.c b/drivers/platform/x86/asus-tf103c-dock.c
> index f09a3fc6524a..de683e17ce01 100644
> --- a/drivers/platform/x86/asus-tf103c-dock.c
> +++ b/drivers/platform/x86/asus-tf103c-dock.c
> @@ -669,7 +669,8 @@ static irqreturn_t tf103c_dock_hpd_irq(int irq, void *data)
> {
> struct tf103c_dock_data *dock = data;
>
> - mod_delayed_work(system_long_wq, &dock->hpd_work, TF103C_DOCK_HPD_DEBOUNCE);
> + mod_delayed_work(system_dfl_long_wq, &dock->hpd_work,
> + TF103C_DOCK_HPD_DEBOUNCE);
> return IRQ_HANDLED;
> }
>
> @@ -677,7 +678,8 @@ static void tf103c_dock_start_hpd(struct tf103c_dock_data *dock)
> {
> enable_irq(dock->hpd_irq);
> /* Sync current HPD status */
> - queue_delayed_work(system_long_wq, &dock->hpd_work, TF103C_DOCK_HPD_DEBOUNCE);
> + queue_delayed_work(system_dfl_long_wq, &dock->hpd_work,
> + TF103C_DOCK_HPD_DEBOUNCE);
> }
>
> static void tf103c_dock_stop_hpd(struct tf103c_dock_data *dock)
next prev parent reply other threads:[~2026-05-07 14:42 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-07 14:39 [RFC PATCH] platform/x86: asus-tf103c-dock: Move long delayed work on system_dfl_long_wq Marco Crivellari
2026-05-07 14:42 ` Hans de Goede [this message]
2026-05-08 13:34 ` Ilpo Järvinen
2026-05-08 14:24 ` 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=3af8e050-9934-45ca-8e5e-1e6a69909637@kernel.org \
--to=hansg@kernel.org \
--cc=bigeasy@linutronix.de \
--cc=corentin.chary@gmail.com \
--cc=denis.benato@linux.dev \
--cc=frederic@kernel.org \
--cc=ilpo.jarvinen@linux.intel.com \
--cc=jiangshanlai@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=luke@ljones.dev \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=platform-driver-x86@vger.kernel.org \
--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