On Sat, 21 Jun 2025 11:10:14 -0600, Caleb Sander Mateos wrote:
> UBLK_F_SUPPORT_ZERO_COPY has a very old comment describing the initial
> idea for how zero-copy would be implemented. The actual implementation
> added in commit 1f6540e2aabb ("ublk: zc register/unregister bvec") uses
> io_uring registered buffers rather than shared memory mapping.
> Remove the inaccurate remarks about mapping ublk request memory into the
> ublk server's address space and requiring 4K block size. Replace them
> with a description of the current zero-copy mechanism.
>
> [...]
Applied, thanks!
[1/1] ublk: update UBLK_F_SUPPORT_ZERO_COPY comment in UAPI header
commit: c770c2e2b53b468d5eb124e7daabdb4a8471f442
Best regards,
--
Jens Axboe
