The io_uring_clone_buffers(3) function clones registered buffers from the ring indicated by src to the
ring indicated by dst. Upon successful completion of this operation, src and dst will have the same set
of registered buffers. This operation is identical to performing a io_uring_register_buffers(3) operation
on the dst ring, if the src ring previously had that same buffer registration operating done.
The dst ring must not have any buffers currently registered. If buffers are currently registered on the
destination ring, they must be unregistered with io_uring_unregister_buffers(3) first.
Available since kernel 6.12.
The io_uring_clone_buffers_offset(3) function also clones buffers from the src ring to the dst ring,
however it supports cloning only a subset of the buffers, where io_uring_clone_buffers(3) always clones
all of them. dst_off indicates at what offset cloning should start in the destination, src_off indicates
at what offset cloning should start in the source, and nr indicates how many buffers to clone at the
given offset. If both dst_off, src_off, and nr are given as 0, then io_uring_clone_buffers_offset(3)
performs the same action as io_uring_clone_buffers(3).flags may be set to the following value:
IORING_REGISTER_DST_REPLACE
If set, cloning may happen for a destination ring that already has a buffer table assigned. In
that case, existing nodes that overlap with the specified range will be released and
replaced.IORING_REGISTER_DST_REPLACE If set, cloning may happen for a destination ring that
already has a buffer table assigned. In that case, existing nodes that overlap with the specified
range will be released and replaced.
Available since kernel 6.13.