[PATCH RFC 1/1] block/export: FUSE-over-io_uring Support for QEMU FUSE Exports

support is still incomplete. In addition, handling connection termination and managing the "drained" state of a FUSE block export in QEMU remain as pending work. Suggested-by: Kevin Wolf Suggested-by: Stefan Hajnoczi Signed-off-by: Brian Song --- block/export/fuse.c

[PATCH RFC 0/1] block/export: FUSE-over-io_uring Support for QEMU FUSE Exports

CPUs. Therefore, this initial version only works on single-core VMs (i.e., QEMU started with -smp 1) or single core machine. Brian Song (1): block/export: FUSE-over-io_uring Support for QEMU FUSE Exports block/export/fuse.c | 423 +-- docs/tools/qemu

[RFC PATCH 0/1] add fixed file table support

pth=64 Run status group 0 (all jobs): READ: bw=498MiB/s (522MB/s), 498MiB/s-498MiB/s (522MB/s-522MB/s), io=14.6GiB (15.7GB), run=30001-30001msec Disk stats (read/write): vda: ios=4468557/140, sectors=35748456/8817, merge=0/18, ticks=129894/244, in_queue=130143, util=95.00% Brian Song (1)

[RFC PATCH 1/1] This work adds support for registering block file descriptors to the io_uring instance and uses IOSQE_FIXED_FILE in I/O requests (SQEs) to avoid the cost of fdget() in the kernel. It i

Suggested-by: Kevin Wolf Suggested-by: Stefan Hajnoczi Signed-off-by: Brian Song --- block/io_uring.c | 60 1 file changed, 60 insertions(+) diff --git a/block/io_uring.c b/block/io_uring.c index dd4f304910..94a875fbae 100644 --- a/block