From: Viacheslav Dubeyko <vdubeyko@redhat.com>
To: Marco Crivellari <marco.crivellari@suse.com>,
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>,
Michal Hocko <mhocko@suse.com>,
Viacheslav Dubeyko <slava@dubeyko.com>,
Yangtao Li <frank.li@vivo.com>,
linux-fsdevel@vger.kernel.org
Subject: Re: [RFC PATCH 4/6] hfs: Move long delayed work on system_dfl_long_wq
Date: Fri, 08 May 2026 11:34:59 -0700 [thread overview]
Message-ID: <fb80f5422bfddf6397bc2db660ca0849f67c42d5.camel@redhat.com> (raw)
In-Reply-To: <20260508134541.282073-5-marco.crivellari@suse.com>
On Fri, 2026-05-08 at 15:45 +0200, 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.
>
> Cc: Viacheslav Dubeyko <slava@dubeyko.com>
> Cc: John Paul Adrian Glaubitz
> Cc: Yangtao Li <frank.li@vivo.com>
> Cc: linux-fsdevel@vger.kernel.org
> Signed-off-by: Marco Crivellari <marco.crivellari@suse.com>
> ---
> fs/hfs/super.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/fs/hfs/super.c b/fs/hfs/super.c
> index a4f2a2bfa6d3..cf4e7a6112e7 100644
> --- a/fs/hfs/super.c
> +++ b/fs/hfs/super.c
> @@ -82,7 +82,7 @@ void hfs_mark_mdb_dirty(struct super_block *sb)
> spin_lock(&sbi->work_lock);
> if (!sbi->work_queued) {
> delay = msecs_to_jiffies(dirty_writeback_interval * 10);
> - queue_delayed_work(system_long_wq, &sbi->mdb_work, delay);
> + queue_delayed_work(system_dfl_long_wq, &sbi->mdb_work, delay);
> sbi->work_queued = 1;
> }
> spin_unlock(&sbi->work_lock);
Looks good.
Reviewed-by: Viacheslav Dubeyko <slava@dubeyko.com>
Thanks,
Slava.
next prev parent reply other threads:[~2026-05-08 18:35 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-08 13:45 [RFC PATCH 0/6] fs: Move long delayed work on system_dfl_long_wq Marco Crivellari
2026-05-08 13:45 ` [RFC PATCH 1/6] ufs: " 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 [this message]
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=fb80f5422bfddf6397bc2db660ca0849f67c42d5.camel@redhat.com \
--to=vdubeyko@redhat.com \
--cc=bigeasy@linutronix.de \
--cc=frank.li@vivo.com \
--cc=frederic@kernel.org \
--cc=jiangshanlai@gmail.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marco.crivellari@suse.com \
--cc=mhocko@suse.com \
--cc=slava@dubeyko.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox