qapi/block-export: Document FUSE's multi-threading

Document for users that FUSE's multi-threading implementation
distributes requests in a round-robin manner, regardless of where they
originate from.

As noted by Stefan, this will probably change with a FUSE-over-io_uring
implementation (which is supposed to have CPU affinity), but documenting
that is left for once that is done.

Suggested-by: Stefan Hajnoczi <stefanha@redhat.com>
Acked-by: Markus Armbruster <armbru@redhat.com>
Signed-off-by: Hanna Czenczek <hreitz@redhat.com>
Message-ID: <20260309150856.26800-25-hreitz@redhat.com>
Reviewed-by: Kevin Wolf <kwolf@redhat.com>
Signed-off-by: Kevin Wolf <kwolf@redhat.com>
This commit is contained in:
Hanna Czenczek
2026-03-09 16:08:55 +01:00
committed by Kevin Wolf
parent b756692ce1
commit 40ee2ff0ce

View File

@@ -164,6 +164,11 @@
# Options for exporting a block graph node on some (file) mountpoint
# as a raw image.
#
# Multi-threading note: The FUSE export supports multi-threading.
# Currently, requests are distributed across these threads in a
# round-robin fashion, i.e. independently of the CPU core from which a
# request originates.
#
# @mountpoint: Path on which to export the block device via FUSE.
# This must point to an existing regular file.
#