Anatol Belski 4f9fcfa22b block: raw: Route aio and uring bounce through the vectored API ...

Reimplement run_unaligned_operation over AlignedFile read_vectored_at
and write_vectored_at instead of scattering and gathering through the
per operation write_bytes_at and read_bytes_at closures. The aio and
uring engines already reach this helper for the O_DIRECT misaligned
case, so both now share the same vectored bounce path as the sync
engine and the scatter gather logic lives only in AlignedFile.

The operation iovecs point at the same memory that write_bytes_at and
read_bytes_at reach, and the aligned fast path already hands those
iovecs to the kernel, so the direct vectored call is equivalent. For
guest memory read targets the destination pages are marked dirty by
mark_read_dirty in execute_async before the operation is submitted,
independent of how the bounce copies bytes, so the raw iovec path
preserves dirty tracking. Drop the now unneeded mut bindings at the
call sites.

Signed-off-by: Anatol Belski <anbelski@linux.microsoft.com>

2026-07-21 08:37:00 +00:00

..

src

block: raw: Route aio and uring bounce through the vectored API

2026-07-21 08:37:00 +00:00

Cargo.toml

build(deps): bump the non-rust-vmm group across 2 directories with 13 updates

2026-07-10 00:53:35 +00:00