Linux filesystem development
 help / color / mirror / Atom feed
From: Bernd Schubert <bernd@bsbernd.com>
To: Gang He <dchg2000@gmail.com>
Cc: "linux-fsdevel@vger.kernel.org" <linux-fsdevel@vger.kernel.org>
Subject: Re: Fuse over io_uring mode cannot handle iodepth > 1 case properly like the default mode
Date: Thu, 18 Sep 2025 10:38:48 +0200	[thread overview]
Message-ID: <dbb91af0-ef9d-4a17-852e-ffaa1c759661@bsbernd.com> (raw)
In-Reply-To: <CAGmFzSdD71SxAxCJp5BbJZ7-JVARtoDPPScGvxhTF=+HQ+D6jw@mail.gmail.com>

[Added back fsdevel into CC]

Hi Gang,

On 9/18/25 05:05, Gang He wrote:
> Hi Bernd,
> 
> Sorry for interruption again.
> About enable fuse over io_uring feature, I can back-port the related
> kernel patch set.
> But, for user-space libfuse, when will you or the team release a
> tag(e.g. 3.18)? then I can upgrade the libfuse directly, rather than
> back-port patches.
> Second, Fuse over io_uring mode cannot handle iodepth > 1 case
> quickly, I feel this is a by-design issue, the iouring uses the own
> thread queue to handle the requests from the user space. I write a
> kernel patch, which can fix this case, but for the most cases, we
> still use the current design. the patch is attached, could you take a
> look at it, to see if this patch make sense, or not.


I will try to find time to release libfuse-3.18 today, one io-uring
related patch is missing (re-init of some fields in struct fuse_req) and
then just the release process.

Regarding queue balancing, please have a look here:

https://github.com/bsbernd/linux/commits/reduced-nr-ring-queues_3.1/


The tricky part and which is why I didn't publish v2 of this series is
to keep performance for blocking/sync requests (like DIO, metadata,
etc). At DDN we run with an additional workaround patch that disables
migration in fuse_request_end(), which results in kind of
wake_up_on_current_cpu(). Adding in wake_up_on_current_cpu() to fuse is
simple, I have the patch, problem is more that wake_up_on_current_cpu()
is not perfect. I'm just in the middle to walk through scheduler code.
For example, wake_up_on_current_cpu() gets perfect after increasing
/sys/kernel/debug/sched/migration_cost_ns
Now I don't want to change system wide migration costs, but it needs to
be time limited change when waking up from fuse. Additionally it needs
to be a hint, depending on if the queue has more pending work - that is
the part that gets even more complex with reduced queues and queue
balancing.

Also see https://lkml.org/lkml/2023/5/3/646 and related threads for
reference.

Thanks,
Bernd

  parent reply	other threads:[~2025-09-18  8:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-15  7:45 Fuse over io_uring mode cannot handle iodepth > 1 case properly like the default mode Gang He
2025-08-15 20:56 ` Bernd Schubert
2025-08-18  1:39   ` Gang He
2025-08-18 17:31     ` Bernd Schubert
2025-08-19  2:16       ` Gang He
     [not found]         ` <CAGmFzSdD71SxAxCJp5BbJZ7-JVARtoDPPScGvxhTF=+HQ+D6jw@mail.gmail.com>
2025-09-18  8:38           ` Bernd Schubert [this message]
2025-09-24 21:09             ` Bernd Schubert
2025-09-25  6:52               ` Gang He

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=dbb91af0-ef9d-4a17-852e-ffaa1c759661@bsbernd.com \
    --to=bernd@bsbernd.com \
    --cc=dchg2000@gmail.com \
    --cc=linux-fsdevel@vger.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