From: Stefan Hajnoczi <stefanha@redhat.com>
To: Brian 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: [PATCH 4/4] iotests: add tests for FUSE-over-io_uring
Date: Tue, 9 Sep 2025 15:38:30 -0400 [thread overview]
Message-ID: <20250909193830.GF218449@fedora> (raw)
In-Reply-To: <20250830025025.3610-5-hibriansong@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 4930 bytes --]
On Fri, Aug 29, 2025 at 10:50:25PM -0400, Brian Song wrote:
> To test FUSE-over-io_uring, set the environment variable
> FUSE_OVER_IO_URING=1. This applies only when using the
> 'fuse' protocol.
>
> $ FUSE_OVER_IO_URING=1 ./check -fuse
>
> Suggested-by: Kevin Wolf <kwolf@redhat.com>
> Suggested-by: Stefan Hajnoczi <stefanha@redhat.com>
> Signed-off-by: Brian Song <hibriansong@gmail.com>
> ---
> tests/qemu-iotests/check | 2 ++
> tests/qemu-iotests/common.rc | 45 +++++++++++++++++++++++++++---------
> 2 files changed, 36 insertions(+), 11 deletions(-)
>
> diff --git a/tests/qemu-iotests/check b/tests/qemu-iotests/check
> index 545f9ec7bd..c6fa0f9e3d 100755
> --- a/tests/qemu-iotests/check
> +++ b/tests/qemu-iotests/check
> @@ -94,6 +94,8 @@ def make_argparser() -> argparse.ArgumentParser:
> mg.add_argument('-' + fmt, dest='imgfmt', action='store_const',
> const=fmt, help=f'test {fmt}')
>
> + # To test FUSE-over-io_uring, set the environment variable
> + # FUSE_OVER_IO_URING=1. This applies only when using the 'fuse' protocol
> protocol_list = ['file', 'rbd', 'nbd', 'ssh', 'nfs', 'fuse']
> g_prt = p.add_argument_group(
> ' image protocol options',
> diff --git a/tests/qemu-iotests/common.rc b/tests/qemu-iotests/common.rc
> index e977cb4eb6..f8b79c3810 100644
> --- a/tests/qemu-iotests/common.rc
> +++ b/tests/qemu-iotests/common.rc
> @@ -539,17 +539,38 @@ _make_test_img()
> touch "$export_mp"
> rm -f "$SOCK_DIR/fuse-output"
>
> - # Usually, users would export formatted nodes. But we present fuse as a
> - # protocol-level driver here, so we have to leave the format to the
> - # client.
> - # Switch off allow-other, because in general we do not need it for
> - # iotests. The default allow-other=auto has the downside of printing a
> - # fusermount error on its first attempt if allow_other is not
> - # permissible, which we would need to filter.
This comment applies to both branches of the if statement. I think
keeping it here is slightly better.
> - QSD_NEED_PID=y $QSD \
> - --blockdev file,node-name=export-node,filename=$img_name,discard=unmap \
> - --export fuse,id=fuse-export,node-name=export-node,mountpoint="$export_mp",writable=on,growable=on,allow-other=off \
> - &
> + if [ -n "$FUSE_OVER_IO_URING" ]; then
> + nr_cpu=$(nproc 2>/dev/null || echo 1)
> + nr_iothreads=$((nr_cpu / 2))
> + if [ $nr_iothreads -lt 1 ]; then
> + nr_iothreads=1
> + fi
Please add a comment explaining that the purpose of this configuration
based on the number of CPUs is to test multiple IOThreads when the host
allows it, since that is a more interesting case then just 1 IOThread.
Many other configurations are possible as well, but not all of them can
be tested because the test matrix would be large.
> +
> + iothread_args=""
> + iothread_export_args=""
> + for ((i=0; i<$nr_iothreads; i++)); do
> + iothread_args="$iothread_args --object iothread,id=iothread$i"
> + iothread_export_args="$iothread_export_args,iothread.$i=iothread$i"
> + done
> +
> + QSD_NEED_PID=y $QSD \
> + $iothread_args \
> + --blockdev file,node-name=export-node,filename=$img_name,discard=unmap \
> + --export fuse,id=fuse-export,node-name=export-node,mountpoint="$export_mp",writable=on,growable=on,allow-other=off,io-uring=on$iothread_export_args \
> + &
> + else
> + # Usually, users would export formatted nodes. But we present fuse as a
> + # protocol-level driver here, so we have to leave the format to the
> + # client.
> + # Switch off allow-other, because in general we do not need it for
> + # iotests. The default allow-other=auto has the downside of printing a
> + # fusermount error on its first attempt if allow_other is not
> + # permissible, which we would need to filter.
> + QSD_NEED_PID=y $QSD \
> + --blockdev file,node-name=export-node,filename=$img_name,discard=unmap \
> + --export fuse,id=fuse-export,node-name=export-node,mountpoint="$export_mp",writable=on,growable=on,allow-other=off \
> + &
> + fi
>
> pidfile="$QEMU_TEST_DIR/qemu-storage-daemon.pid"
>
> @@ -592,6 +613,8 @@ _rm_test_img()
>
> kill "${FUSE_PIDS[index]}"
>
> + sleep 1
> +
What is the purpose of this sleep command?
> # Wait until the mount is gone
> timeout=10 # *0.5 s
> while true; do
> --
> 2.45.2
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2025-09-09 19:39 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-30 2:50 [PATCH 0/4] export/fuse: Add FUSE-over-io_uring for Storage Exports Brian Song
2025-08-30 2:50 ` [PATCH 1/4] export/fuse: add opt to enable FUSE-over-io_uring Brian Song
2025-09-03 10:53 ` Stefan Hajnoczi
2025-09-03 18:00 ` Brian Song
2025-09-09 14:48 ` Stefan Hajnoczi
2025-09-09 17:46 ` Brian Song
2025-09-09 18:05 ` Bernd Schubert
2025-09-03 11:26 ` Stefan Hajnoczi
2025-09-16 19:08 ` Kevin Wolf
2025-09-17 19:47 ` Brian Song
2025-09-19 14:13 ` Kevin Wolf
2025-08-30 2:50 ` [PATCH 2/4] export/fuse: process FUSE-over-io_uring requests Brian Song
2025-09-03 11:51 ` Stefan Hajnoczi
2025-09-08 19:09 ` Brian Song
2025-09-08 19:45 ` Bernd Schubert
2025-09-09 1:10 ` Brian Song
2025-09-09 15:26 ` Stefan Hajnoczi
2025-09-19 13:54 ` Kevin Wolf
2025-08-30 2:50 ` [PATCH 3/4] export/fuse: Safe termination for FUSE-uring Brian Song
2025-09-09 19:33 ` Stefan Hajnoczi
2025-09-09 20:51 ` Brian Song
2025-09-10 13:17 ` Stefan Hajnoczi
2025-09-15 5:43 ` Brian Song
2025-09-17 13:01 ` Hanna Czenczek
2025-09-17 22:06 ` Brian Song
2025-09-22 17:41 ` Stefan Hajnoczi
2025-09-22 17:51 ` Stefan Hajnoczi
2025-08-30 2:50 ` [PATCH 4/4] iotests: add tests for FUSE-over-io_uring Brian Song
2025-09-09 19:38 ` Stefan Hajnoczi [this message]
2025-09-09 20:51 ` Brian Song
2025-09-10 13:14 ` Stefan Hajnoczi
2025-09-12 2:22 ` Brian Song
2025-09-15 17:41 ` Stefan Hajnoczi
2025-08-30 12:00 ` [PATCH 0/4] export/fuse: Add FUSE-over-io_uring for Storage Exports Brian Song
2025-09-03 9:49 ` Stefan Hajnoczi
2025-09-03 18:11 ` Brian Song
2025-09-16 12:18 ` Kevin Wolf
2025-09-04 19:32 ` 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=20250909193830.GF218449@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).