On 8/17/25 15:45, Stefan Hajnoczi wrote:
> On Thu, Aug 14, 2025 at 11:46:16PM -0400, Zhi Song wrote:
>> Due to kernel limitations, when the FUSE-over-io_uring option is
>> enabled,
>> you must create and assign nr_cpu IOThreads. For example:
>
> While it would be nice for the kernel to support a more flexible queue
> mapping policy, userspace can work around this.
>
> I think Kevin suggested creating the number of FUSE queues required by
> the kernel and configuring them across the user's IOThreads. That way
> the number of IOThreads can be smaller than the number of FUSE queues.
Sorry, had been another week off last week and I'm only slowly catching
up.
Regarding more flexible queues, see here
https://lore.kernel.org/r/20250722-reduced-nr-ring-queues_3-v1-0-aa8e37ae9...@ddn.com
And actually forgot to mention the corresponding libfuse branch for that:
https://github.com/bsbernd/libfuse/tree/uring-reduce-nr-queues
Bernd
