diff options
| author | Caleb Sander Mateos <csander@purestorage.com> | 2025-06-21 11:10:14 -0600 |
|---|---|---|
| committer | Jens Axboe <axboe@kernel.dk> | 2025-06-24 20:45:31 -0600 |
| commit | 81b4d1a1d03301dcca8af5c58eded9e535f1f6ed (patch) | |
| tree | db361575c3979a8e39ddea33a7fe3c3060e85158 /scripts/lib/kdoc/kdoc_parser.py | |
| parent | 67caa528ae08cd05e485c0ea6aea0baaf6579b06 (diff) | |
ublk: update UBLK_F_SUPPORT_ZERO_COPY comment in UAPI header
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.
Signed-off-by: Caleb Sander Mateos <csander@purestorage.com>
Reviewed-by: Ming Lei <ming.lei@redhat.com>
Link: https://lore.kernel.org/r/20250621171015.354932-1-csander@purestorage.com
Signed-off-by: Jens Axboe <axboe@kernel.dk>
Diffstat (limited to 'scripts/lib/kdoc/kdoc_parser.py')
0 files changed, 0 insertions, 0 deletions