Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions man/io_uring_register_buffers.3
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,12 @@ return 0.
return number of buffers updated.
On failure they return
.BR -errno .

.SH NOTES
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'd word this stronger - "Don't use this API for new code. Use the more efficient io_uring_register_buf_ring(3) API instead, see that man page for details."

When possible prefer to use the newer and more efficient
.BR io_uring_register_buf_ring (3)
API.

.SH SEE ALSO
.BR io_uring_register (2),
.BR io_uring_get_sqe (3),
Expand Down
6 changes: 6 additions & 0 deletions man/io_uring_setup_buf_ring.3
Original file line number Diff line number Diff line change
Expand Up @@ -80,12 +80,18 @@ returns a pointer to the buffer ring. On failure it returns
and sets
.I *err
to -errno.

.SH NOTES
Note that even if the kernel supports this feature, registering a provided
buffer ring may still fail with
.B -EINVAL
if the host is a 32-bit architecture and the memory being passed in resides in
high memory.

Remember that you need to call
Copy link
Copy Markdown
Owner

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"Use io_uring_buf_ring_add(3) to add buffers to the ring, and io_uring_buf_ring_advance(3) to make these buffers available to the kernel. Refer to those man pages for details."

.BR io_uring_buf_ring_add (3)
to make the allocated buffers available to the kernel.

.SH SEE ALSO
.BR io_uring_register_buf_ring (3),
.BR io_uring_buf_ring_init (3),
Expand Down