Re: [RFC PATCH 5/6] fuse: dax: Move long delayed work on system_dfl_long_wq

[Marco Crivellari]

On Wed, Jun 10, 2026 at 2:17 PM Miklos Szeredi <miklos@xxxxxxxxxx> wrote:
>
> On Fri, 8 May 2026 at 15:45, Marco Crivellari <marco.crivellari@xxxxxxxx> 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: Miklos Szeredi <miklos@xxxxxxxxxx>
> > Cc: linux-fsdevel@xxxxxxxxxxxxxxx
> > Signed-off-by: Marco Crivellari <marco.crivellari@xxxxxxxx>
>
> Applied, thanks.
>
> Miklos

Many thanks!

-- 

Marco Crivellari

SUSE Labs