hesela.devio_uring registered buffers
io_uring registered buffers are application-memory regions registered with a ring and selected by index for supported fixed-buffer operations.
Registration: io_uring_register_buffers registers an iovec array for later fixed-buffer operations. Reusing those regions can avoid repeated mapping and page-reference work, notably with O_DIRECT I/O; registration does not itself open a file with O_DIRECT or guarantee a workload speedup. [1]
Selection: io_uring_prep_read_fixed uses buf_index to choose a registered region. The requested address and byte length must lie within that region; a subrange is allowed. This index is not a provided-buffer group ID or a selected buffer ID returned in CQE flags. [2] [3]
Completion: choosing registered memory does not establish that a read transferred every requested byte. Inspect the operation result and keep in-flight payload memory valid. Registration, request completion and the application's decision to reuse the payload are separate responsibilities. [2] [4]
Memory cost: the liburing 2.8 registration manual describes locked buffers charged against RLIMIT_MEMLOCK. Registering only part of a huge page still pins the whole huge page. Ring teardown can complete asynchronously, so closing the ring is not evidence that its pages were immediately unpinned. Size and measure the registered pool separately from each request's byte count. [5]
Relations
Limitations
- A fixed-buffer request must stay within its selected registered region; registration does not relax other I/O requirements. [2]
- Registering a provided-buffer ring does not register its payloads for fixed-buffer I/O; a group ID is not a fixed-buffer index. [7, 1]
Citations
- liburing 2.8: registration and fixed-buffer mapping
- liburing 2.8: registered index and permitted subranges
- liburing 2.8: buffer groups and selected IDs
- liburing 2.8: io_uring(7), payload-buffer lifetime
- liburing 2.8: io_uring_register(2), locked memory and asynchronous teardown
- liburing 2.8: provided-buffer descriptor-ring registration
Further reading
Sources & caveats
- Primary documentation and pinned Linux v6.16 ABI review; no native kernel execution, performance benchmark or durability experiment.