From: Stefan Hajnoczi <stefanha@redhat.com>
To: Zhi Song <hibriansong@gmail.com>
Cc: qemu-block@nongnu.org, qemu-devel@nongnu.org, armbru@redhat.com,
bernd@bsbernd.com, fam@euphon.net, hreitz@redhat.com,
kwolf@redhat.com
Subject: Re: [RFC PATCH 0/3] block/export: Add FUSE-over-io_uring for Storage Exports
Date: Sun, 17 Aug 2025 09:45:27 -0400 [thread overview]
Message-ID: <20250817134527.GA321129@fedora> (raw)
In-Reply-To: <20250815034619.51980-1-hizhisong@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 537 bytes --]
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.
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-08-17 13:46 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-15 3:46 [RFC PATCH 0/3] block/export: Add FUSE-over-io_uring for Storage Exports Zhi Song
2025-08-15 3:46 ` [PATCH 1/3] fuse: add FUSE-over-io_uring enable opt and init Zhi Song
2025-08-16 23:13 ` Brian Song
2025-08-17 13:42 ` Stefan Hajnoczi
2025-08-18 23:04 ` Bernd Schubert
2025-08-19 1:15 ` Brian Song
2025-08-19 22:26 ` Bernd Schubert
2025-08-19 23:23 ` Brian Song
2025-08-20 3:31 ` Brian Song
2025-08-15 3:46 ` [PATCH 2/3] fuse: Handle FUSE-uring requests Zhi Song
2025-08-15 3:46 ` [PATCH 3/3] fuse: Safe termination for FUSE-uring Zhi Song
2025-08-17 13:45 ` Stefan Hajnoczi [this message]
2025-08-18 22:54 ` [RFC PATCH 0/3] block/export: Add FUSE-over-io_uring for Storage Exports Bernd Schubert
2025-08-21 1:32 ` Brian Song
2025-08-21 14:20 ` Stefan Hajnoczi
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=20250817134527.GA321129@fedora \
--to=stefanha@redhat.com \
--cc=armbru@redhat.com \
--cc=bernd@bsbernd.com \
--cc=fam@euphon.net \
--cc=hibriansong@gmail.com \
--cc=hreitz@redhat.com \
--cc=kwolf@redhat.com \
--cc=qemu-block@nongnu.org \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).