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: Wed, 24 Sep 2025 23:09:20 +0200	[thread overview]
Message-ID: <fb7bc595-bbc6-42b0-a16c-acc79f59cbee@bsbernd.com> (raw)
In-Reply-To: <dbb91af0-ef9d-4a17-852e-ffaa1c759661@bsbernd.com>



On 9/18/25 10:38, Bernd Schubert wrote:
> [Added back fsdevel into CC]
> 

I'm getting there, upcoming patch as part of the queue reduction series:

fuse: {io-uring} Queue background requests on a different core

Running background IO on a different core makes quite a difference.

fio --directory=/tmp/dest --name=iops.\$jobnum --rw=randread \
--bs=4k --size=1G --numjobs=1 --iodepth=4 --time_based\
--runtime=30s --group_reporting --ioengine=io_uring\
 --direct=1

unpatched
   READ: bw=272MiB/s (285MB/s), 272MiB/s-272MiB/s (285MB/s-285MB/s) ...

patched
Run status group 0 (all jobs):
   READ: bw=674MiB/s (707MB/s), 674MiB/s-674MiB/s (707MB/s-707MB/s) ...


fuse-over-io-uring RFC v1 and v2 versions had

https://lore.kernel.org/all/20240529-fuse-uring-for-6-9-rfc2-out-v1-17-d149476b1d65@ddn.com/

I dropped it on request as was an optimization hack. I had
planned to add it back earlier, but was totally occupied
from January to beginning of September...



Thanks,
Bernd

  reply	other threads:[~2025-09-24 21:09 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
2025-09-24 21:09             ` Bernd Schubert [this message]
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=fb7bc595-bbc6-42b0-a16c-acc79f59cbee@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