From: Marco Crivellari <marco.crivellari@suse.com>
To: linux-kernel@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>,
Marco Crivellari <marco.crivellari@suse.com>,
Michal Hocko <mhocko@suse.com>, Al Viro <viro@zeniv.linux.org.uk>,
David Sterba <dsterba@suse.com>,
David Woodhouse <dwmw2@infradead.org>,
Eric Sandeen <sandeen@redhat.com>,
John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>,
Kees Cook <kees@kernel.org>, Miklos Szeredi <miklos@szeredi.hu>,
Richard Weinberger <richard@nod.at>,
Viacheslav Dubeyko <slava@dubeyko.com>,
Yangtao Li <frank.li@vivo.com>
Subject: [RFC PATCH 0/6] fs: Move long delayed work on system_dfl_long_wq
Date: Fri, 8 May 2026 15:45:28 +0200 [thread overview]
Message-ID: <20260508134541.282073-1-marco.crivellari@suse.com> (raw)
Hello,
Currently the code uses the per-cpu workqueue system_long_wq to schedule
long running works.
Unbound works could benefit from scheduler task placement, to optimize
performance and power consumption. Another good reason to have this unbound,
is the "queue_delayed_work()" function, used to enqueue the work item.
More details on this will follow in the next section.
Recently, a new unbound workqueue specific for long running work has been
added:
c116737e972e ("workqueue: Add system_dfl_long_wq for long unbound works")
~~~ Details about queue_delayed_work ~~~
system_long_wq is a per-cpu workqueue and it is used as a parameter of
queue_delayed_work(). This function schedule an item that it will later
be enqueued (once the timer will fire). __queue_delayed_work() does the job
receiving as "cpu" WORK_CPU_UNBOUND:
if (housekeeping_enabled(HK_TYPE_TIMER)) {
// [....]
} else {
if (likely(cpu == WORK_CPU_UNBOUND))
add_timer_global(timer);
else
add_timer_on(timer, cpu);
}
The timer is global, so can fire everywhere, and the work item will be
enqueued where the timer fired.
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 the
workqueue with the new system_dfl_long_wq, so that the used workqueue is
now unbound and can benefit from scheduler task placement.
Thanks!
Marco Crivellari (6):
ufs: Move long delayed work on system_dfl_long_wq
fs/jffs2: Move long delayed work on system_dfl_long_wq
hfsplus: Move long delayed work on system_dfl_long_wq
hfs: Move long delayed work on system_dfl_long_wq
fuse: dax: Move long delayed work on system_dfl_long_wq
affs: Move long delayed work on system_dfl_long_wq
fs/affs/super.c | 2 +-
fs/fuse/dax.c | 2 +-
fs/hfs/super.c | 2 +-
fs/hfsplus/super.c | 2 +-
fs/jffs2/wbuf.c | 2 +-
fs/ufs/super.c | 2 +-
6 files changed, 6 insertions(+), 6 deletions(-)
--
2.53.0
next reply other threads:[~2026-05-08 13:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 13:45 Marco Crivellari [this message]
2026-05-08 13:45 ` [RFC PATCH 1/6] ufs: Move long delayed work on system_dfl_long_wq Marco Crivellari
2026-05-08 13:45 ` [RFC PATCH 2/6] fs/jffs2: " Marco Crivellari
2026-05-08 13:45 ` [RFC PATCH 3/6] hfsplus: " Marco Crivellari
2026-05-08 18:34 ` Viacheslav Dubeyko
2026-05-08 13:45 ` [RFC PATCH 4/6] hfs: " Marco Crivellari
2026-05-08 18:34 ` Viacheslav Dubeyko
2026-05-08 13:45 ` [RFC PATCH 5/6] fuse: dax: " Marco Crivellari
2026-05-08 13:45 ` [RFC PATCH 6/6] affs: " 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=20260508134541.282073-1-marco.crivellari@suse.com \
--to=marco.crivellari@suse.com \
--cc=bigeasy@linutronix.de \
--cc=dsterba@suse.com \
--cc=dwmw2@infradead.org \
--cc=frank.li@vivo.com \
--cc=frederic@kernel.org \
--cc=glaubitz@physik.fu-berlin.de \
--cc=jiangshanlai@gmail.com \
--cc=kees@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mhocko@suse.com \
--cc=miklos@szeredi.hu \
--cc=richard@nod.at \
--cc=sandeen@redhat.com \
--cc=slava@dubeyko.com \
--cc=tj@kernel.org \
--cc=viro@zeniv.linux.org.uk \
/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