Re: [PATCH RFC v1] ksmbd: add use_unbound_wq module parameter for the ksmbd-io workqueue
From: Namjae Jeon
Date: Mon Nov 16 2026 - 07:10:37 EST
On Mon, Nov 16, 2026 at 4:49 PM Stefan Chulski
<stefan.chulski@xxxxxxxxxxxx> wrote:
>
> The "ksmbd-io" workqueue has always been per-CPU. Commit 69635d7f4b34
> ("fs: WQ_PERCPU added to alloc_workqueue users") only made that
> default explicit as part of the treewide transition to unbound-by-default;
> it was not a ksmbd-specific decision.
>
> Per-CPU work keeps request processing on the CPU that queued it, which
> is good for cache locality, but it also runs work on CPUs that were
> isolated from workqueue noise (isolcpus=, nohz_full=) and prevents the
> scheduler from placing blocked or long-running workers elsewhere.
> Which behaviour is better depends on the workload and platform.
>
> Add a boolean use_unbound_wq module parameter. It defaults to false, so
> behaviour is unchanged unless it is set; when true, "ksmbd-io" is
> allocated with WQ_UNBOUND instead of WQ_PERCPU. The "ksmbd-break"
> workqueue is already WQ_UNBOUND and is not affected.
>
> Document the parameter in ksmbd.rst.
>
> Signed-off-by: Stefan Chulski <stefan.chulski@xxxxxxxxxxxx>
Hi Stefan,
Do you have numbers comparing the per-CPU and unbound queues,
How does this compare with the earlier following RFC ?
https://lore.kernel.org/linux-cifs/20261022092514.2590010-1-huiwen.he@xxxxxxxxx/
Thanks.