* [PATCH gwproxy v1 0/3] Minor changes and fixes
@ 2025-07-29 2:48 Ahmad Gani
2025-07-29 2:48 ` [PATCH gwproxy v1 2/3] io_uring: Add macro guard Ahmad Gani
` (2 more replies)
0 siblings, 3 replies; 11+ messages in thread
From: Ahmad Gani @ 2025-07-29 2:48 UTC (permalink / raw)
To: Ammar Faizi; +Cc: Ahmad Gani, GNU/Weeb Mailing List
The patches contain the following changes:
- add liburing to the code base
- add macro guard
- fix undeclared GWP_CONN_FLAG_IS_CANCEL macro
My Linux distro didn't have a static version of the liburing library.
Let's just embed the liburing source code directly into the code base.
VS Code's C/C++ linter was complaining about an undefined struct member.
Adding a macro guard resolved the warning, although I later discovered
that configuring the defines array in c_cpp_properties.json also fixes
the issue, but it's still nice to have macro guard as a safe fallback.
And I noticed that declaration of GWP_CONN_FLAG_IS_CANCEL is missing, and
have now declared it.
Please pull!
Signed-off-by: Ahmad Gani <reyuki@gnuweeb.org>
---
Ahmad Gani (3):
io_uring: Add liburing to the code base
io_uring: Add macro guard
io_uring: Rename GWP_CONN_FLAG_IS_SHUTDOWN to GWP_CONN_FLAG_IS_CANCEL
Makefile | 10 +-
src/gwproxy/ev/io_uring.c | 13 +-
src/gwproxy/gwproxy.h | 2 +-
.../.github/actions/codespell/stopwords | 7 +
src/liburing/.github/pull_request_template.md | 86 +
src/liburing/.github/workflows/ci.yml | 281 ++
src/liburing/.gitignore | 48 +
src/liburing/CHANGELOG | 137 +
src/liburing/CITATION.cff | 11 +
src/liburing/CONTRIBUTING.md | 165 ++
src/liburing/COPYING | 502 ++++
src/liburing/COPYING.GPL | 339 +++
src/liburing/LICENSE | 20 +
src/liburing/Makefile | 96 +
src/liburing/Makefile.common | 7 +
src/liburing/Makefile.quiet | 11 +
src/liburing/README | 111 +
src/liburing/SECURITY.md | 6 +
src/liburing/configure | 728 +++++
src/liburing/debian/README.Debian | 7 +
src/liburing/debian/changelog | 38 +
src/liburing/debian/control | 39 +
src/liburing/debian/copyright | 49 +
src/liburing/debian/liburing-dev.install | 4 +
src/liburing/debian/liburing-dev.manpages | 5 +
src/liburing/debian/liburing2.install | 1 +
src/liburing/debian/liburing2.symbols | 56 +
src/liburing/debian/patches/series | 1 +
src/liburing/debian/rules | 29 +
src/liburing/debian/source/format | 1 +
src/liburing/debian/source/local-options | 2 +
src/liburing/debian/source/options | 1 +
src/liburing/debian/watch | 3 +
src/liburing/examples/Makefile | 62 +
src/liburing/examples/helpers.c | 95 +
src/liburing/examples/helpers.h | 25 +
src/liburing/examples/io_uring-close-test.c | 123 +
src/liburing/examples/io_uring-cp.c | 282 ++
src/liburing/examples/io_uring-test.c | 115 +
src/liburing/examples/io_uring-udp.c | 403 +++
src/liburing/examples/kdigest.c | 405 +++
src/liburing/examples/link-cp.c | 193 ++
src/liburing/examples/napi-busy-poll-client.c | 509 ++++
src/liburing/examples/napi-busy-poll-server.c | 450 +++
src/liburing/examples/poll-bench.c | 101 +
src/liburing/examples/proxy.c | 2528 +++++++++++++++++
src/liburing/examples/proxy.h | 102 +
src/liburing/examples/reg-wait.c | 194 ++
src/liburing/examples/rsrc-update-bench.c | 100 +
src/liburing/examples/send-zerocopy.c | 705 +++++
src/liburing/examples/ucontext-cp.c | 258 ++
src/liburing/examples/zcrx.c | 436 +++
src/liburing/liburing-ffi.pc.in | 12 +
src/liburing/liburing.pc.in | 12 +
src/liburing/liburing.spec | 66 +
src/liburing/make-debs.sh | 55 +
src/liburing/man/IO_URING_CHECK_VERSION.3 | 1 +
src/liburing/man/IO_URING_VERSION_MAJOR.3 | 1 +
src/liburing/man/IO_URING_VERSION_MINOR.3 | 1 +
.../man/__io_uring_buf_ring_cq_advance.3 | 1 +
src/liburing/man/io_uring.7 | 864 ++++++
src/liburing/man/io_uring_buf_ring_add.3 | 61 +
src/liburing/man/io_uring_buf_ring_advance.3 | 31 +
.../man/io_uring_buf_ring_available.3 | 47 +
.../man/io_uring_buf_ring_cq_advance.3 | 55 +
src/liburing/man/io_uring_buf_ring_init.3 | 36 +
src/liburing/man/io_uring_buf_ring_mask.3 | 27 +
src/liburing/man/io_uring_check_version.3 | 72 +
src/liburing/man/io_uring_clone_buffers.3 | 168 ++
.../man/io_uring_clone_buffers_offset.3 | 1 +
src/liburing/man/io_uring_close_ring_fd.3 | 43 +
src/liburing/man/io_uring_cq_advance.3 | 49 +
src/liburing/man/io_uring_cq_has_overflow.3 | 31 +
src/liburing/man/io_uring_cq_ready.3 | 26 +
src/liburing/man/io_uring_cqe_get_data.3 | 53 +
src/liburing/man/io_uring_cqe_get_data64.3 | 1 +
src/liburing/man/io_uring_cqe_seen.3 | 41 +
src/liburing/man/io_uring_enable_rings.3 | 40 +
src/liburing/man/io_uring_enter.2 | 2066 ++++++++++++++
src/liburing/man/io_uring_enter2.2 | 1 +
src/liburing/man/io_uring_for_each_cqe.3 | 63 +
src/liburing/man/io_uring_free_buf_ring.3 | 53 +
src/liburing/man/io_uring_free_probe.3 | 27 +
src/liburing/man/io_uring_free_reg_wait.3 | 35 +
src/liburing/man/io_uring_get_events.3 | 33 +
src/liburing/man/io_uring_get_probe.3 | 30 +
src/liburing/man/io_uring_get_sqe.3 | 57 +
src/liburing/man/io_uring_major_version.3 | 1 +
src/liburing/man/io_uring_minor_version.3 | 1 +
src/liburing/man/io_uring_opcode_supported.3 | 30 +
src/liburing/man/io_uring_peek_batch_cqe.3 | 1 +
src/liburing/man/io_uring_peek_cqe.3 | 59 +
src/liburing/man/io_uring_prep_accept.3 | 203 ++
.../man/io_uring_prep_accept_direct.3 | 1 +
src/liburing/man/io_uring_prep_bind.3 | 54 +
src/liburing/man/io_uring_prep_cancel.3 | 136 +
src/liburing/man/io_uring_prep_cancel64.3 | 1 +
src/liburing/man/io_uring_prep_cancel_fd.3 | 1 +
src/liburing/man/io_uring_prep_close.3 | 67 +
src/liburing/man/io_uring_prep_close_direct.3 | 1 +
src/liburing/man/io_uring_prep_cmd.3 | 126 +
src/liburing/man/io_uring_prep_cmd_discard.3 | 64 +
src/liburing/man/io_uring_prep_connect.3 | 66 +
src/liburing/man/io_uring_prep_epoll_wait.3 | 64 +
src/liburing/man/io_uring_prep_fadvise.3 | 76 +
src/liburing/man/io_uring_prep_fadvise64.3 | 1 +
src/liburing/man/io_uring_prep_fallocate.3 | 59 +
src/liburing/man/io_uring_prep_fgetxattr.3 | 1 +
src/liburing/man/io_uring_prep_files_update.3 | 92 +
.../man/io_uring_prep_fixed_fd_install.3 | 70 +
src/liburing/man/io_uring_prep_fsetxattr.3 | 1 +
src/liburing/man/io_uring_prep_fsync.3 | 70 +
src/liburing/man/io_uring_prep_ftruncate.3 | 54 +
src/liburing/man/io_uring_prep_futex_wait.3 | 94 +
src/liburing/man/io_uring_prep_futex_waitv.3 | 78 +
src/liburing/man/io_uring_prep_futex_wake.3 | 86 +
src/liburing/man/io_uring_prep_getxattr.3 | 61 +
src/liburing/man/io_uring_prep_link.3 | 1 +
src/liburing/man/io_uring_prep_link_timeout.3 | 98 +
src/liburing/man/io_uring_prep_linkat.3 | 91 +
src/liburing/man/io_uring_prep_listen.3 | 52 +
src/liburing/man/io_uring_prep_madvise.3 | 72 +
src/liburing/man/io_uring_prep_madvise64.3 | 1 +
src/liburing/man/io_uring_prep_mkdir.3 | 1 +
src/liburing/man/io_uring_prep_mkdirat.3 | 83 +
src/liburing/man/io_uring_prep_msg_ring.3 | 92 +
.../man/io_uring_prep_msg_ring_cqe_flags.3 | 1 +
src/liburing/man/io_uring_prep_msg_ring_fd.3 | 83 +
.../man/io_uring_prep_msg_ring_fd_alloc.3 | 1 +
.../man/io_uring_prep_multishot_accept.3 | 1 +
.../io_uring_prep_multishot_accept_direct.3 | 1 +
src/liburing/man/io_uring_prep_nop.3 | 28 +
src/liburing/man/io_uring_prep_open.3 | 1 +
src/liburing/man/io_uring_prep_open_direct.3 | 1 +
src/liburing/man/io_uring_prep_openat.3 | 138 +
src/liburing/man/io_uring_prep_openat2.3 | 119 +
.../man/io_uring_prep_openat2_direct.3 | 1 +
.../man/io_uring_prep_openat_direct.3 | 1 +
src/liburing/man/io_uring_prep_poll_add.3 | 72 +
.../man/io_uring_prep_poll_multishot.3 | 1 +
src/liburing/man/io_uring_prep_poll_remove.3 | 55 +
src/liburing/man/io_uring_prep_poll_update.3 | 101 +
.../man/io_uring_prep_provide_buffers.3 | 140 +
src/liburing/man/io_uring_prep_read.3 | 69 +
src/liburing/man/io_uring_prep_read_fixed.3 | 72 +
.../man/io_uring_prep_read_multishot.3 | 100 +
src/liburing/man/io_uring_prep_readv.3 | 85 +
src/liburing/man/io_uring_prep_readv2.3 | 111 +
src/liburing/man/io_uring_prep_recv.3 | 139 +
.../man/io_uring_prep_recv_multishot.3 | 1 +
src/liburing/man/io_uring_prep_recvmsg.3 | 126 +
.../man/io_uring_prep_recvmsg_multishot.3 | 1 +
.../man/io_uring_prep_remove_buffers.3 | 52 +
src/liburing/man/io_uring_prep_rename.3 | 1 +
src/liburing/man/io_uring_prep_renameat.3 | 95 +
src/liburing/man/io_uring_prep_send.3 | 146 +
src/liburing/man/io_uring_prep_send_bundle.3 | 1 +
.../man/io_uring_prep_send_set_addr.3 | 38 +
src/liburing/man/io_uring_prep_send_zc.3 | 96 +
.../man/io_uring_prep_send_zc_fixed.3 | 1 +
src/liburing/man/io_uring_prep_sendmsg.3 | 91 +
src/liburing/man/io_uring_prep_sendmsg_zc.3 | 1 +
src/liburing/man/io_uring_prep_sendto.3 | 1 +
src/liburing/man/io_uring_prep_setxattr.3 | 64 +
src/liburing/man/io_uring_prep_shutdown.3 | 53 +
src/liburing/man/io_uring_prep_socket.3 | 118 +
.../man/io_uring_prep_socket_direct.3 | 1 +
.../man/io_uring_prep_socket_direct_alloc.3 | 1 +
src/liburing/man/io_uring_prep_splice.3 | 120 +
src/liburing/man/io_uring_prep_statx.3 | 74 +
src/liburing/man/io_uring_prep_symlink.3 | 1 +
src/liburing/man/io_uring_prep_symlinkat.3 | 85 +
.../man/io_uring_prep_sync_file_range.3 | 59 +
src/liburing/man/io_uring_prep_tee.3 | 74 +
src/liburing/man/io_uring_prep_timeout.3 | 107 +
.../man/io_uring_prep_timeout_remove.3 | 1 +
.../man/io_uring_prep_timeout_update.3 | 99 +
src/liburing/man/io_uring_prep_unlink.3 | 1 +
src/liburing/man/io_uring_prep_unlinkat.3 | 82 +
src/liburing/man/io_uring_prep_waitid.3 | 67 +
src/liburing/man/io_uring_prep_write.3 | 67 +
src/liburing/man/io_uring_prep_write_fixed.3 | 72 +
src/liburing/man/io_uring_prep_writev.3 | 85 +
src/liburing/man/io_uring_prep_writev2.3 | 111 +
src/liburing/man/io_uring_queue_exit.3 | 26 +
src/liburing/man/io_uring_queue_init.3 | 130 +
src/liburing/man/io_uring_queue_init_mem.3 | 1 +
src/liburing/man/io_uring_queue_init_params.3 | 1 +
.../man/io_uring_recvmsg_cmsg_firsthdr.3 | 1 +
.../man/io_uring_recvmsg_cmsg_nexthdr.3 | 1 +
src/liburing/man/io_uring_recvmsg_name.3 | 1 +
src/liburing/man/io_uring_recvmsg_out.3 | 82 +
src/liburing/man/io_uring_recvmsg_payload.3 | 1 +
.../man/io_uring_recvmsg_payload_length.3 | 1 +
src/liburing/man/io_uring_recvmsg_validate.3 | 1 +
src/liburing/man/io_uring_register.2 | 1199 ++++++++
src/liburing/man/io_uring_register_buf_ring.3 | 157 +
src/liburing/man/io_uring_register_buffers.3 | 105 +
.../man/io_uring_register_buffers_sparse.3 | 1 +
.../man/io_uring_register_buffers_tags.3 | 1 +
.../io_uring_register_buffers_update_tag.3 | 1 +
src/liburing/man/io_uring_register_clock.3 | 72 +
src/liburing/man/io_uring_register_eventfd.3 | 50 +
.../man/io_uring_register_eventfd_async.3 | 1 +
.../man/io_uring_register_file_alloc_range.3 | 52 +
src/liburing/man/io_uring_register_files.3 | 120 +
.../man/io_uring_register_files_sparse.3 | 1 +
.../man/io_uring_register_files_tags.3 | 1 +
.../man/io_uring_register_files_update.3 | 1 +
.../man/io_uring_register_files_update_tag.3 | 1 +
src/liburing/man/io_uring_register_iowq_aff.3 | 67 +
.../man/io_uring_register_iowq_max_workers.3 | 71 +
src/liburing/man/io_uring_register_napi.3 | 40 +
src/liburing/man/io_uring_register_reg_wait.3 | 62 +
src/liburing/man/io_uring_register_ring_fd.3 | 51 +
.../man/io_uring_register_sync_cancel.3 | 73 +
src/liburing/man/io_uring_register_sync_msg.3 | 74 +
src/liburing/man/io_uring_resize_rings.3 | 116 +
src/liburing/man/io_uring_setup.2 | 762 +++++
src/liburing/man/io_uring_setup_buf_ring.3 | 94 +
src/liburing/man/io_uring_setup_reg_wait.3 | 121 +
src/liburing/man/io_uring_sq_ready.3 | 31 +
src/liburing/man/io_uring_sq_space_left.3 | 25 +
src/liburing/man/io_uring_sqe_set_buf_group.3 | 32 +
src/liburing/man/io_uring_sqe_set_data.3 | 57 +
src/liburing/man/io_uring_sqe_set_data64.3 | 1 +
src/liburing/man/io_uring_sqe_set_flags.3 | 87 +
src/liburing/man/io_uring_sqring_wait.3 | 34 +
src/liburing/man/io_uring_submit.3 | 51 +
.../man/io_uring_submit_and_get_events.3 | 31 +
src/liburing/man/io_uring_submit_and_wait.3 | 44 +
.../io_uring_submit_and_wait_min_timeout.3 | 119 +
.../man/io_uring_submit_and_wait_reg.3 | 63 +
.../man/io_uring_submit_and_wait_timeout.3 | 74 +
.../man/io_uring_unregister_buf_ring.3 | 30 +
.../man/io_uring_unregister_buffers.3 | 27 +
.../man/io_uring_unregister_eventfd.3 | 1 +
src/liburing/man/io_uring_unregister_files.3 | 27 +
.../man/io_uring_unregister_iowq_aff.3 | 1 +
src/liburing/man/io_uring_unregister_napi.3 | 27 +
.../man/io_uring_unregister_ring_fd.3 | 32 +
src/liburing/man/io_uring_wait_cqe.3 | 41 +
src/liburing/man/io_uring_wait_cqe_nr.3 | 49 +
src/liburing/man/io_uring_wait_cqe_timeout.3 | 61 +
src/liburing/man/io_uring_wait_cqes.3 | 80 +
.../man/io_uring_wait_cqes_min_timeout.3 | 76 +
src/liburing/src/Makefile | 142 +
src/liburing/src/arch/aarch64/lib.h | 47 +
src/liburing/src/arch/aarch64/syscall.h | 91 +
src/liburing/src/arch/generic/lib.h | 17 +
src/liburing/src/arch/generic/syscall.h | 100 +
src/liburing/src/arch/riscv64/lib.h | 48 +
src/liburing/src/arch/riscv64/syscall.h | 100 +
src/liburing/src/arch/syscall-defs.h | 94 +
src/liburing/src/arch/x86/lib.h | 11 +
src/liburing/src/arch/x86/syscall.h | 296 ++
src/liburing/src/ffi.c | 15 +
src/liburing/src/include/liburing.h | 1796 ++++++++++++
src/liburing/src/include/liburing/barrier.h | 81 +
src/liburing/src/include/liburing/io_uring.h | 995 +++++++
src/liburing/src/include/liburing/sanitize.h | 39 +
src/liburing/src/int_flags.h | 21 +
src/liburing/src/lib.h | 50 +
src/liburing/src/liburing-ffi.map | 246 ++
src/liburing/src/liburing.map | 128 +
src/liburing/src/nolibc.c | 55 +
src/liburing/src/queue.c | 485 ++++
src/liburing/src/register.c | 515 ++++
src/liburing/src/sanitize.c | 174 ++
src/liburing/src/setup.c | 698 +++++
src/liburing/src/setup.h | 15 +
src/liburing/src/syscall.c | 29 +
src/liburing/src/syscall.h | 53 +
src/liburing/src/version.c | 21 +
src/liburing/test/232c93d07b74.c | 294 ++
src/liburing/test/35fa71a030ca.c | 336 +++
src/liburing/test/500f9fbadef8.c | 93 +
src/liburing/test/7ad0e4b2f83c.c | 69 +
src/liburing/test/8a9973408177.c | 107 +
src/liburing/test/917257daa0fe.c | 61 +
src/liburing/test/Makefile | 348 +++
src/liburing/test/a0908ae19763.c | 66 +
src/liburing/test/a4c0b3decb33.c | 188 ++
src/liburing/test/accept-link.c | 255 ++
src/liburing/test/accept-non-empty.c | 256 ++
src/liburing/test/accept-reuse.c | 163 ++
src/liburing/test/accept-test.c | 84 +
src/liburing/test/accept.c | 918 ++++++
src/liburing/test/across-fork.c | 284 ++
src/liburing/test/b19062a56726.c | 61 +
src/liburing/test/b5837bd5311d.c | 78 +
src/liburing/test/bind-listen.c | 408 +++
src/liburing/test/buf-ring-nommap.c | 130 +
src/liburing/test/buf-ring-put.c | 83 +
src/liburing/test/buf-ring.c | 475 ++++
src/liburing/test/ce593a6c480a.c | 139 +
src/liburing/test/close-opath.c | 123 +
src/liburing/test/cmd-discard.c | 435 +++
src/liburing/test/config | 14 +
src/liburing/test/conn-unreach.c | 132 +
src/liburing/test/connect-rep.c | 204 ++
src/liburing/test/connect.c | 446 +++
src/liburing/test/coredump.c | 67 +
src/liburing/test/cq-full.c | 97 +
src/liburing/test/cq-overflow.c | 542 ++++
src/liburing/test/cq-peek-batch.c | 103 +
src/liburing/test/cq-ready.c | 95 +
src/liburing/test/cq-size.c | 65 +
src/liburing/test/d4ae271dfaae.c | 104 +
src/liburing/test/d77a67ed5f27.c | 65 +
src/liburing/test/defer-taskrun.c | 391 +++
src/liburing/test/defer-tw-timeout.c | 176 ++
src/liburing/test/defer.c | 319 +++
src/liburing/test/double-poll-crash.c | 195 ++
src/liburing/test/drop-submit.c | 94 +
src/liburing/test/eeed8b54e0df.c | 122 +
src/liburing/test/empty-eownerdead.c | 45 +
src/liburing/test/eploop.c | 74 +
src/liburing/test/epwait.c | 420 +++
src/liburing/test/eventfd-disable.c | 179 ++
src/liburing/test/eventfd-reg.c | 77 +
src/liburing/test/eventfd-ring.c | 123 +
src/liburing/test/eventfd.c | 112 +
src/liburing/test/evfd-short-read.c | 84 +
src/liburing/test/evloop.c | 73 +
src/liburing/test/exec-target.c | 6 +
src/liburing/test/exit-no-cleanup.c | 128 +
src/liburing/test/fadvise.c | 185 ++
src/liburing/test/fallocate.c | 265 ++
src/liburing/test/fc2a85cb02ef.c | 132 +
src/liburing/test/fd-install.c | 500 ++++
src/liburing/test/fd-pass.c | 237 ++
src/liburing/test/fdinfo-sqpoll.c | 117 +
src/liburing/test/fdinfo.c | 427 +++
src/liburing/test/fifo-nonblock-read.c | 58 +
src/liburing/test/file-exit-unreg.c | 48 +
src/liburing/test/file-register.c | 1201 ++++++++
src/liburing/test/file-update.c | 231 ++
src/liburing/test/file-verify.c | 665 +++++
src/liburing/test/files-exit-hang-poll.c | 114 +
src/liburing/test/files-exit-hang-timeout.c | 136 +
src/liburing/test/fixed-buf-iter.c | 117 +
src/liburing/test/fixed-buf-merge.c | 101 +
src/liburing/test/fixed-hugepage.c | 425 +++
src/liburing/test/fixed-link.c | 90 +
src/liburing/test/fixed-reuse.c | 160 ++
src/liburing/test/fixed-seg.c | 187 ++
src/liburing/test/fpos.c | 255 ++
src/liburing/test/fsnotify.c | 119 +
src/liburing/test/fsync.c | 224 ++
src/liburing/test/futex-kill.c | 135 +
src/liburing/test/futex.c | 583 ++++
src/liburing/test/hardlink.c | 170 ++
src/liburing/test/helpers.c | 511 ++++
src/liburing/test/helpers.h | 129 +
src/liburing/test/ignore-single-mmap.c | 48 +
src/liburing/test/init-mem.c | 206 ++
src/liburing/test/io-cancel.c | 537 ++++
src/liburing/test/io_uring_enter.c | 264 ++
src/liburing/test/io_uring_passthrough.c | 521 ++++
src/liburing/test/io_uring_register.c | 533 ++++
src/liburing/test/io_uring_setup.c | 110 +
src/liburing/test/iopoll-leak.c | 89 +
src/liburing/test/iopoll-overflow.c | 119 +
src/liburing/test/iopoll.c | 475 ++++
src/liburing/test/iowait.c | 141 +
src/liburing/test/kallsyms.c | 203 ++
src/liburing/test/lfs-openat-write.c | 119 +
src/liburing/test/lfs-openat.c | 273 ++
src/liburing/test/link-timeout.c | 1267 +++++++++
src/liburing/test/link.c | 497 ++++
src/liburing/test/link_drain.c | 255 ++
src/liburing/test/linked-defer-close.c | 224 ++
src/liburing/test/madvise.c | 182 ++
src/liburing/test/min-timeout-wait.c | 329 +++
src/liburing/test/min-timeout.c | 208 ++
src/liburing/test/mkdir.c | 118 +
src/liburing/test/msg-ring-fd.c | 331 +++
src/liburing/test/msg-ring-flags.c | 212 ++
src/liburing/test/msg-ring-overflow.c | 159 ++
src/liburing/test/msg-ring.c | 587 ++++
src/liburing/test/multicqes_drain.c | 429 +++
src/liburing/test/napi-test.c | 228 ++
src/liburing/test/napi-test.sh | 48 +
src/liburing/test/no-mmap-inval.c | 44 +
src/liburing/test/nolibc.c | 62 +
src/liburing/test/nop-all-sizes.c | 99 +
src/liburing/test/nop.c | 221 ++
src/liburing/test/nvme.h | 171 ++
src/liburing/test/ooo-file-unreg.c | 82 +
src/liburing/test/open-close.c | 301 ++
src/liburing/test/open-direct-link.c | 188 ++
src/liburing/test/open-direct-pick.c | 180 ++
src/liburing/test/openat2.c | 335 +++
src/liburing/test/personality.c | 204 ++
src/liburing/test/pipe-bug.c | 101 +
src/liburing/test/pipe-eof.c | 93 +
src/liburing/test/pipe-reuse.c | 105 +
src/liburing/test/poll-cancel-all.c | 496 ++++
src/liburing/test/poll-cancel-ton.c | 135 +
src/liburing/test/poll-cancel.c | 228 ++
src/liburing/test/poll-link.c | 221 ++
src/liburing/test/poll-many.c | 236 ++
src/liburing/test/poll-mshot-overflow.c | 265 ++
src/liburing/test/poll-mshot-update.c | 330 +++
src/liburing/test/poll-race-mshot.c | 276 ++
src/liburing/test/poll-race.c | 105 +
src/liburing/test/poll-ring.c | 48 +
src/liburing/test/poll-v-poll.c | 356 +++
src/liburing/test/poll.c | 327 +++
src/liburing/test/pollfree.c | 148 +
src/liburing/test/probe.c | 135 +
src/liburing/test/read-before-exit.c | 129 +
src/liburing/test/read-inc-file.c | 150 +
src/liburing/test/read-mshot-empty.c | 158 ++
src/liburing/test/read-mshot-stdin.c | 121 +
src/liburing/test/read-mshot.c | 659 +++++
src/liburing/test/read-write.c | 1085 +++++++
src/liburing/test/recv-bundle-short-ooo.c | 450 +++
src/liburing/test/recv-inc-ooo.c | 411 +++
src/liburing/test/recv-msgall-stream.c | 401 +++
src/liburing/test/recv-msgall.c | 268 ++
src/liburing/test/recv-mshot-fair.c | 559 ++++
src/liburing/test/recv-multishot.c | 602 ++++
src/liburing/test/recvsend_bundle-inc.c | 680 +++++
src/liburing/test/recvsend_bundle.c | 754 +++++
src/liburing/test/reg-fd-only.c | 141 +
src/liburing/test/reg-hint.c | 56 +
src/liburing/test/reg-reg-ring.c | 90 +
src/liburing/test/reg-wait.c | 580 ++++
src/liburing/test/regbuf-clone.c | 698 +++++
src/liburing/test/regbuf-merge.c | 98 +
src/liburing/test/register-restrictions.c | 634 +++++
src/liburing/test/rename.c | 190 ++
src/liburing/test/resize-rings.c | 666 +++++
src/liburing/test/ring-leak.c | 283 ++
src/liburing/test/ring-leak2.c | 249 ++
src/liburing/test/ringbuf-read.c | 201 ++
src/liburing/test/ringbuf-status.c | 246 ++
src/liburing/test/rsrc_tags.c | 514 ++++
src/liburing/test/runtests-loop.sh | 16 +
src/liburing/test/runtests-quiet.sh | 11 +
src/liburing/test/runtests.sh | 183 ++
src/liburing/test/rw_merge_test.c | 98 +
src/liburing/test/self.c | 91 +
src/liburing/test/send-zerocopy.c | 952 +++++++
src/liburing/test/send_recv.c | 412 +++
src/liburing/test/send_recvmsg.c | 444 +++
src/liburing/test/sendmsg_iov_clean.c | 216 ++
src/liburing/test/shared-wq.c | 84 +
src/liburing/test/short-read.c | 76 +
src/liburing/test/shutdown.c | 155 +
src/liburing/test/sigfd-deadlock.c | 88 +
src/liburing/test/single-issuer.c | 169 ++
src/liburing/test/skip-cqe.c | 428 +++
src/liburing/test/socket-getsetsock-cmd.c | 346 +++
src/liburing/test/socket-io-cmd.c | 237 ++
src/liburing/test/socket-nb.c | 147 +
src/liburing/test/socket-rw-eagain.c | 139 +
src/liburing/test/socket-rw-offset.c | 139 +
src/liburing/test/socket-rw.c | 127 +
src/liburing/test/socket.c | 451 +++
src/liburing/test/splice.c | 514 ++++
src/liburing/test/sq-full-cpp.cc | 45 +
src/liburing/test/sq-full.c | 45 +
src/liburing/test/sq-poll-dup.c | 211 ++
src/liburing/test/sq-poll-kthread.c | 169 ++
src/liburing/test/sq-poll-share.c | 140 +
src/liburing/test/sq-space_left.c | 159 ++
src/liburing/test/sqpoll-disable-exit.c | 204 ++
src/liburing/test/sqpoll-exec.c | 132 +
src/liburing/test/sqpoll-exit-hang.c | 54 +
src/liburing/test/sqpoll-sleep.c | 76 +
src/liburing/test/sqwait.c | 134 +
src/liburing/test/statx.c | 261 ++
src/liburing/test/stdout.c | 234 ++
src/liburing/test/submit-and-wait.c | 84 +
src/liburing/test/submit-link-fail.c | 156 +
src/liburing/test/submit-reuse.c | 215 ++
src/liburing/test/symlink.c | 128 +
src/liburing/test/sync-cancel.c | 269 ++
src/liburing/test/teardowns.c | 58 +
src/liburing/test/test.h | 36 +
src/liburing/test/thread-exit.c | 148 +
src/liburing/test/timeout-new.c | 231 ++
src/liburing/test/timeout.c | 1987 +++++++++++++
src/liburing/test/timerfd-short-read.c | 81 +
src/liburing/test/timestamp.c | 380 +++
src/liburing/test/truncate.c | 186 ++
src/liburing/test/tty-write-dpoll.c | 60 +
src/liburing/test/unlink.c | 205 ++
src/liburing/test/uring_cmd_ublk.c | 1252 ++++++++
src/liburing/test/vec-regbuf.c | 609 ++++
src/liburing/test/version.c | 25 +
src/liburing/test/wait-timeout.c | 287 ++
src/liburing/test/waitid.c | 427 +++
src/liburing/test/wakeup-hang.c | 162 ++
src/liburing/test/wq-aff.c | 185 ++
src/liburing/test/xattr.c | 442 +++
.../xfail_prep_link_timeout_out_of_scope.c | 46 +
.../xfail_register_buffers_out_of_scope.c | 51 +
src/liburing/test/zcrx.c | 928 ++++++
502 files changed, 89312 insertions(+), 7 deletions(-)
create mode 100644 src/liburing/.github/actions/codespell/stopwords
create mode 100644 src/liburing/.github/pull_request_template.md
create mode 100644 src/liburing/.github/workflows/ci.yml
create mode 100644 src/liburing/.gitignore
create mode 100644 src/liburing/CHANGELOG
create mode 100644 src/liburing/CITATION.cff
create mode 100644 src/liburing/CONTRIBUTING.md
create mode 100644 src/liburing/COPYING
create mode 100644 src/liburing/COPYING.GPL
create mode 100644 src/liburing/LICENSE
create mode 100644 src/liburing/Makefile
create mode 100644 src/liburing/Makefile.common
create mode 100644 src/liburing/Makefile.quiet
create mode 100644 src/liburing/README
create mode 100644 src/liburing/SECURITY.md
create mode 100755 src/liburing/configure
create mode 100644 src/liburing/debian/README.Debian
create mode 100644 src/liburing/debian/changelog
create mode 100644 src/liburing/debian/control
create mode 100644 src/liburing/debian/copyright
create mode 100644 src/liburing/debian/liburing-dev.install
create mode 100644 src/liburing/debian/liburing-dev.manpages
create mode 100644 src/liburing/debian/liburing2.install
create mode 100644 src/liburing/debian/liburing2.symbols
create mode 100644 src/liburing/debian/patches/series
create mode 100755 src/liburing/debian/rules
create mode 100644 src/liburing/debian/source/format
create mode 100644 src/liburing/debian/source/local-options
create mode 100644 src/liburing/debian/source/options
create mode 100644 src/liburing/debian/watch
create mode 100644 src/liburing/examples/Makefile
create mode 100644 src/liburing/examples/helpers.c
create mode 100644 src/liburing/examples/helpers.h
create mode 100644 src/liburing/examples/io_uring-close-test.c
create mode 100644 src/liburing/examples/io_uring-cp.c
create mode 100644 src/liburing/examples/io_uring-test.c
create mode 100644 src/liburing/examples/io_uring-udp.c
create mode 100644 src/liburing/examples/kdigest.c
create mode 100644 src/liburing/examples/link-cp.c
create mode 100644 src/liburing/examples/napi-busy-poll-client.c
create mode 100644 src/liburing/examples/napi-busy-poll-server.c
create mode 100644 src/liburing/examples/poll-bench.c
create mode 100644 src/liburing/examples/proxy.c
create mode 100644 src/liburing/examples/proxy.h
create mode 100644 src/liburing/examples/reg-wait.c
create mode 100644 src/liburing/examples/rsrc-update-bench.c
create mode 100644 src/liburing/examples/send-zerocopy.c
create mode 100644 src/liburing/examples/ucontext-cp.c
create mode 100644 src/liburing/examples/zcrx.c
create mode 100644 src/liburing/liburing-ffi.pc.in
create mode 100644 src/liburing/liburing.pc.in
create mode 100644 src/liburing/liburing.spec
create mode 100755 src/liburing/make-debs.sh
create mode 120000 src/liburing/man/IO_URING_CHECK_VERSION.3
create mode 120000 src/liburing/man/IO_URING_VERSION_MAJOR.3
create mode 120000 src/liburing/man/IO_URING_VERSION_MINOR.3
create mode 120000 src/liburing/man/__io_uring_buf_ring_cq_advance.3
create mode 100644 src/liburing/man/io_uring.7
create mode 100644 src/liburing/man/io_uring_buf_ring_add.3
create mode 100644 src/liburing/man/io_uring_buf_ring_advance.3
create mode 100644 src/liburing/man/io_uring_buf_ring_available.3
create mode 100644 src/liburing/man/io_uring_buf_ring_cq_advance.3
create mode 100644 src/liburing/man/io_uring_buf_ring_init.3
create mode 100644 src/liburing/man/io_uring_buf_ring_mask.3
create mode 100644 src/liburing/man/io_uring_check_version.3
create mode 100644 src/liburing/man/io_uring_clone_buffers.3
create mode 120000 src/liburing/man/io_uring_clone_buffers_offset.3
create mode 100644 src/liburing/man/io_uring_close_ring_fd.3
create mode 100644 src/liburing/man/io_uring_cq_advance.3
create mode 100644 src/liburing/man/io_uring_cq_has_overflow.3
create mode 100644 src/liburing/man/io_uring_cq_ready.3
create mode 100644 src/liburing/man/io_uring_cqe_get_data.3
create mode 120000 src/liburing/man/io_uring_cqe_get_data64.3
create mode 100644 src/liburing/man/io_uring_cqe_seen.3
create mode 100644 src/liburing/man/io_uring_enable_rings.3
create mode 100644 src/liburing/man/io_uring_enter.2
create mode 120000 src/liburing/man/io_uring_enter2.2
create mode 100644 src/liburing/man/io_uring_for_each_cqe.3
create mode 100644 src/liburing/man/io_uring_free_buf_ring.3
create mode 100644 src/liburing/man/io_uring_free_probe.3
create mode 100644 src/liburing/man/io_uring_free_reg_wait.3
create mode 100644 src/liburing/man/io_uring_get_events.3
create mode 100644 src/liburing/man/io_uring_get_probe.3
create mode 100644 src/liburing/man/io_uring_get_sqe.3
create mode 120000 src/liburing/man/io_uring_major_version.3
create mode 120000 src/liburing/man/io_uring_minor_version.3
create mode 100644 src/liburing/man/io_uring_opcode_supported.3
create mode 120000 src/liburing/man/io_uring_peek_batch_cqe.3
create mode 100644 src/liburing/man/io_uring_peek_cqe.3
create mode 100644 src/liburing/man/io_uring_prep_accept.3
create mode 120000 src/liburing/man/io_uring_prep_accept_direct.3
create mode 100644 src/liburing/man/io_uring_prep_bind.3
create mode 100644 src/liburing/man/io_uring_prep_cancel.3
create mode 120000 src/liburing/man/io_uring_prep_cancel64.3
create mode 120000 src/liburing/man/io_uring_prep_cancel_fd.3
create mode 100644 src/liburing/man/io_uring_prep_close.3
create mode 120000 src/liburing/man/io_uring_prep_close_direct.3
create mode 100644 src/liburing/man/io_uring_prep_cmd.3
create mode 100644 src/liburing/man/io_uring_prep_cmd_discard.3
create mode 100644 src/liburing/man/io_uring_prep_connect.3
create mode 100644 src/liburing/man/io_uring_prep_epoll_wait.3
create mode 100644 src/liburing/man/io_uring_prep_fadvise.3
create mode 120000 src/liburing/man/io_uring_prep_fadvise64.3
create mode 100644 src/liburing/man/io_uring_prep_fallocate.3
create mode 120000 src/liburing/man/io_uring_prep_fgetxattr.3
create mode 100644 src/liburing/man/io_uring_prep_files_update.3
create mode 100644 src/liburing/man/io_uring_prep_fixed_fd_install.3
create mode 120000 src/liburing/man/io_uring_prep_fsetxattr.3
create mode 100644 src/liburing/man/io_uring_prep_fsync.3
create mode 100644 src/liburing/man/io_uring_prep_ftruncate.3
create mode 100644 src/liburing/man/io_uring_prep_futex_wait.3
create mode 100644 src/liburing/man/io_uring_prep_futex_waitv.3
create mode 100644 src/liburing/man/io_uring_prep_futex_wake.3
create mode 100644 src/liburing/man/io_uring_prep_getxattr.3
create mode 120000 src/liburing/man/io_uring_prep_link.3
create mode 100644 src/liburing/man/io_uring_prep_link_timeout.3
create mode 100644 src/liburing/man/io_uring_prep_linkat.3
create mode 100644 src/liburing/man/io_uring_prep_listen.3
create mode 100644 src/liburing/man/io_uring_prep_madvise.3
create mode 120000 src/liburing/man/io_uring_prep_madvise64.3
create mode 120000 src/liburing/man/io_uring_prep_mkdir.3
create mode 100644 src/liburing/man/io_uring_prep_mkdirat.3
create mode 100644 src/liburing/man/io_uring_prep_msg_ring.3
create mode 120000 src/liburing/man/io_uring_prep_msg_ring_cqe_flags.3
create mode 100644 src/liburing/man/io_uring_prep_msg_ring_fd.3
create mode 120000 src/liburing/man/io_uring_prep_msg_ring_fd_alloc.3
create mode 120000 src/liburing/man/io_uring_prep_multishot_accept.3
create mode 120000 src/liburing/man/io_uring_prep_multishot_accept_direct.3
create mode 100644 src/liburing/man/io_uring_prep_nop.3
create mode 120000 src/liburing/man/io_uring_prep_open.3
create mode 120000 src/liburing/man/io_uring_prep_open_direct.3
create mode 100644 src/liburing/man/io_uring_prep_openat.3
create mode 100644 src/liburing/man/io_uring_prep_openat2.3
create mode 120000 src/liburing/man/io_uring_prep_openat2_direct.3
create mode 120000 src/liburing/man/io_uring_prep_openat_direct.3
create mode 100644 src/liburing/man/io_uring_prep_poll_add.3
create mode 120000 src/liburing/man/io_uring_prep_poll_multishot.3
create mode 100644 src/liburing/man/io_uring_prep_poll_remove.3
create mode 100644 src/liburing/man/io_uring_prep_poll_update.3
create mode 100644 src/liburing/man/io_uring_prep_provide_buffers.3
create mode 100644 src/liburing/man/io_uring_prep_read.3
create mode 100644 src/liburing/man/io_uring_prep_read_fixed.3
create mode 100644 src/liburing/man/io_uring_prep_read_multishot.3
create mode 100644 src/liburing/man/io_uring_prep_readv.3
create mode 100644 src/liburing/man/io_uring_prep_readv2.3
create mode 100644 src/liburing/man/io_uring_prep_recv.3
create mode 120000 src/liburing/man/io_uring_prep_recv_multishot.3
create mode 100644 src/liburing/man/io_uring_prep_recvmsg.3
create mode 120000 src/liburing/man/io_uring_prep_recvmsg_multishot.3
create mode 100644 src/liburing/man/io_uring_prep_remove_buffers.3
create mode 120000 src/liburing/man/io_uring_prep_rename.3
create mode 100644 src/liburing/man/io_uring_prep_renameat.3
create mode 100644 src/liburing/man/io_uring_prep_send.3
create mode 120000 src/liburing/man/io_uring_prep_send_bundle.3
create mode 100644 src/liburing/man/io_uring_prep_send_set_addr.3
create mode 100644 src/liburing/man/io_uring_prep_send_zc.3
create mode 120000 src/liburing/man/io_uring_prep_send_zc_fixed.3
create mode 100644 src/liburing/man/io_uring_prep_sendmsg.3
create mode 120000 src/liburing/man/io_uring_prep_sendmsg_zc.3
create mode 120000 src/liburing/man/io_uring_prep_sendto.3
create mode 100644 src/liburing/man/io_uring_prep_setxattr.3
create mode 100644 src/liburing/man/io_uring_prep_shutdown.3
create mode 100644 src/liburing/man/io_uring_prep_socket.3
create mode 120000 src/liburing/man/io_uring_prep_socket_direct.3
create mode 120000 src/liburing/man/io_uring_prep_socket_direct_alloc.3
create mode 100644 src/liburing/man/io_uring_prep_splice.3
create mode 100644 src/liburing/man/io_uring_prep_statx.3
create mode 120000 src/liburing/man/io_uring_prep_symlink.3
create mode 100644 src/liburing/man/io_uring_prep_symlinkat.3
create mode 100644 src/liburing/man/io_uring_prep_sync_file_range.3
create mode 100644 src/liburing/man/io_uring_prep_tee.3
create mode 100644 src/liburing/man/io_uring_prep_timeout.3
create mode 120000 src/liburing/man/io_uring_prep_timeout_remove.3
create mode 100644 src/liburing/man/io_uring_prep_timeout_update.3
create mode 120000 src/liburing/man/io_uring_prep_unlink.3
create mode 100644 src/liburing/man/io_uring_prep_unlinkat.3
create mode 100644 src/liburing/man/io_uring_prep_waitid.3
create mode 100644 src/liburing/man/io_uring_prep_write.3
create mode 100644 src/liburing/man/io_uring_prep_write_fixed.3
create mode 100644 src/liburing/man/io_uring_prep_writev.3
create mode 100644 src/liburing/man/io_uring_prep_writev2.3
create mode 100644 src/liburing/man/io_uring_queue_exit.3
create mode 100644 src/liburing/man/io_uring_queue_init.3
create mode 120000 src/liburing/man/io_uring_queue_init_mem.3
create mode 120000 src/liburing/man/io_uring_queue_init_params.3
create mode 120000 src/liburing/man/io_uring_recvmsg_cmsg_firsthdr.3
create mode 120000 src/liburing/man/io_uring_recvmsg_cmsg_nexthdr.3
create mode 120000 src/liburing/man/io_uring_recvmsg_name.3
create mode 100644 src/liburing/man/io_uring_recvmsg_out.3
create mode 120000 src/liburing/man/io_uring_recvmsg_payload.3
create mode 120000 src/liburing/man/io_uring_recvmsg_payload_length.3
create mode 120000 src/liburing/man/io_uring_recvmsg_validate.3
create mode 100644 src/liburing/man/io_uring_register.2
create mode 100644 src/liburing/man/io_uring_register_buf_ring.3
create mode 100644 src/liburing/man/io_uring_register_buffers.3
create mode 120000 src/liburing/man/io_uring_register_buffers_sparse.3
create mode 120000 src/liburing/man/io_uring_register_buffers_tags.3
create mode 120000 src/liburing/man/io_uring_register_buffers_update_tag.3
create mode 100644 src/liburing/man/io_uring_register_clock.3
create mode 100644 src/liburing/man/io_uring_register_eventfd.3
create mode 120000 src/liburing/man/io_uring_register_eventfd_async.3
create mode 100644 src/liburing/man/io_uring_register_file_alloc_range.3
create mode 100644 src/liburing/man/io_uring_register_files.3
create mode 120000 src/liburing/man/io_uring_register_files_sparse.3
create mode 120000 src/liburing/man/io_uring_register_files_tags.3
create mode 120000 src/liburing/man/io_uring_register_files_update.3
create mode 120000 src/liburing/man/io_uring_register_files_update_tag.3
create mode 100644 src/liburing/man/io_uring_register_iowq_aff.3
create mode 100644 src/liburing/man/io_uring_register_iowq_max_workers.3
create mode 100644 src/liburing/man/io_uring_register_napi.3
create mode 100644 src/liburing/man/io_uring_register_reg_wait.3
create mode 100644 src/liburing/man/io_uring_register_ring_fd.3
create mode 100644 src/liburing/man/io_uring_register_sync_cancel.3
create mode 100644 src/liburing/man/io_uring_register_sync_msg.3
create mode 100644 src/liburing/man/io_uring_resize_rings.3
create mode 100644 src/liburing/man/io_uring_setup.2
create mode 100644 src/liburing/man/io_uring_setup_buf_ring.3
create mode 100644 src/liburing/man/io_uring_setup_reg_wait.3
create mode 100644 src/liburing/man/io_uring_sq_ready.3
create mode 100644 src/liburing/man/io_uring_sq_space_left.3
create mode 100644 src/liburing/man/io_uring_sqe_set_buf_group.3
create mode 100644 src/liburing/man/io_uring_sqe_set_data.3
create mode 120000 src/liburing/man/io_uring_sqe_set_data64.3
create mode 100644 src/liburing/man/io_uring_sqe_set_flags.3
create mode 100644 src/liburing/man/io_uring_sqring_wait.3
create mode 100644 src/liburing/man/io_uring_submit.3
create mode 100644 src/liburing/man/io_uring_submit_and_get_events.3
create mode 100644 src/liburing/man/io_uring_submit_and_wait.3
create mode 100644 src/liburing/man/io_uring_submit_and_wait_min_timeout.3
create mode 100644 src/liburing/man/io_uring_submit_and_wait_reg.3
create mode 100644 src/liburing/man/io_uring_submit_and_wait_timeout.3
create mode 100644 src/liburing/man/io_uring_unregister_buf_ring.3
create mode 100644 src/liburing/man/io_uring_unregister_buffers.3
create mode 120000 src/liburing/man/io_uring_unregister_eventfd.3
create mode 100644 src/liburing/man/io_uring_unregister_files.3
create mode 120000 src/liburing/man/io_uring_unregister_iowq_aff.3
create mode 100644 src/liburing/man/io_uring_unregister_napi.3
create mode 100644 src/liburing/man/io_uring_unregister_ring_fd.3
create mode 100644 src/liburing/man/io_uring_wait_cqe.3
create mode 100644 src/liburing/man/io_uring_wait_cqe_nr.3
create mode 100644 src/liburing/man/io_uring_wait_cqe_timeout.3
create mode 100644 src/liburing/man/io_uring_wait_cqes.3
create mode 100644 src/liburing/man/io_uring_wait_cqes_min_timeout.3
create mode 100644 src/liburing/src/Makefile
create mode 100644 src/liburing/src/arch/aarch64/lib.h
create mode 100644 src/liburing/src/arch/aarch64/syscall.h
create mode 100644 src/liburing/src/arch/generic/lib.h
create mode 100644 src/liburing/src/arch/generic/syscall.h
create mode 100644 src/liburing/src/arch/riscv64/lib.h
create mode 100644 src/liburing/src/arch/riscv64/syscall.h
create mode 100644 src/liburing/src/arch/syscall-defs.h
create mode 100644 src/liburing/src/arch/x86/lib.h
create mode 100644 src/liburing/src/arch/x86/syscall.h
create mode 100644 src/liburing/src/ffi.c
create mode 100644 src/liburing/src/include/liburing.h
create mode 100644 src/liburing/src/include/liburing/barrier.h
create mode 100644 src/liburing/src/include/liburing/io_uring.h
create mode 100644 src/liburing/src/include/liburing/sanitize.h
create mode 100644 src/liburing/src/int_flags.h
create mode 100644 src/liburing/src/lib.h
create mode 100644 src/liburing/src/liburing-ffi.map
create mode 100644 src/liburing/src/liburing.map
create mode 100644 src/liburing/src/nolibc.c
create mode 100644 src/liburing/src/queue.c
create mode 100644 src/liburing/src/register.c
create mode 100644 src/liburing/src/sanitize.c
create mode 100644 src/liburing/src/setup.c
create mode 100644 src/liburing/src/setup.h
create mode 100644 src/liburing/src/syscall.c
create mode 100644 src/liburing/src/syscall.h
create mode 100644 src/liburing/src/version.c
create mode 100644 src/liburing/test/232c93d07b74.c
create mode 100644 src/liburing/test/35fa71a030ca.c
create mode 100644 src/liburing/test/500f9fbadef8.c
create mode 100644 src/liburing/test/7ad0e4b2f83c.c
create mode 100644 src/liburing/test/8a9973408177.c
create mode 100644 src/liburing/test/917257daa0fe.c
create mode 100644 src/liburing/test/Makefile
create mode 100644 src/liburing/test/a0908ae19763.c
create mode 100644 src/liburing/test/a4c0b3decb33.c
create mode 100644 src/liburing/test/accept-link.c
create mode 100644 src/liburing/test/accept-non-empty.c
create mode 100644 src/liburing/test/accept-reuse.c
create mode 100644 src/liburing/test/accept-test.c
create mode 100644 src/liburing/test/accept.c
create mode 100644 src/liburing/test/across-fork.c
create mode 100644 src/liburing/test/b19062a56726.c
create mode 100644 src/liburing/test/b5837bd5311d.c
create mode 100644 src/liburing/test/bind-listen.c
create mode 100644 src/liburing/test/buf-ring-nommap.c
create mode 100644 src/liburing/test/buf-ring-put.c
create mode 100644 src/liburing/test/buf-ring.c
create mode 100644 src/liburing/test/ce593a6c480a.c
create mode 100644 src/liburing/test/close-opath.c
create mode 100644 src/liburing/test/cmd-discard.c
create mode 100644 src/liburing/test/config
create mode 100644 src/liburing/test/conn-unreach.c
create mode 100644 src/liburing/test/connect-rep.c
create mode 100644 src/liburing/test/connect.c
create mode 100644 src/liburing/test/coredump.c
create mode 100644 src/liburing/test/cq-full.c
create mode 100644 src/liburing/test/cq-overflow.c
create mode 100644 src/liburing/test/cq-peek-batch.c
create mode 100644 src/liburing/test/cq-ready.c
create mode 100644 src/liburing/test/cq-size.c
create mode 100644 src/liburing/test/d4ae271dfaae.c
create mode 100644 src/liburing/test/d77a67ed5f27.c
create mode 100644 src/liburing/test/defer-taskrun.c
create mode 100644 src/liburing/test/defer-tw-timeout.c
create mode 100644 src/liburing/test/defer.c
create mode 100644 src/liburing/test/double-poll-crash.c
create mode 100644 src/liburing/test/drop-submit.c
create mode 100644 src/liburing/test/eeed8b54e0df.c
create mode 100644 src/liburing/test/empty-eownerdead.c
create mode 100644 src/liburing/test/eploop.c
create mode 100644 src/liburing/test/epwait.c
create mode 100644 src/liburing/test/eventfd-disable.c
create mode 100644 src/liburing/test/eventfd-reg.c
create mode 100644 src/liburing/test/eventfd-ring.c
create mode 100644 src/liburing/test/eventfd.c
create mode 100644 src/liburing/test/evfd-short-read.c
create mode 100644 src/liburing/test/evloop.c
create mode 100644 src/liburing/test/exec-target.c
create mode 100644 src/liburing/test/exit-no-cleanup.c
create mode 100644 src/liburing/test/fadvise.c
create mode 100644 src/liburing/test/fallocate.c
create mode 100644 src/liburing/test/fc2a85cb02ef.c
create mode 100644 src/liburing/test/fd-install.c
create mode 100644 src/liburing/test/fd-pass.c
create mode 100644 src/liburing/test/fdinfo-sqpoll.c
create mode 100644 src/liburing/test/fdinfo.c
create mode 100644 src/liburing/test/fifo-nonblock-read.c
create mode 100644 src/liburing/test/file-exit-unreg.c
create mode 100644 src/liburing/test/file-register.c
create mode 100644 src/liburing/test/file-update.c
create mode 100644 src/liburing/test/file-verify.c
create mode 100644 src/liburing/test/files-exit-hang-poll.c
create mode 100644 src/liburing/test/files-exit-hang-timeout.c
create mode 100644 src/liburing/test/fixed-buf-iter.c
create mode 100644 src/liburing/test/fixed-buf-merge.c
create mode 100644 src/liburing/test/fixed-hugepage.c
create mode 100644 src/liburing/test/fixed-link.c
create mode 100644 src/liburing/test/fixed-reuse.c
create mode 100644 src/liburing/test/fixed-seg.c
create mode 100644 src/liburing/test/fpos.c
create mode 100644 src/liburing/test/fsnotify.c
create mode 100644 src/liburing/test/fsync.c
create mode 100644 src/liburing/test/futex-kill.c
create mode 100644 src/liburing/test/futex.c
create mode 100644 src/liburing/test/hardlink.c
create mode 100644 src/liburing/test/helpers.c
create mode 100644 src/liburing/test/helpers.h
create mode 100644 src/liburing/test/ignore-single-mmap.c
create mode 100644 src/liburing/test/init-mem.c
create mode 100644 src/liburing/test/io-cancel.c
create mode 100644 src/liburing/test/io_uring_enter.c
create mode 100644 src/liburing/test/io_uring_passthrough.c
create mode 100644 src/liburing/test/io_uring_register.c
create mode 100644 src/liburing/test/io_uring_setup.c
create mode 100644 src/liburing/test/iopoll-leak.c
create mode 100644 src/liburing/test/iopoll-overflow.c
create mode 100644 src/liburing/test/iopoll.c
create mode 100644 src/liburing/test/iowait.c
create mode 100644 src/liburing/test/kallsyms.c
create mode 100644 src/liburing/test/lfs-openat-write.c
create mode 100644 src/liburing/test/lfs-openat.c
create mode 100644 src/liburing/test/link-timeout.c
create mode 100644 src/liburing/test/link.c
create mode 100644 src/liburing/test/link_drain.c
create mode 100644 src/liburing/test/linked-defer-close.c
create mode 100644 src/liburing/test/madvise.c
create mode 100644 src/liburing/test/min-timeout-wait.c
create mode 100644 src/liburing/test/min-timeout.c
create mode 100644 src/liburing/test/mkdir.c
create mode 100644 src/liburing/test/msg-ring-fd.c
create mode 100644 src/liburing/test/msg-ring-flags.c
create mode 100644 src/liburing/test/msg-ring-overflow.c
create mode 100644 src/liburing/test/msg-ring.c
create mode 100644 src/liburing/test/multicqes_drain.c
create mode 100644 src/liburing/test/napi-test.c
create mode 100644 src/liburing/test/napi-test.sh
create mode 100644 src/liburing/test/no-mmap-inval.c
create mode 100644 src/liburing/test/nolibc.c
create mode 100644 src/liburing/test/nop-all-sizes.c
create mode 100644 src/liburing/test/nop.c
create mode 100644 src/liburing/test/nvme.h
create mode 100644 src/liburing/test/ooo-file-unreg.c
create mode 100644 src/liburing/test/open-close.c
create mode 100644 src/liburing/test/open-direct-link.c
create mode 100644 src/liburing/test/open-direct-pick.c
create mode 100644 src/liburing/test/openat2.c
create mode 100644 src/liburing/test/personality.c
create mode 100644 src/liburing/test/pipe-bug.c
create mode 100644 src/liburing/test/pipe-eof.c
create mode 100644 src/liburing/test/pipe-reuse.c
create mode 100644 src/liburing/test/poll-cancel-all.c
create mode 100644 src/liburing/test/poll-cancel-ton.c
create mode 100644 src/liburing/test/poll-cancel.c
create mode 100644 src/liburing/test/poll-link.c
create mode 100644 src/liburing/test/poll-many.c
create mode 100644 src/liburing/test/poll-mshot-overflow.c
create mode 100644 src/liburing/test/poll-mshot-update.c
create mode 100644 src/liburing/test/poll-race-mshot.c
create mode 100644 src/liburing/test/poll-race.c
create mode 100644 src/liburing/test/poll-ring.c
create mode 100644 src/liburing/test/poll-v-poll.c
create mode 100644 src/liburing/test/poll.c
create mode 100644 src/liburing/test/pollfree.c
create mode 100644 src/liburing/test/probe.c
create mode 100644 src/liburing/test/read-before-exit.c
create mode 100644 src/liburing/test/read-inc-file.c
create mode 100644 src/liburing/test/read-mshot-empty.c
create mode 100644 src/liburing/test/read-mshot-stdin.c
create mode 100644 src/liburing/test/read-mshot.c
create mode 100644 src/liburing/test/read-write.c
create mode 100644 src/liburing/test/recv-bundle-short-ooo.c
create mode 100644 src/liburing/test/recv-inc-ooo.c
create mode 100644 src/liburing/test/recv-msgall-stream.c
create mode 100644 src/liburing/test/recv-msgall.c
create mode 100644 src/liburing/test/recv-mshot-fair.c
create mode 100644 src/liburing/test/recv-multishot.c
create mode 100644 src/liburing/test/recvsend_bundle-inc.c
create mode 100644 src/liburing/test/recvsend_bundle.c
create mode 100644 src/liburing/test/reg-fd-only.c
create mode 100644 src/liburing/test/reg-hint.c
create mode 100644 src/liburing/test/reg-reg-ring.c
create mode 100644 src/liburing/test/reg-wait.c
create mode 100644 src/liburing/test/regbuf-clone.c
create mode 100644 src/liburing/test/regbuf-merge.c
create mode 100644 src/liburing/test/register-restrictions.c
create mode 100644 src/liburing/test/rename.c
create mode 100644 src/liburing/test/resize-rings.c
create mode 100644 src/liburing/test/ring-leak.c
create mode 100644 src/liburing/test/ring-leak2.c
create mode 100644 src/liburing/test/ringbuf-read.c
create mode 100644 src/liburing/test/ringbuf-status.c
create mode 100644 src/liburing/test/rsrc_tags.c
create mode 100755 src/liburing/test/runtests-loop.sh
create mode 100755 src/liburing/test/runtests-quiet.sh
create mode 100755 src/liburing/test/runtests.sh
create mode 100644 src/liburing/test/rw_merge_test.c
create mode 100644 src/liburing/test/self.c
create mode 100644 src/liburing/test/send-zerocopy.c
create mode 100644 src/liburing/test/send_recv.c
create mode 100644 src/liburing/test/send_recvmsg.c
create mode 100644 src/liburing/test/sendmsg_iov_clean.c
create mode 100644 src/liburing/test/shared-wq.c
create mode 100644 src/liburing/test/short-read.c
create mode 100644 src/liburing/test/shutdown.c
create mode 100644 src/liburing/test/sigfd-deadlock.c
create mode 100644 src/liburing/test/single-issuer.c
create mode 100644 src/liburing/test/skip-cqe.c
create mode 100644 src/liburing/test/socket-getsetsock-cmd.c
create mode 100644 src/liburing/test/socket-io-cmd.c
create mode 100644 src/liburing/test/socket-nb.c
create mode 100644 src/liburing/test/socket-rw-eagain.c
create mode 100644 src/liburing/test/socket-rw-offset.c
create mode 100644 src/liburing/test/socket-rw.c
create mode 100644 src/liburing/test/socket.c
create mode 100644 src/liburing/test/splice.c
create mode 100644 src/liburing/test/sq-full-cpp.cc
create mode 100644 src/liburing/test/sq-full.c
create mode 100644 src/liburing/test/sq-poll-dup.c
create mode 100644 src/liburing/test/sq-poll-kthread.c
create mode 100644 src/liburing/test/sq-poll-share.c
create mode 100644 src/liburing/test/sq-space_left.c
create mode 100644 src/liburing/test/sqpoll-disable-exit.c
create mode 100644 src/liburing/test/sqpoll-exec.c
create mode 100644 src/liburing/test/sqpoll-exit-hang.c
create mode 100644 src/liburing/test/sqpoll-sleep.c
create mode 100644 src/liburing/test/sqwait.c
create mode 100644 src/liburing/test/statx.c
create mode 100644 src/liburing/test/stdout.c
create mode 100644 src/liburing/test/submit-and-wait.c
create mode 100644 src/liburing/test/submit-link-fail.c
create mode 100644 src/liburing/test/submit-reuse.c
create mode 100644 src/liburing/test/symlink.c
create mode 100644 src/liburing/test/sync-cancel.c
create mode 100644 src/liburing/test/teardowns.c
create mode 100644 src/liburing/test/test.h
create mode 100644 src/liburing/test/thread-exit.c
create mode 100644 src/liburing/test/timeout-new.c
create mode 100644 src/liburing/test/timeout.c
create mode 100644 src/liburing/test/timerfd-short-read.c
create mode 100644 src/liburing/test/timestamp.c
create mode 100644 src/liburing/test/truncate.c
create mode 100644 src/liburing/test/tty-write-dpoll.c
create mode 100644 src/liburing/test/unlink.c
create mode 100644 src/liburing/test/uring_cmd_ublk.c
create mode 100644 src/liburing/test/vec-regbuf.c
create mode 100644 src/liburing/test/version.c
create mode 100644 src/liburing/test/wait-timeout.c
create mode 100644 src/liburing/test/waitid.c
create mode 100644 src/liburing/test/wakeup-hang.c
create mode 100644 src/liburing/test/wq-aff.c
create mode 100644 src/liburing/test/xattr.c
create mode 100644 src/liburing/test/xfail_prep_link_timeout_out_of_scope.c
create mode 100644 src/liburing/test/xfail_register_buffers_out_of_scope.c
create mode 100644 src/liburing/test/zcrx.c
base-commit: 06fa2ea2ba4acee27d03b7f467012b403df1f48c
--
Ahmad Gani
^ permalink raw reply [flat|nested] 11+ messages in thread
* [PATCH gwproxy v1 2/3] io_uring: Add macro guard
2025-07-29 2:48 [PATCH gwproxy v1 0/3] Minor changes and fixes Ahmad Gani
@ 2025-07-29 2:48 ` Ahmad Gani
2025-07-29 2:48 ` [PATCH gwproxy v1 3/3] io_uring: Rename GWP_CONN_FLAG_IS_SHUTDOWN to GWP_CONN_FLAG_IS_CANCEL Ahmad Gani
2025-07-29 2:53 ` [PATCH gwproxy v1 0/3] Minor changes and fixes Ammar Faizi
2 siblings, 0 replies; 11+ messages in thread
From: Ahmad Gani @ 2025-07-29 2:48 UTC (permalink / raw)
To: Ammar Faizi; +Cc: Ahmad Gani, GNU/Weeb Mailing List
To prevent linter error from text editor such as VSCode.
Signed-off-by: Ahmad Gani <reyuki@gnuweeb.org>
---
src/gwproxy/ev/io_uring.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/src/gwproxy/ev/io_uring.c b/src/gwproxy/ev/io_uring.c
index 5b8785ade49f..e7696efbf4aa 100644
--- a/src/gwproxy/ev/io_uring.c
+++ b/src/gwproxy/ev/io_uring.c
@@ -2,6 +2,9 @@
/*
* Copyright (C) 2025 Ammar Faizi <ammarfaizi2@gnuweeb.org>
*/
+
+#ifdef CONFIG_IO_URING
+
#ifndef _GNU_SOURCE
#define _GNU_SOURCE
#endif
@@ -764,3 +767,5 @@ void gwp_ctx_signal_all_io_uring(struct gwp_ctx *ctx)
io_uring_submit_eintr(&we->iou->ring, 8);
}
+
+#endif // CONFIG_IO_URING
--
Ahmad Gani
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [PATCH gwproxy v1 3/3] io_uring: Rename GWP_CONN_FLAG_IS_SHUTDOWN to GWP_CONN_FLAG_IS_CANCEL
2025-07-29 2:48 [PATCH gwproxy v1 0/3] Minor changes and fixes Ahmad Gani
2025-07-29 2:48 ` [PATCH gwproxy v1 2/3] io_uring: Add macro guard Ahmad Gani
@ 2025-07-29 2:48 ` Ahmad Gani
2025-07-29 2:53 ` [PATCH gwproxy v1 0/3] Minor changes and fixes Ammar Faizi
2 siblings, 0 replies; 11+ messages in thread
From: Ahmad Gani @ 2025-07-29 2:48 UTC (permalink / raw)
To: Ammar Faizi; +Cc: Ahmad Gani, GNU/Weeb Mailing List
A previous commit forgot to replace GWP_CONN_FLAG_IS_SHUTDOWN and leading to
build error on debug mode, it wasn't detected on release mode.
Fixes: 06fa2ea2ba4a ("io_uring: Replace prep_shutdown() with prep_cancel()")
Signed-off-by: Ahmad Gani <reyuki@gnuweeb.org>
---
src/gwproxy/ev/io_uring.c | 8 ++++----
src/gwproxy/gwproxy.h | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/src/gwproxy/ev/io_uring.c b/src/gwproxy/ev/io_uring.c
index e7696efbf4aa..ca7178476f9f 100644
--- a/src/gwproxy/ev/io_uring.c
+++ b/src/gwproxy/ev/io_uring.c
@@ -318,7 +318,7 @@ static void shutdown_gcp(struct gwp_wrk *w, struct gwp_conn_pair *gcp)
struct gwp_ctx *ctx = w->ctx;
struct io_uring_sqe *s;
- if (gcp->flags & GWP_CONN_FLAG_IS_SHUTDOWN)
+ if (gcp->flags & GWP_CONN_FLAG_IS_CANCEL)
return;
if (gcp->target.fd >= 0) {
@@ -339,7 +339,7 @@ static void shutdown_gcp(struct gwp_wrk *w, struct gwp_conn_pair *gcp)
get_gcp(gcp);
}
- gcp->flags |= GWP_CONN_FLAG_IS_SHUTDOWN;
+ gcp->flags |= GWP_CONN_FLAG_IS_CANCEL;
}
static int arm_gcp(struct gwp_wrk *w, struct gwp_conn_pair *gcp)
@@ -640,7 +640,7 @@ static int handle_event(struct gwp_wrk *w, struct io_uring_cqe *cqe)
break;
case EV_BIT_TARGET_CANCEL:
pr_dbg(&ctx->lh, "Handling target cancel event: %d", cqe->res);
- assert(gcp->flags & GWP_CONN_FLAG_IS_SHUTDOWN);
+ assert(gcp->flags & GWP_CONN_FLAG_IS_CANCEL);
r = 0;
break;
case EV_BIT_CLIENT_CANCEL:
@@ -661,7 +661,7 @@ static int handle_event(struct gwp_wrk *w, struct io_uring_cqe *cqe)
gcp = udata;
if ((gcp->flags & GWP_CONN_FLAG_IS_DYING) &&
- !(gcp->flags & GWP_CONN_FLAG_IS_SHUTDOWN))
+ !(gcp->flags & GWP_CONN_FLAG_IS_CANCEL))
shutdown_gcp(w, gcp);
put_gcp(w, gcp);
diff --git a/src/gwproxy/gwproxy.h b/src/gwproxy/gwproxy.h
index 86c1a05458ad..4b0fdfb37f73 100644
--- a/src/gwproxy/gwproxy.h
+++ b/src/gwproxy/gwproxy.h
@@ -99,7 +99,7 @@ enum {
*/
GWP_CONN_FLAG_NO_CLOSE_FD = (1ull << 0ull),
GWP_CONN_FLAG_IS_DYING = (1ull << 1ull),
- GWP_CONN_FLAG_IS_SHUTDOWN = (1ull << 2ull),
+ GWP_CONN_FLAG_IS_CANCEL = (1ull << 2ull),
};
struct gwp_conn_pair {
--
Ahmad Gani
^ permalink raw reply related [flat|nested] 11+ messages in thread
* Re: [PATCH gwproxy v1 0/3] Minor changes and fixes
2025-07-29 2:48 [PATCH gwproxy v1 0/3] Minor changes and fixes Ahmad Gani
2025-07-29 2:48 ` [PATCH gwproxy v1 2/3] io_uring: Add macro guard Ahmad Gani
2025-07-29 2:48 ` [PATCH gwproxy v1 3/3] io_uring: Rename GWP_CONN_FLAG_IS_SHUTDOWN to GWP_CONN_FLAG_IS_CANCEL Ahmad Gani
@ 2025-07-29 2:53 ` Ammar Faizi
2025-07-29 3:08 ` [PATCH gwproxy v2] io_uring: Reduce liburing code base Ahmad Gani
2025-07-29 3:47 ` [PATCH gwproxy v2 0/3] Minor changes and fixes Ahmad Gani
2 siblings, 2 replies; 11+ messages in thread
From: Ammar Faizi @ 2025-07-29 2:53 UTC (permalink / raw)
To: Ahmad Gani; +Cc: GNU/Weeb Mailing List
On Tue, Jul 29, 2025 at 09:48:25AM +0700, Ahmad Gani wrote:
> io_uring: Add liburing to the code base
This one feels too big. Let's not bring liburing tests and liburing
manpages.
--
Ammar Faizi
^ permalink raw reply [flat|nested] 11+ messages in thread
* [PATCH gwproxy v2] io_uring: Reduce liburing code base
2025-07-29 2:53 ` [PATCH gwproxy v1 0/3] Minor changes and fixes Ammar Faizi
@ 2025-07-29 3:08 ` Ahmad Gani
2025-07-29 3:47 ` [PATCH gwproxy v2 0/3] Minor changes and fixes Ahmad Gani
1 sibling, 0 replies; 11+ messages in thread
From: Ahmad Gani @ 2025-07-29 3:08 UTC (permalink / raw)
To: ammarfaizi2; +Cc: gwml, reyuki
Removing manual pages and tests directory.
Signed-off-by: Ahmad Gani <reyuki@gnuweeb.org>
---
src/liburing/man/IO_URING_CHECK_VERSION.3 | 1 -
src/liburing/man/IO_URING_VERSION_MAJOR.3 | 1 -
src/liburing/man/IO_URING_VERSION_MINOR.3 | 1 -
.../man/__io_uring_buf_ring_cq_advance.3 | 1 -
src/liburing/man/io_uring.7 | 864 -------
src/liburing/man/io_uring_buf_ring_add.3 | 61 -
src/liburing/man/io_uring_buf_ring_advance.3 | 31 -
.../man/io_uring_buf_ring_available.3 | 47 -
.../man/io_uring_buf_ring_cq_advance.3 | 55 -
src/liburing/man/io_uring_buf_ring_init.3 | 36 -
src/liburing/man/io_uring_buf_ring_mask.3 | 27 -
src/liburing/man/io_uring_check_version.3 | 72 -
src/liburing/man/io_uring_clone_buffers.3 | 168 --
.../man/io_uring_clone_buffers_offset.3 | 1 -
src/liburing/man/io_uring_close_ring_fd.3 | 43 -
src/liburing/man/io_uring_cq_advance.3 | 49 -
src/liburing/man/io_uring_cq_has_overflow.3 | 31 -
src/liburing/man/io_uring_cq_ready.3 | 26 -
src/liburing/man/io_uring_cqe_get_data.3 | 53 -
src/liburing/man/io_uring_cqe_get_data64.3 | 1 -
src/liburing/man/io_uring_cqe_seen.3 | 41 -
src/liburing/man/io_uring_enable_rings.3 | 40 -
src/liburing/man/io_uring_enter.2 | 2066 -----------------
src/liburing/man/io_uring_enter2.2 | 1 -
src/liburing/man/io_uring_for_each_cqe.3 | 63 -
src/liburing/man/io_uring_free_buf_ring.3 | 53 -
src/liburing/man/io_uring_free_probe.3 | 27 -
src/liburing/man/io_uring_free_reg_wait.3 | 35 -
src/liburing/man/io_uring_get_events.3 | 33 -
src/liburing/man/io_uring_get_probe.3 | 30 -
src/liburing/man/io_uring_get_sqe.3 | 57 -
src/liburing/man/io_uring_major_version.3 | 1 -
src/liburing/man/io_uring_minor_version.3 | 1 -
src/liburing/man/io_uring_opcode_supported.3 | 30 -
src/liburing/man/io_uring_peek_batch_cqe.3 | 1 -
src/liburing/man/io_uring_peek_cqe.3 | 59 -
src/liburing/man/io_uring_prep_accept.3 | 203 --
.../man/io_uring_prep_accept_direct.3 | 1 -
src/liburing/man/io_uring_prep_bind.3 | 54 -
src/liburing/man/io_uring_prep_cancel.3 | 136 --
src/liburing/man/io_uring_prep_cancel64.3 | 1 -
src/liburing/man/io_uring_prep_cancel_fd.3 | 1 -
src/liburing/man/io_uring_prep_close.3 | 67 -
src/liburing/man/io_uring_prep_close_direct.3 | 1 -
src/liburing/man/io_uring_prep_cmd.3 | 126 -
src/liburing/man/io_uring_prep_cmd_discard.3 | 64 -
src/liburing/man/io_uring_prep_connect.3 | 66 -
src/liburing/man/io_uring_prep_epoll_wait.3 | 64 -
src/liburing/man/io_uring_prep_fadvise.3 | 76 -
src/liburing/man/io_uring_prep_fadvise64.3 | 1 -
src/liburing/man/io_uring_prep_fallocate.3 | 59 -
src/liburing/man/io_uring_prep_fgetxattr.3 | 1 -
src/liburing/man/io_uring_prep_files_update.3 | 92 -
.../man/io_uring_prep_fixed_fd_install.3 | 70 -
src/liburing/man/io_uring_prep_fsetxattr.3 | 1 -
src/liburing/man/io_uring_prep_fsync.3 | 70 -
src/liburing/man/io_uring_prep_ftruncate.3 | 54 -
src/liburing/man/io_uring_prep_futex_wait.3 | 94 -
src/liburing/man/io_uring_prep_futex_waitv.3 | 78 -
src/liburing/man/io_uring_prep_futex_wake.3 | 86 -
src/liburing/man/io_uring_prep_getxattr.3 | 61 -
src/liburing/man/io_uring_prep_link.3 | 1 -
src/liburing/man/io_uring_prep_link_timeout.3 | 98 -
src/liburing/man/io_uring_prep_linkat.3 | 91 -
src/liburing/man/io_uring_prep_listen.3 | 52 -
src/liburing/man/io_uring_prep_madvise.3 | 72 -
src/liburing/man/io_uring_prep_madvise64.3 | 1 -
src/liburing/man/io_uring_prep_mkdir.3 | 1 -
src/liburing/man/io_uring_prep_mkdirat.3 | 83 -
src/liburing/man/io_uring_prep_msg_ring.3 | 92 -
.../man/io_uring_prep_msg_ring_cqe_flags.3 | 1 -
src/liburing/man/io_uring_prep_msg_ring_fd.3 | 83 -
.../man/io_uring_prep_msg_ring_fd_alloc.3 | 1 -
.../man/io_uring_prep_multishot_accept.3 | 1 -
.../io_uring_prep_multishot_accept_direct.3 | 1 -
src/liburing/man/io_uring_prep_nop.3 | 28 -
src/liburing/man/io_uring_prep_open.3 | 1 -
src/liburing/man/io_uring_prep_open_direct.3 | 1 -
src/liburing/man/io_uring_prep_openat.3 | 138 --
src/liburing/man/io_uring_prep_openat2.3 | 119 -
.../man/io_uring_prep_openat2_direct.3 | 1 -
.../man/io_uring_prep_openat_direct.3 | 1 -
src/liburing/man/io_uring_prep_poll_add.3 | 72 -
.../man/io_uring_prep_poll_multishot.3 | 1 -
src/liburing/man/io_uring_prep_poll_remove.3 | 55 -
src/liburing/man/io_uring_prep_poll_update.3 | 101 -
.../man/io_uring_prep_provide_buffers.3 | 140 --
src/liburing/man/io_uring_prep_read.3 | 69 -
src/liburing/man/io_uring_prep_read_fixed.3 | 72 -
.../man/io_uring_prep_read_multishot.3 | 100 -
src/liburing/man/io_uring_prep_readv.3 | 85 -
src/liburing/man/io_uring_prep_readv2.3 | 111 -
src/liburing/man/io_uring_prep_recv.3 | 139 --
.../man/io_uring_prep_recv_multishot.3 | 1 -
src/liburing/man/io_uring_prep_recvmsg.3 | 126 -
.../man/io_uring_prep_recvmsg_multishot.3 | 1 -
.../man/io_uring_prep_remove_buffers.3 | 52 -
src/liburing/man/io_uring_prep_rename.3 | 1 -
src/liburing/man/io_uring_prep_renameat.3 | 95 -
src/liburing/man/io_uring_prep_send.3 | 146 --
src/liburing/man/io_uring_prep_send_bundle.3 | 1 -
.../man/io_uring_prep_send_set_addr.3 | 38 -
src/liburing/man/io_uring_prep_send_zc.3 | 96 -
.../man/io_uring_prep_send_zc_fixed.3 | 1 -
src/liburing/man/io_uring_prep_sendmsg.3 | 91 -
src/liburing/man/io_uring_prep_sendmsg_zc.3 | 1 -
src/liburing/man/io_uring_prep_sendto.3 | 1 -
src/liburing/man/io_uring_prep_setxattr.3 | 64 -
src/liburing/man/io_uring_prep_shutdown.3 | 53 -
src/liburing/man/io_uring_prep_socket.3 | 118 -
.../man/io_uring_prep_socket_direct.3 | 1 -
.../man/io_uring_prep_socket_direct_alloc.3 | 1 -
src/liburing/man/io_uring_prep_splice.3 | 120 -
src/liburing/man/io_uring_prep_statx.3 | 74 -
src/liburing/man/io_uring_prep_symlink.3 | 1 -
src/liburing/man/io_uring_prep_symlinkat.3 | 85 -
.../man/io_uring_prep_sync_file_range.3 | 59 -
src/liburing/man/io_uring_prep_tee.3 | 74 -
src/liburing/man/io_uring_prep_timeout.3 | 107 -
.../man/io_uring_prep_timeout_remove.3 | 1 -
.../man/io_uring_prep_timeout_update.3 | 99 -
src/liburing/man/io_uring_prep_unlink.3 | 1 -
src/liburing/man/io_uring_prep_unlinkat.3 | 82 -
src/liburing/man/io_uring_prep_waitid.3 | 67 -
src/liburing/man/io_uring_prep_write.3 | 67 -
src/liburing/man/io_uring_prep_write_fixed.3 | 72 -
src/liburing/man/io_uring_prep_writev.3 | 85 -
src/liburing/man/io_uring_prep_writev2.3 | 111 -
src/liburing/man/io_uring_queue_exit.3 | 26 -
src/liburing/man/io_uring_queue_init.3 | 130 --
src/liburing/man/io_uring_queue_init_mem.3 | 1 -
src/liburing/man/io_uring_queue_init_params.3 | 1 -
.../man/io_uring_recvmsg_cmsg_firsthdr.3 | 1 -
.../man/io_uring_recvmsg_cmsg_nexthdr.3 | 1 -
src/liburing/man/io_uring_recvmsg_name.3 | 1 -
src/liburing/man/io_uring_recvmsg_out.3 | 82 -
src/liburing/man/io_uring_recvmsg_payload.3 | 1 -
.../man/io_uring_recvmsg_payload_length.3 | 1 -
src/liburing/man/io_uring_recvmsg_validate.3 | 1 -
src/liburing/man/io_uring_register.2 | 1199 ----------
src/liburing/man/io_uring_register_buf_ring.3 | 157 --
src/liburing/man/io_uring_register_buffers.3 | 105 -
.../man/io_uring_register_buffers_sparse.3 | 1 -
.../man/io_uring_register_buffers_tags.3 | 1 -
.../io_uring_register_buffers_update_tag.3 | 1 -
src/liburing/man/io_uring_register_clock.3 | 72 -
src/liburing/man/io_uring_register_eventfd.3 | 50 -
.../man/io_uring_register_eventfd_async.3 | 1 -
.../man/io_uring_register_file_alloc_range.3 | 52 -
src/liburing/man/io_uring_register_files.3 | 120 -
.../man/io_uring_register_files_sparse.3 | 1 -
.../man/io_uring_register_files_tags.3 | 1 -
.../man/io_uring_register_files_update.3 | 1 -
.../man/io_uring_register_files_update_tag.3 | 1 -
src/liburing/man/io_uring_register_iowq_aff.3 | 67 -
.../man/io_uring_register_iowq_max_workers.3 | 71 -
src/liburing/man/io_uring_register_napi.3 | 40 -
src/liburing/man/io_uring_register_reg_wait.3 | 62 -
src/liburing/man/io_uring_register_ring_fd.3 | 51 -
.../man/io_uring_register_sync_cancel.3 | 73 -
src/liburing/man/io_uring_register_sync_msg.3 | 74 -
src/liburing/man/io_uring_resize_rings.3 | 116 -
src/liburing/man/io_uring_setup.2 | 762 ------
src/liburing/man/io_uring_setup_buf_ring.3 | 94 -
src/liburing/man/io_uring_setup_reg_wait.3 | 121 -
src/liburing/man/io_uring_sq_ready.3 | 31 -
src/liburing/man/io_uring_sq_space_left.3 | 25 -
src/liburing/man/io_uring_sqe_set_buf_group.3 | 32 -
src/liburing/man/io_uring_sqe_set_data.3 | 57 -
src/liburing/man/io_uring_sqe_set_data64.3 | 1 -
src/liburing/man/io_uring_sqe_set_flags.3 | 87 -
src/liburing/man/io_uring_sqring_wait.3 | 34 -
src/liburing/man/io_uring_submit.3 | 51 -
.../man/io_uring_submit_and_get_events.3 | 31 -
src/liburing/man/io_uring_submit_and_wait.3 | 44 -
.../io_uring_submit_and_wait_min_timeout.3 | 119 -
.../man/io_uring_submit_and_wait_reg.3 | 63 -
.../man/io_uring_submit_and_wait_timeout.3 | 74 -
.../man/io_uring_unregister_buf_ring.3 | 30 -
.../man/io_uring_unregister_buffers.3 | 27 -
.../man/io_uring_unregister_eventfd.3 | 1 -
src/liburing/man/io_uring_unregister_files.3 | 27 -
.../man/io_uring_unregister_iowq_aff.3 | 1 -
src/liburing/man/io_uring_unregister_napi.3 | 27 -
.../man/io_uring_unregister_ring_fd.3 | 32 -
src/liburing/man/io_uring_wait_cqe.3 | 41 -
src/liburing/man/io_uring_wait_cqe_nr.3 | 49 -
src/liburing/man/io_uring_wait_cqe_timeout.3 | 61 -
src/liburing/man/io_uring_wait_cqes.3 | 80 -
.../man/io_uring_wait_cqes_min_timeout.3 | 76 -
190 files changed, 14080 deletions(-)
delete mode 120000 src/liburing/man/IO_URING_CHECK_VERSION.3
delete mode 120000 src/liburing/man/IO_URING_VERSION_MAJOR.3
delete mode 120000 src/liburing/man/IO_URING_VERSION_MINOR.3
delete mode 120000 src/liburing/man/__io_uring_buf_ring_cq_advance.3
delete mode 100644 src/liburing/man/io_uring.7
delete mode 100644 src/liburing/man/io_uring_buf_ring_add.3
delete mode 100644 src/liburing/man/io_uring_buf_ring_advance.3
delete mode 100644 src/liburing/man/io_uring_buf_ring_available.3
delete mode 100644 src/liburing/man/io_uring_buf_ring_cq_advance.3
delete mode 100644 src/liburing/man/io_uring_buf_ring_init.3
delete mode 100644 src/liburing/man/io_uring_buf_ring_mask.3
delete mode 100644 src/liburing/man/io_uring_check_version.3
delete mode 100644 src/liburing/man/io_uring_clone_buffers.3
delete mode 120000 src/liburing/man/io_uring_clone_buffers_offset.3
delete mode 100644 src/liburing/man/io_uring_close_ring_fd.3
delete mode 100644 src/liburing/man/io_uring_cq_advance.3
delete mode 100644 src/liburing/man/io_uring_cq_has_overflow.3
delete mode 100644 src/liburing/man/io_uring_cq_ready.3
delete mode 100644 src/liburing/man/io_uring_cqe_get_data.3
delete mode 120000 src/liburing/man/io_uring_cqe_get_data64.3
delete mode 100644 src/liburing/man/io_uring_cqe_seen.3
delete mode 100644 src/liburing/man/io_uring_enable_rings.3
delete mode 100644 src/liburing/man/io_uring_enter.2
delete mode 120000 src/liburing/man/io_uring_enter2.2
delete mode 100644 src/liburing/man/io_uring_for_each_cqe.3
delete mode 100644 src/liburing/man/io_uring_free_buf_ring.3
delete mode 100644 src/liburing/man/io_uring_free_probe.3
delete mode 100644 src/liburing/man/io_uring_free_reg_wait.3
delete mode 100644 src/liburing/man/io_uring_get_events.3
delete mode 100644 src/liburing/man/io_uring_get_probe.3
delete mode 100644 src/liburing/man/io_uring_get_sqe.3
delete mode 120000 src/liburing/man/io_uring_major_version.3
delete mode 120000 src/liburing/man/io_uring_minor_version.3
delete mode 100644 src/liburing/man/io_uring_opcode_supported.3
delete mode 120000 src/liburing/man/io_uring_peek_batch_cqe.3
delete mode 100644 src/liburing/man/io_uring_peek_cqe.3
delete mode 100644 src/liburing/man/io_uring_prep_accept.3
delete mode 120000 src/liburing/man/io_uring_prep_accept_direct.3
delete mode 100644 src/liburing/man/io_uring_prep_bind.3
delete mode 100644 src/liburing/man/io_uring_prep_cancel.3
delete mode 120000 src/liburing/man/io_uring_prep_cancel64.3
delete mode 120000 src/liburing/man/io_uring_prep_cancel_fd.3
delete mode 100644 src/liburing/man/io_uring_prep_close.3
delete mode 120000 src/liburing/man/io_uring_prep_close_direct.3
delete mode 100644 src/liburing/man/io_uring_prep_cmd.3
delete mode 100644 src/liburing/man/io_uring_prep_cmd_discard.3
delete mode 100644 src/liburing/man/io_uring_prep_connect.3
delete mode 100644 src/liburing/man/io_uring_prep_epoll_wait.3
delete mode 100644 src/liburing/man/io_uring_prep_fadvise.3
delete mode 120000 src/liburing/man/io_uring_prep_fadvise64.3
delete mode 100644 src/liburing/man/io_uring_prep_fallocate.3
delete mode 120000 src/liburing/man/io_uring_prep_fgetxattr.3
delete mode 100644 src/liburing/man/io_uring_prep_files_update.3
delete mode 100644 src/liburing/man/io_uring_prep_fixed_fd_install.3
delete mode 120000 src/liburing/man/io_uring_prep_fsetxattr.3
delete mode 100644 src/liburing/man/io_uring_prep_fsync.3
delete mode 100644 src/liburing/man/io_uring_prep_ftruncate.3
delete mode 100644 src/liburing/man/io_uring_prep_futex_wait.3
delete mode 100644 src/liburing/man/io_uring_prep_futex_waitv.3
delete mode 100644 src/liburing/man/io_uring_prep_futex_wake.3
delete mode 100644 src/liburing/man/io_uring_prep_getxattr.3
delete mode 120000 src/liburing/man/io_uring_prep_link.3
delete mode 100644 src/liburing/man/io_uring_prep_link_timeout.3
delete mode 100644 src/liburing/man/io_uring_prep_linkat.3
delete mode 100644 src/liburing/man/io_uring_prep_listen.3
delete mode 100644 src/liburing/man/io_uring_prep_madvise.3
delete mode 120000 src/liburing/man/io_uring_prep_madvise64.3
delete mode 120000 src/liburing/man/io_uring_prep_mkdir.3
delete mode 100644 src/liburing/man/io_uring_prep_mkdirat.3
delete mode 100644 src/liburing/man/io_uring_prep_msg_ring.3
delete mode 120000 src/liburing/man/io_uring_prep_msg_ring_cqe_flags.3
delete mode 100644 src/liburing/man/io_uring_prep_msg_ring_fd.3
delete mode 120000 src/liburing/man/io_uring_prep_msg_ring_fd_alloc.3
delete mode 120000 src/liburing/man/io_uring_prep_multishot_accept.3
delete mode 120000 src/liburing/man/io_uring_prep_multishot_accept_direct.3
delete mode 100644 src/liburing/man/io_uring_prep_nop.3
delete mode 120000 src/liburing/man/io_uring_prep_open.3
delete mode 120000 src/liburing/man/io_uring_prep_open_direct.3
delete mode 100644 src/liburing/man/io_uring_prep_openat.3
delete mode 100644 src/liburing/man/io_uring_prep_openat2.3
delete mode 120000 src/liburing/man/io_uring_prep_openat2_direct.3
delete mode 120000 src/liburing/man/io_uring_prep_openat_direct.3
delete mode 100644 src/liburing/man/io_uring_prep_poll_add.3
delete mode 120000 src/liburing/man/io_uring_prep_poll_multishot.3
delete mode 100644 src/liburing/man/io_uring_prep_poll_remove.3
delete mode 100644 src/liburing/man/io_uring_prep_poll_update.3
delete mode 100644 src/liburing/man/io_uring_prep_provide_buffers.3
delete mode 100644 src/liburing/man/io_uring_prep_read.3
delete mode 100644 src/liburing/man/io_uring_prep_read_fixed.3
delete mode 100644 src/liburing/man/io_uring_prep_read_multishot.3
delete mode 100644 src/liburing/man/io_uring_prep_readv.3
delete mode 100644 src/liburing/man/io_uring_prep_readv2.3
delete mode 100644 src/liburing/man/io_uring_prep_recv.3
delete mode 120000 src/liburing/man/io_uring_prep_recv_multishot.3
delete mode 100644 src/liburing/man/io_uring_prep_recvmsg.3
delete mode 120000 src/liburing/man/io_uring_prep_recvmsg_multishot.3
delete mode 100644 src/liburing/man/io_uring_prep_remove_buffers.3
delete mode 120000 src/liburing/man/io_uring_prep_rename.3
delete mode 100644 src/liburing/man/io_uring_prep_renameat.3
delete mode 100644 src/liburing/man/io_uring_prep_send.3
delete mode 120000 src/liburing/man/io_uring_prep_send_bundle.3
delete mode 100644 src/liburing/man/io_uring_prep_send_set_addr.3
delete mode 100644 src/liburing/man/io_uring_prep_send_zc.3
delete mode 120000 src/liburing/man/io_uring_prep_send_zc_fixed.3
delete mode 100644 src/liburing/man/io_uring_prep_sendmsg.3
delete mode 120000 src/liburing/man/io_uring_prep_sendmsg_zc.3
delete mode 120000 src/liburing/man/io_uring_prep_sendto.3
delete mode 100644 src/liburing/man/io_uring_prep_setxattr.3
delete mode 100644 src/liburing/man/io_uring_prep_shutdown.3
delete mode 100644 src/liburing/man/io_uring_prep_socket.3
delete mode 120000 src/liburing/man/io_uring_prep_socket_direct.3
delete mode 120000 src/liburing/man/io_uring_prep_socket_direct_alloc.3
delete mode 100644 src/liburing/man/io_uring_prep_splice.3
delete mode 100644 src/liburing/man/io_uring_prep_statx.3
delete mode 120000 src/liburing/man/io_uring_prep_symlink.3
delete mode 100644 src/liburing/man/io_uring_prep_symlinkat.3
delete mode 100644 src/liburing/man/io_uring_prep_sync_file_range.3
delete mode 100644 src/liburing/man/io_uring_prep_tee.3
delete mode 100644 src/liburing/man/io_uring_prep_timeout.3
delete mode 120000 src/liburing/man/io_uring_prep_timeout_remove.3
delete mode 100644 src/liburing/man/io_uring_prep_timeout_update.3
delete mode 120000 src/liburing/man/io_uring_prep_unlink.3
delete mode 100644 src/liburing/man/io_uring_prep_unlinkat.3
delete mode 100644 src/liburing/man/io_uring_prep_waitid.3
delete mode 100644 src/liburing/man/io_uring_prep_write.3
delete mode 100644 src/liburing/man/io_uring_prep_write_fixed.3
delete mode 100644 src/liburing/man/io_uring_prep_writev.3
delete mode 100644 src/liburing/man/io_uring_prep_writev2.3
delete mode 100644 src/liburing/man/io_uring_queue_exit.3
delete mode 100644 src/liburing/man/io_uring_queue_init.3
delete mode 120000 src/liburing/man/io_uring_queue_init_mem.3
delete mode 120000 src/liburing/man/io_uring_queue_init_params.3
delete mode 120000 src/liburing/man/io_uring_recvmsg_cmsg_firsthdr.3
delete mode 120000 src/liburing/man/io_uring_recvmsg_cmsg_nexthdr.3
delete mode 120000 src/liburing/man/io_uring_recvmsg_name.3
delete mode 100644 src/liburing/man/io_uring_recvmsg_out.3
delete mode 120000 src/liburing/man/io_uring_recvmsg_payload.3
delete mode 120000 src/liburing/man/io_uring_recvmsg_payload_length.3
delete mode 120000 src/liburing/man/io_uring_recvmsg_validate.3
delete mode 100644 src/liburing/man/io_uring_register.2
delete mode 100644 src/liburing/man/io_uring_register_buf_ring.3
delete mode 100644 src/liburing/man/io_uring_register_buffers.3
delete mode 120000 src/liburing/man/io_uring_register_buffers_sparse.3
delete mode 120000 src/liburing/man/io_uring_register_buffers_tags.3
delete mode 120000 src/liburing/man/io_uring_register_buffers_update_tag.3
delete mode 100644 src/liburing/man/io_uring_register_clock.3
delete mode 100644 src/liburing/man/io_uring_register_eventfd.3
delete mode 120000 src/liburing/man/io_uring_register_eventfd_async.3
delete mode 100644 src/liburing/man/io_uring_register_file_alloc_range.3
delete mode 100644 src/liburing/man/io_uring_register_files.3
delete mode 120000 src/liburing/man/io_uring_register_files_sparse.3
delete mode 120000 src/liburing/man/io_uring_register_files_tags.3
delete mode 120000 src/liburing/man/io_uring_register_files_update.3
delete mode 120000 src/liburing/man/io_uring_register_files_update_tag.3
delete mode 100644 src/liburing/man/io_uring_register_iowq_aff.3
delete mode 100644 src/liburing/man/io_uring_register_iowq_max_workers.3
delete mode 100644 src/liburing/man/io_uring_register_napi.3
delete mode 100644 src/liburing/man/io_uring_register_reg_wait.3
delete mode 100644 src/liburing/man/io_uring_register_ring_fd.3
delete mode 100644 src/liburing/man/io_uring_register_sync_cancel.3
delete mode 100644 src/liburing/man/io_uring_register_sync_msg.3
delete mode 100644 src/liburing/man/io_uring_resize_rings.3
delete mode 100644 src/liburing/man/io_uring_setup.2
delete mode 100644 src/liburing/man/io_uring_setup_buf_ring.3
delete mode 100644 src/liburing/man/io_uring_setup_reg_wait.3
delete mode 100644 src/liburing/man/io_uring_sq_ready.3
delete mode 100644 src/liburing/man/io_uring_sq_space_left.3
delete mode 100644 src/liburing/man/io_uring_sqe_set_buf_group.3
delete mode 100644 src/liburing/man/io_uring_sqe_set_data.3
delete mode 120000 src/liburing/man/io_uring_sqe_set_data64.3
delete mode 100644 src/liburing/man/io_uring_sqe_set_flags.3
delete mode 100644 src/liburing/man/io_uring_sqring_wait.3
delete mode 100644 src/liburing/man/io_uring_submit.3
delete mode 100644 src/liburing/man/io_uring_submit_and_get_events.3
delete mode 100644 src/liburing/man/io_uring_submit_and_wait.3
delete mode 100644 src/liburing/man/io_uring_submit_and_wait_min_timeout.3
delete mode 100644 src/liburing/man/io_uring_submit_and_wait_reg.3
delete mode 100644 src/liburing/man/io_uring_submit_and_wait_timeout.3
delete mode 100644 src/liburing/man/io_uring_unregister_buf_ring.3
delete mode 100644 src/liburing/man/io_uring_unregister_buffers.3
delete mode 120000 src/liburing/man/io_uring_unregister_eventfd.3
delete mode 100644 src/liburing/man/io_uring_unregister_files.3
delete mode 120000 src/liburing/man/io_uring_unregister_iowq_aff.3
delete mode 100644 src/liburing/man/io_uring_unregister_napi.3
delete mode 100644 src/liburing/man/io_uring_unregister_ring_fd.3
delete mode 100644 src/liburing/man/io_uring_wait_cqe.3
delete mode 100644 src/liburing/man/io_uring_wait_cqe_nr.3
delete mode 100644 src/liburing/man/io_uring_wait_cqe_timeout.3
delete mode 100644 src/liburing/man/io_uring_wait_cqes.3
delete mode 100644 src/liburing/man/io_uring_wait_cqes_min_timeout.3
diff --git a/src/liburing/man/IO_URING_CHECK_VERSION.3 b/src/liburing/man/IO_URING_CHECK_VERSION.3
deleted file mode 120000
index 21bbf456e240..000000000000
--- a/src/liburing/man/IO_URING_CHECK_VERSION.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_check_version.3
\ No newline at end of file
diff --git a/src/liburing/man/IO_URING_VERSION_MAJOR.3 b/src/liburing/man/IO_URING_VERSION_MAJOR.3
deleted file mode 120000
index 21bbf456e240..000000000000
--- a/src/liburing/man/IO_URING_VERSION_MAJOR.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_check_version.3
\ No newline at end of file
diff --git a/src/liburing/man/IO_URING_VERSION_MINOR.3 b/src/liburing/man/IO_URING_VERSION_MINOR.3
deleted file mode 120000
index 21bbf456e240..000000000000
--- a/src/liburing/man/IO_URING_VERSION_MINOR.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_check_version.3
\ No newline at end of file
diff --git a/src/liburing/man/__io_uring_buf_ring_cq_advance.3 b/src/liburing/man/__io_uring_buf_ring_cq_advance.3
deleted file mode 120000
index 4b3a1e5fa112..000000000000
--- a/src/liburing/man/__io_uring_buf_ring_cq_advance.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_buf_ring_cq_advance.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring.7 b/src/liburing/man/io_uring.7
deleted file mode 100644
index 19714db566c3..000000000000
--- a/src/liburing/man/io_uring.7
+++ /dev/null
@@ -1,864 +0,0 @@
-.\" Copyright (C) 2020 Shuveb Hussain <shuveb@gmail.com>
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-
-.TH io_uring 7 2020-07-26 "Linux" "Linux Programmer's Manual"
-.SH NAME
-io_uring \- Asynchronous I/O facility
-.SH SYNOPSIS
-.nf
-.B "#include <linux/io_uring.h>"
-.fi
-.PP
-.SH DESCRIPTION
-.PP
-.B io_uring
-is a Linux-specific API for asynchronous I/O.
-It allows the user to submit one or more I/O requests,
-which are processed asynchronously without blocking the calling process.
-.B io_uring
-gets its name from ring buffers which are shared between user space and
-kernel space. This arrangement allows for efficient I/O,
-while avoiding the overhead of copying buffers between them,
-where possible.
-This interface makes
-.B io_uring
-different from other UNIX I/O APIs,
-wherein,
-rather than just communicate between kernel and user space with system calls,
-ring buffers are used as the main mode of communication.
-This arrangement has various performance benefits which are discussed in a
-separate section below.
-This man page uses the terms shared buffers, shared ring buffers and
-queues interchangeably.
-.PP
-The general programming model you need to follow for
-.B io_uring
-is outlined below
-.IP \(bu
-Set up shared buffers with
-.BR io_uring_setup (2)
-and
-.BR mmap (2),
-mapping into user space shared buffers for the submission queue (SQ) and the
-completion queue (CQ).
-You place I/O requests you want to make on the SQ,
-while the kernel places the results of those operations on the CQ.
-.IP \(bu
-For every I/O request you need to make (like to read a file, write a file,
-accept a socket connection, etc), you create a submission queue entry,
-or SQE,
-describe the I/O operation you need to get done and add it to the tail of
-the submission queue (SQ).
-Each I/O operation is,
-in essence,
-the equivalent of a system call you would have made otherwise,
-if you were not using
-.BR io_uring .
-For instance,
-a SQE with the
-.I opcode
-set to
-.B IORING_OP_READ
-will request a read operation to be issued that is similar to the
-.BR read (2)
-system call. Refer to the opcode documentation in
-.BR io_uring_enter (2)
-for all supported opcodes and their properties.
-You can add more than one SQE to the queue depending on the number of
-operations you want to request.
-.IP \(bu
-After you add one or more SQEs,
-you need to call
-.BR io_uring_enter (2)
-to tell the kernel to dequeue your I/O requests off the SQ and begin
-processing them.
-.IP \(bu
-For each SQE you submit,
-once it is done processing the request,
-the kernel places a completion queue event or CQE at the tail of the
-completion queue or CQ.
-The kernel places exactly one matching CQE in the CQ for every SQE you
-submit on the SQ.
-After you retrieve a CQE,
-minimally,
-you might be interested in checking the
-.I res
-field of the CQE structure,
-which corresponds to the return value of the system
-call's equivalent,
-had you used it directly without using
-.BR io_uring .
-Given that
-.B io_uring
-is an async interface,
-.I errno
-is never used for passing back error information. Instead,
-.I res
-will contain what the equivalent system call would have returned in case
-of success, and in case of error
-.I res
-will contain
-.IR -errno .
-For example, if the normal read system call would have returned -1 and set
-.I errno
-to
-.BR EINVAL ,
-then
-.I res
-would contain
-.BR -EINVAL .
-If the normal system call would have returned a read size of 1024, then
-.I res
-would contain 1024.
-.IP \(bu
-Optionally,
-.BR io_uring_enter (2)
-can also wait for a specified number of requests to be processed by the kernel
-before it returns.
-If you specified a certain number of completions to wait for,
-the kernel would have placed at least those many number of CQEs on the CQ,
-which you can then readily read,
-right after the return from
-.BR io_uring_enter (2).
-.IP \(bu
-It is important to remember that I/O requests submitted to the kernel can
-complete in any order.
-It is not necessary for the kernel to process one request after another,
-in the order you placed them.
-Given that the interface is a ring,
-the requests are attempted in order,
-however that doesn't imply any sort of ordering on their execution or
-completion.
-When more than one request is in flight,
-it is not possible to determine which one will execute or complete first.
-When you dequeue CQEs off the CQ,
-you should always check which submitted request it corresponds to.
-The most common method for doing so is utilizing the
-.I user_data
-field in the request, which is passed back on the completion side.
-.IP \(bu
-Concretely, for operations where strict ordering is required,
-such as for sends and receives on a stream-oriented TCP socket,
-it is generally unsafe to have more than one outstanding send,
-or more than one outstanding receive (the two directions are independent)
-on a given socket at a time, as the kernel may reorder their execution
-if poll arming or other background kernel activities are involved.
-However,
-.B io_uring
-provides various facilities to enable applications to efficiently
-pipeline their operations safely. If the requests are submitted in a
-single batch, the application may use
-.B IOSQE_IO_LINK
-to enforce an execution order in the kernel. Otherwise,
-.B io_uring
-provides advanced features like
-.I multi shot
-and send/receive
-.I bundles
-to allow applications to provide more data in fewer, more efficient trips
-to the kernel. Even if these features are used, applications must still
-ensure they do not overlap different sends or different receives on a
-given file.
-.PP
-Adding to and reading from the queues:
-.IP \(bu
-You add SQEs to the tail of the SQ.
-The kernel reads SQEs off the head of the queue.
-.IP \(bu
-The kernel adds CQEs to the tail of the CQ.
-You read CQEs off the head of the queue.
-.PP
-It should be noted that depending on the configuration io_uring's behavior
-can deviate from the behavior outlined above, like not posting a CQE for
-every SQE when setting
-.B IOSQE_CQE_SKIP_SUCCESS
-in the SQE or posting multiple CQEs for a single SQE for multi shot operations
-or requiring an
-.BR io_uring_enter (2)
-syscall to make the kernel begin processing newly added SQEs when using
-submission queue polling.
-
-.SS Submission queue polling
-One of the goals of
-.B io_uring
-is to provide a means for efficient I/O.
-To this end,
-.B io_uring
-supports a polling mode that lets you avoid the call to
-.BR io_uring_enter (2),
-which you use to inform the kernel that you have queued SQEs on to the SQ.
-With SQ Polling,
-.B io_uring
-starts a kernel thread that polls the submission queue for any I/O
-requests you submit by adding SQEs.
-With SQ Polling enabled,
-there is no need for you to call
-.BR io_uring_enter (2),
-letting you avoid the overhead of system calls.
-A designated kernel thread dequeues SQEs off the SQ as you add them and
-dispatches them for asynchronous processing.
-.SS Setting up io_uring
-.PP
-The main steps in setting up
-.B io_uring
-consist of mapping in the shared buffers with
-.BR mmap (2)
-calls.
-In the example program included in this man page,
-the function
-.BR app_setup_uring ()
-sets up
-.B io_uring
-with a QUEUE_DEPTH deep submission queue.
-Pay attention to the 2
-.BR mmap (2)
-calls that set up the shared submission and completion queues.
-If your kernel is older than version 5.4,
-three
-.BR mmap(2)
-calls are required.
-.PP
-.SS Submitting I/O requests
-The process of submitting a request consists of describing the I/O
-operation you need to get done using an
-.B io_uring_sqe
-structure instance.
-These details describe the equivalent system call and its parameters.
-Because the range of I/O operations Linux supports are very varied and the
-.B io_uring_sqe
-structure needs to be able to describe them,
-it has several fields,
-some packed into unions for space efficiency.
-Here is a simplified version of struct
-.B io_uring_sqe
-with some of the most often used fields:
-.PP
-.in +4n
-.EX
-struct io_uring_sqe {
- __u8 opcode; /* type of operation for this sqe */
- __s32 fd; /* file descriptor to do IO on */
- __u64 off; /* offset into file */
- __u64 addr; /* pointer to buffer or iovecs */
- __u32 len; /* buffer size or number of iovecs */
- __u64 user_data; /* data to be passed back at completion time */
- __u8 flags; /* IOSQE_ flags */
- ...
-};
-.EE
-.in
-
-Here is struct
-.B io_uring_sqe
-in full:
-
-.in +4n
-.EX
-struct io_uring_sqe {
- __u8 opcode; /* type of operation for this sqe */
- __u8 flags; /* IOSQE_ flags */
- __u16 ioprio; /* ioprio for the request */
- __s32 fd; /* file descriptor to do IO on */
- union {
- __u64 off; /* offset into file */
- __u64 addr2;
- struct {
- __u32 cmd_op;
- __u32 __pad1;
- };
- };
- union {
- __u64 addr; /* pointer to buffer or iovecs */
- __u64 splice_off_in;
- struct {
- __u32 level;
- __u32 optname;
- };
- };
- __u32 len; /* buffer size or number of iovecs */
- union {
- __kernel_rwf_t rw_flags;
- __u32 fsync_flags;
- __u16 poll_events; /* compatibility */
- __u32 poll32_events; /* word-reversed for BE */
- __u32 sync_range_flags;
- __u32 msg_flags;
- __u32 timeout_flags;
- __u32 accept_flags;
- __u32 cancel_flags;
- __u32 open_flags;
- __u32 statx_flags;
- __u32 fadvise_advice;
- __u32 splice_flags;
- __u32 rename_flags;
- __u32 unlink_flags;
- __u32 hardlink_flags;
- __u32 xattr_flags;
- __u32 msg_ring_flags;
- __u32 uring_cmd_flags;
- __u32 waitid_flags;
- __u32 futex_flags;
- __u32 install_fd_flags;
- __u32 nop_flags;
- };
- __u64 user_data; /* data to be passed back at completion time */
- /* pack this to avoid bogus arm OABI complaints */
- union {
- /* index into fixed buffers, if used */
- __u16 buf_index;
- /* for grouped buffer selection */
- __u16 buf_group;
- } __attribute__((packed));
- /* personality to use, if used */
- __u16 personality;
- union {
- __s32 splice_fd_in;
- __u32 file_index;
- __u32 optlen;
- struct {
- __u16 addr_len;
- __u16 __pad3[1];
- };
- };
- union {
- struct {
- __u64 addr3;
- __u64 __pad2[1];
- };
- __u64 optval;
- /*
- * If the ring is initialized with IORING_SETUP_SQE128, then
- * this field is used for 80 bytes of arbitrary command data
- */
- __u8 cmd[0];
- };
-};
-.EE
-.in
-.PP
-To submit an I/O request to
-.BR io_uring ,
-you need to acquire a submission queue entry (SQE) from the submission
-queue (SQ),
-fill it up with details of the operation you want to submit and call
-.BR io_uring_enter (2).
-There are helper functions of the form io_uring_prep_X to enable proper
-setup of the SQE. If you want to avoid calling
-.BR io_uring_enter (2),
-you have the option of setting up Submission Queue Polling.
-.PP
-SQEs are added to the tail of the submission queue.
-The kernel picks up SQEs off the head of the SQ.
-The general algorithm to get the next available SQE and update the tail is
-as follows.
-.PP
-.in +4n
-.EX
-struct io_uring_sqe *sqe;
-unsigned tail, index;
-tail = *sqring->tail;
-index = tail & (*sqring->ring_mask);
-sqe = &sqring->sqes[index];
-/* fill up details about this I/O request */
-describe_io(sqe);
-/* fill the sqe index into the SQ ring array */
-sqring->array[index] = index;
-tail++;
-atomic_store_explicit(sqring->tail, tail, memory_order_release);
-.EE
-.in
-.PP
-To get the index of an entry,
-the application must mask the current tail index with the size mask of the
-ring.
-This holds true for both SQs and CQs.
-Once the SQE is acquired,
-the necessary fields are filled in,
-describing the request.
-While the CQ ring directly indexes the shared array of CQEs,
-the submission side has an indirection array between them.
-The submission side ring buffer is an index into this array,
-which in turn contains the index into the SQEs.
-.PP
-The following code snippet demonstrates how a read operation,
-an equivalent of a
-.BR preadv2 (2)
-system call is described by filling up an SQE with the necessary
-parameters.
-.PP
-.in +4n
-.EX
-struct iovec iovecs[16];
- ...
-sqe->opcode = IORING_OP_READV;
-sqe->fd = fd;
-sqe->addr = (unsigned long) iovecs;
-sqe->len = 16;
-sqe->off = offset;
-sqe->flags = 0;
-.EE
-.in
-.TP
-.B Memory ordering
-Modern compilers and CPUs freely reorder reads and writes without
-affecting the program's outcome to optimize performance.
-Some aspects of this need to be kept in mind on SMP systems since
-.B io_uring
-involves buffers shared between kernel and user space.
-These buffers are both visible and modifiable from kernel and user space.
-As heads and tails belonging to these shared buffers are updated by kernel
-and user space,
-changes need to be coherently visible on either side,
-irrespective of whether a CPU switch took place after the kernel-user mode
-switch happened.
-We use memory barriers to enforce this coherency.
-Being significantly large subjects on their own,
-memory barriers are out of scope for further discussion on this man page.
-For more information on modern memory models the reader may refer to the
-Documentation/memory-barriers.txt in the kernel tree or to the documentation
-of the formal C11 or kernel memory model.
-.TP
-.B Letting the kernel know about I/O submissions
-Once you place one or more SQEs on to the SQ,
-you need to let the kernel know that you've done so.
-You can do this by calling the
-.BR io_uring_enter (2)
-system call.
-This system call is also capable of waiting for a specified count of
-events to complete.
-This way,
-you can be sure to find completion events in the completion queue without
-having to poll it for events later.
-.SS Reading completion events
-Similar to the submission queue (SQ),
-the completion queue (CQ) is a shared buffer between the kernel and user
-space.
-Whereas you placed submission queue entries on the tail of the SQ and the
-kernel read off the head,
-when it comes to the CQ,
-the kernel places completion queue events or CQEs on the tail of the CQ and
-you read off its head.
-.PP
-Submission is flexible (and thus a bit more complicated) since it needs to
-be able to encode different types of system calls that take various
-parameters.
-Completion,
-on the other hand is simpler since we're looking only for a return value
-back from the kernel.
-This is easily understood by looking at the completion queue event
-structure,
-struct
-.BR io_uring_cqe :
-.PP
-.in +4n
-.EX
-struct io_uring_cqe {
- __u64 user_data; /* sqe->data submission passed back */
- __s32 res; /* result code for this event */
- __u32 flags;
-};
-.EE
-.in
-.PP
-Here,
-.I user_data
-is custom data that is passed unchanged from submission to completion.
-That is,
-from SQEs to CQEs.
-This field can be used to set context,
-uniquely identifying submissions that got completed.
-Given that I/O requests can complete in any order,
-this field can be used to correlate a submission with a completion.
-.I res
-is the result from the system call that was performed as part of the
-submission;
-its return value.
-
-The
-.I flags
-field carries request-specific information. As of the 6.12 kernel,
-the following flags are defined:
-
-.TP
-.B IORING_CQE_F_BUFFER
-If set, the upper 16 bits of the flags field carries the buffer ID that was
-chosen for this request. The request must have been issued with
-.B IOSQE_BUFFER_SELECT
-set, and used with a request type that supports buffer selection. Additionally,
-buffers must have been provided upfront either via the
-.B IORING_OP_PROVIDE_BUFFERS
-or the
-.B IORING_REGISTER_PBUF_RING
-methods.
-.TP
-.B IORING_CQE_F_MORE
-If set, the application should expect more completions from the request. This
-is used for requests that can generate multiple completions, such as multi-shot
-requests, receive, or accept.
-.TP
-.B IORING_CQE_F_SOCK_NONEMPTY
-If set, upon receiving the data from the socket in the current request, the
-socket still had data left on completion of this request.
-.TP
-.B IORING_CQE_F_NOTIF
-Set for notification CQEs, as seen with the zero-copy networking send and
-receive support.
-.TP
-.B IORING_CQE_F_BUF_MORE
-If set, the buffer ID set in the completion will get more completions. This
-means that the provided buffer has been partially consumed and there's more
-buffer space left, and hence the application should expect more completions
-with this buffer ID. Each completion will continue where the previous one
-left off. This can only happen if the provided buffer ring has been setup
-with
-.B IOU_PBUF_RING_INC
-to allow for incremental / partial consumption of buffers.
-.PP
-The general sequence to read completion events off the completion queue is
-as follows:
-.PP
-.in +4n
-.EX
-unsigned head;
-head = *cqring->head;
-if (head != atomic_load_acquire(cqring->tail)) {
- struct io_uring_cqe *cqe;
- unsigned index;
- index = head & (cqring->mask);
- cqe = &cqring->cqes[index];
- /* process completed CQE */
- process_cqe(cqe);
- /* CQE consumption complete */
- head++;
-}
-atomic_store_explicit(cqring->head, head, memory_order_release);
-.EE
-.in
-.PP
-It helps to be reminded that the kernel adds CQEs to the tail of the CQ,
-while you need to dequeue them off the head.
-To get the index of an entry at the head,
-the application must mask the current head index with the size mask of the
-ring.
-Once the CQE has been consumed or processed,
-the head needs to be updated to reflect the consumption of the CQE.
-Attention should be paid to the read and write barriers to ensure
-successful read and update of the head.
-.SS io_uring performance
-Because of the shared ring buffers between kernel and user space,
-.B io_uring
-can be a zero-copy system.
-Copying buffers to and from becomes necessary when system calls that
-transfer data between kernel and user space are involved.
-But since the bulk of the communication in
-.B io_uring
-is via buffers shared between the kernel and user space,
-this huge performance overhead is completely avoided.
-.PP
-While system calls may not seem like a significant overhead,
-in high performance applications,
-making a lot of them will begin to matter.
-While workarounds the operating system has in place to deal with Spectre
-and Meltdown are ideally best done away with,
-unfortunately,
-some of these workarounds are around the system call interface,
-making system calls not as cheap as before on affected hardware.
-While newer hardware should not need these workarounds,
-hardware with these vulnerabilities can be expected to be in the wild for a
-long time.
-While using synchronous programming interfaces or even when using
-asynchronous programming interfaces under Linux,
-there is at least one system call involved in the submission of each
-request.
-In
-.BR io_uring ,
-on the other hand,
-you can batch several requests in one go,
-simply by queueing up multiple SQEs,
-each describing an I/O operation you want and make a single call to
-.BR io_uring_enter (2).
-This is possible due to
-.BR io_uring 's
-shared buffers based design.
-.PP
-While this batching in itself can avoid the overhead associated with
-potentially multiple and frequent system calls,
-you can reduce even this overhead further with Submission Queue Polling,
-by having the kernel poll and pick up your SQEs for processing as you add
-them to the submission queue. This avoids the
-.BR io_uring_enter (2)
-call you need to make to tell the kernel to pick SQEs up.
-For high-performance applications,
-this means even fewer system call overheads.
-.SH CONFORMING TO
-.B io_uring
-is Linux-specific.
-.SH EXAMPLES
-The following example uses
-.B io_uring
-to copy stdin to stdout.
-Using shell redirection,
-you should be able to copy files with this example.
-Because it uses a queue depth of only one,
-this example processes I/O requests one after the other.
-It is purposefully kept this way to aid understanding.
-In real-world scenarios however,
-you'll want to have a larger queue depth to parallelize I/O request
-processing so as to gain the kind of performance benefits
-.B io_uring
-provides with its asynchronous processing of requests.
-.PP
-.EX
-#include <stdio.h>
-#include <stdlib.h>
-#include <sys/stat.h>
-#include <sys/ioctl.h>
-#include <sys/syscall.h>
-#include <sys/mman.h>
-#include <sys/uio.h>
-#include <linux/fs.h>
-#include <fcntl.h>
-#include <unistd.h>
-#include <string.h>
-#include <stdatomic.h>
-
-#include <linux/io_uring.h>
-
-#define QUEUE_DEPTH 1
-#define BLOCK_SZ 1024
-
-/* Macros for barriers needed by io_uring */
-#define io_uring_smp_store_release(p, v) \\
- atomic_store_explicit((_Atomic typeof(*(p)) *)(p), (v), \\
- memory_order_release)
-#define io_uring_smp_load_acquire(p) \\
- atomic_load_explicit((_Atomic typeof(*(p)) *)(p), \\
- memory_order_acquire)
-
-int ring_fd;
-unsigned *sring_tail, *sring_mask, *sring_array,
- *cring_head, *cring_tail, *cring_mask;
-struct io_uring_sqe *sqes;
-struct io_uring_cqe *cqes;
-char buff[BLOCK_SZ];
-off_t offset;
-
-/*
- * System call wrappers provided since glibc does not yet
- * provide wrappers for io_uring system calls.
-* */
-
-int io_uring_setup(unsigned entries, struct io_uring_params *p)
-{
- int ret;
- ret = syscall(__NR_io_uring_setup, entries, p);
- return (ret < 0) ? -errno : ret;
-}
-
-int io_uring_enter(int ring_fd, unsigned int to_submit,
- unsigned int min_complete, unsigned int flags)
-{
- int ret;
- ret = syscall(__NR_io_uring_enter, ring_fd, to_submit,
- min_complete, flags, NULL, 0);
- return (ret < 0) ? -errno : ret;
-}
-
-int app_setup_uring(void) {
- struct io_uring_params p;
- void *sq_ptr, *cq_ptr;
-
- /* See io_uring_setup(2) for io_uring_params.flags you can set */
- memset(&p, 0, sizeof(p));
- ring_fd = io_uring_setup(QUEUE_DEPTH, &p);
- if (ring_fd < 0) {
- perror("io_uring_setup");
- return 1;
- }
-
- /*
- * io_uring communication happens via 2 shared kernel-user space ring
- * buffers, which can be jointly mapped with a single mmap() call in
- * kernels >= 5.4.
- */
-
- int sring_sz = p.sq_off.array + p.sq_entries * sizeof(unsigned);
- int cring_sz = p.cq_off.cqes + p.cq_entries * sizeof(struct io_uring_cqe);
-
- /* Rather than check for kernel version, the recommended way is to
- * check the features field of the io_uring_params structure, which is a
- * bitmask. If IORING_FEAT_SINGLE_MMAP is set, we can do away with the
- * second mmap() call to map in the completion ring separately.
- */
- if (p.features & IORING_FEAT_SINGLE_MMAP) {
- if (cring_sz > sring_sz)
- sring_sz = cring_sz;
- cring_sz = sring_sz;
- }
-
- /* Map in the submission and completion queue ring buffers.
- * Kernels < 5.4 only map in the submission queue, though.
- */
- sq_ptr = mmap(0, sring_sz, PROT_READ | PROT_WRITE,
- MAP_SHARED | MAP_POPULATE,
- ring_fd, IORING_OFF_SQ_RING);
- if (sq_ptr == MAP_FAILED) {
- perror("mmap");
- return 1;
- }
-
- if (p.features & IORING_FEAT_SINGLE_MMAP) {
- cq_ptr = sq_ptr;
- } else {
- /* Map in the completion queue ring buffer in older kernels separately */
- cq_ptr = mmap(0, cring_sz, PROT_READ | PROT_WRITE,
- MAP_SHARED | MAP_POPULATE,
- ring_fd, IORING_OFF_CQ_RING);
- if (cq_ptr == MAP_FAILED) {
- perror("mmap");
- return 1;
- }
- }
- /* Save useful fields for later easy reference */
- sring_tail = sq_ptr + p.sq_off.tail;
- sring_mask = sq_ptr + p.sq_off.ring_mask;
- sring_array = sq_ptr + p.sq_off.array;
-
- /* Map in the submission queue entries array */
- sqes = mmap(0, p.sq_entries * sizeof(struct io_uring_sqe),
- PROT_READ | PROT_WRITE, MAP_SHARED | MAP_POPULATE,
- ring_fd, IORING_OFF_SQES);
- if (sqes == MAP_FAILED) {
- perror("mmap");
- return 1;
- }
-
- /* Save useful fields for later easy reference */
- cring_head = cq_ptr + p.cq_off.head;
- cring_tail = cq_ptr + p.cq_off.tail;
- cring_mask = cq_ptr + p.cq_off.ring_mask;
- cqes = cq_ptr + p.cq_off.cqes;
-
- return 0;
-}
-
-/*
-* Read from completion queue.
-* In this function, we read completion events from the completion queue.
-* We dequeue the CQE, update and head and return the result of the operation.
-* */
-
-int read_from_cq() {
- struct io_uring_cqe *cqe;
- unsigned head;
-
- /* Read barrier */
- head = io_uring_smp_load_acquire(cring_head);
- /*
- * Remember, this is a ring buffer. If head == tail, it means that the
- * buffer is empty.
- * */
- if (head == *cring_tail)
- return -1;
-
- /* Get the entry */
- cqe = &cqes[head & (*cring_mask)];
- if (cqe->res < 0)
- fprintf(stderr, "Error: %s\\n", strerror(abs(cqe->res)));
-
- head++;
-
- /* Write barrier so that update to the head are made visible */
- io_uring_smp_store_release(cring_head, head);
-
- return cqe->res;
-}
-
-/*
-* Submit a read or a write request to the submission queue.
-* */
-
-int submit_to_sq(int fd, int op) {
- unsigned index, tail;
-
- /* Add our submission queue entry to the tail of the SQE ring buffer */
- tail = *sring_tail;
- index = tail & *sring_mask;
- struct io_uring_sqe *sqe = &sqes[index];
- /* Fill in the parameters required for the read or write operation */
- sqe->opcode = op;
- sqe->fd = fd;
- sqe->addr = (unsigned long) buff;
- if (op == IORING_OP_READ) {
- memset(buff, 0, sizeof(buff));
- sqe->len = BLOCK_SZ;
- }
- else {
- sqe->len = strlen(buff);
- }
- sqe->off = offset;
-
- sring_array[index] = index;
- tail++;
-
- /* Update the tail */
- io_uring_smp_store_release(sring_tail, tail);
-
- /*
- * Tell the kernel we have submitted events with the io_uring_enter()
- * system call. We also pass in the IORING_ENTER_GETEVENTS flag which
- * causes the io_uring_enter() call to wait until min_complete
- * (the 3rd param) events complete.
- * */
- int ret = io_uring_enter(ring_fd, 1,1,
- IORING_ENTER_GETEVENTS);
- if(ret < 0) {
- perror("io_uring_enter");
- return -1;
- }
-
- return ret;
-}
-
-int main(int argc, char *argv[]) {
- int res;
-
- /* Setup io_uring for use */
- if(app_setup_uring()) {
- fprintf(stderr, "Unable to setup uring!\\n");
- return 1;
- }
-
- /*
- * A while loop that reads from stdin and writes to stdout.
- * Breaks on EOF.
- */
- while (1) {
- /* Initiate read from stdin and wait for it to complete */
- submit_to_sq(STDIN_FILENO, IORING_OP_READ);
- /* Read completion queue entry */
- res = read_from_cq();
- if (res > 0) {
- /* Read successful. Write to stdout. */
- submit_to_sq(STDOUT_FILENO, IORING_OP_WRITE);
- read_from_cq();
- } else if (res == 0) {
- /* reached EOF */
- break;
- }
- else if (res < 0) {
- /* Error reading file */
- fprintf(stderr, "Error: %s\\n", strerror(abs(res)));
- break;
- }
- offset += res;
- }
-
- return 0;
-}
-.EE
-.SH SEE ALSO
-.BR io_uring_enter (2)
-.BR io_uring_register (2)
-.BR io_uring_setup (2)
diff --git a/src/liburing/man/io_uring_buf_ring_add.3 b/src/liburing/man/io_uring_buf_ring_add.3
deleted file mode 100644
index 49e08e9e0648..000000000000
--- a/src/liburing/man/io_uring_buf_ring_add.3
+++ /dev/null
@@ -1,61 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_buf_ring_add 3 "May 18, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_buf_ring_add \- add buffers to a shared buffer ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_buf_ring_add(struct io_uring_buf_ring *" br ",
-.BI " void *" addr ",
-.BI " unsigned int " len ",
-.BI " unsigned short " bid ",
-.BI " int " mask ",
-.BI " int " buf_offset ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_buf_ring_add (3)
-adds a new buffer to the shared buffer ring
-.IR br .
-The buffer address is indicated by
-.I addr
-and is of
-.I len
-bytes of length.
-.I bid
-is the buffer ID, which will be returned in the CQE.
-.I mask
-is the size mask of the ring, available from
-.BR io_uring_buf_ring_mask (3) .
-.I buf_offset
-is the offset to insert at from the current tail. If just one buffer is provided
-before the ring tail is committed with
-.BR io_uring_buf_ring_advance (3)
-or
-.BR io_uring_buf_ring_cq_advance (3),
-then
-.I buf_offset
-should be 0. If buffers are provided in a loop before being committed, the
-.I buf_offset
-must be incremented by one for each buffer added.
-
-.SH RETURN VALUE
-None
-.SH NOTES
-liburing (or the kernel, for that matter) doesn't care about what buffer ID maps
-to what buffer, and in fact when recycling buffers after use, the application is
-free to add a different buffer into the same buffer ID location. All that
-matters is that the application knows what a given buffer ID in time corresponds
-to in terms of virtual memory. There's no liburing or kernel assumption that
-these mappings are persistent over time, they can very well be different every
-time a given buffer ID is added to the provided buffer ring.
-.SH SEE ALSO
-.BR io_uring_register_buf_ring (3),
-.BR io_uring_buf_ring_mask (3),
-.BR io_uring_buf_ring_advance (3),
-.BR io_uring_buf_ring_cq_advance (3)
diff --git a/src/liburing/man/io_uring_buf_ring_advance.3 b/src/liburing/man/io_uring_buf_ring_advance.3
deleted file mode 100644
index f2dc90b5d0a3..000000000000
--- a/src/liburing/man/io_uring_buf_ring_advance.3
+++ /dev/null
@@ -1,31 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_buf_ring_advance 3 "May 18, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_buf_ring_advance \- advance index of provided buffer in buffer ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_buf_ring_advance(struct io_uring_buf_ring *" br ",
-.BI " int " count ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_buf_ring_advance (3)
-commits
-.I count
-previously added buffers to the shared buffer ring
-.IR br ,
-making them visible to the kernel and hence consumable. This passes ownership
-of the buffer to the ring.
-
-.SH RETURN VALUE
-None
-.SH SEE ALSO
-.BR io_uring_register_buf_ring (3),
-.BR io_uring_buf_ring_add (3),
-.BR io_uring_buf_ring_cq_advance (3)
diff --git a/src/liburing/man/io_uring_buf_ring_available.3 b/src/liburing/man/io_uring_buf_ring_available.3
deleted file mode 100644
index c1dc8b806688..000000000000
--- a/src/liburing/man/io_uring_buf_ring_available.3
+++ /dev/null
@@ -1,47 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_buf_ring_available 3 "Jan 11, 2024" "liburing-2.6" "liburing Manual"
-.SH NAME
-io_uring_buf_ring_available \- return number of unconsumed provided ring buffer entries
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_buf_ring_available(struct io_uring *" ring ",
-.BI " struct io_uring_buf_ring *" br ",
-.BI " unsigned short " bgid ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_buf_ring_available (3)
-helper returns the number of unconsumed (by the kernel) entries in the
-.IR br
-provided buffer group belonging to the io_uring
-.IR ring
-and identified by the buffer group ID
-.IR bgid.
-
-Since the head of the provided buffer ring is only visible to the kernel, it's
-impossible to otherwise know how many unconsumed entries exist in the given
-provided buffer ring. This function query the kernel to return that number.
-Available since kernel 6.8.
-
-.SH NOTES
-The returned number of entries reflect the amount of unconsumed entries at the
-time that it was queried. If inflight IO exists that may consume provided
-buffers from this buffer group, then the returned value is inherently racy.
-.SH RETURN VALUE
-Returns the number of unconsumed entries on success, which may be 0. In case
-of error, may return
-.BR -ENOENT
-if the specified buffer group doesn't exist, or
-.BR -EINVAL
-if the buffer group isn't of the correct type, or if the kernel doesn't
-support this feature.
-.SH SEE ALSO
-.BR io_uring_register_buf_ring (3),
-.BR io_uring_buf_ring_add (3),
-.BR io_uring_buf_ring_cq_advance (3)
diff --git a/src/liburing/man/io_uring_buf_ring_cq_advance.3 b/src/liburing/man/io_uring_buf_ring_cq_advance.3
deleted file mode 100644
index d7ada5d0bd4d..000000000000
--- a/src/liburing/man/io_uring_buf_ring_cq_advance.3
+++ /dev/null
@@ -1,55 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_buf_ring_cq_advance 3 "May 18, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_buf_ring_cq_advance \- advance index of provided buffer and CQ ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_buf_ring_cq_advance(struct io_uring *" ring ",
-.BI " struct io_uring_buf_ring *" br ",
-.BI " int " count ");"
-.PP
-.BI "void __io_uring_buf_ring_cq_advance(struct io_uring *" ring ",
-.BI " struct io_uring_buf_ring *" br ",
-.BI " int " cq_count ",
-.BI " int " buf_count ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_buf_ring_cq_advance (3)
-commits
-.I count
-previously added buffers to the shared buffer ring
-.IR br ,
-making them visible to the kernel and hence consumable. This passes ownership
-of the buffer to the ring. At the same time, it advances the CQ ring of
-.I ring
-by
-.I count
-amount. This effectively bundles both a
-.BR io_uring_buf_ring_advance (3)
-call and a
-.BR io_uring_cq_advance (3)
-into one operation. Since updating either ring index entails a store memory
-barrier, doing both at once is more efficient.
-
-The
-.BR __io_uring_buf_ring_cq_advance (3)
-function performs the same operation, except it splits the counts into two
-separate values. It advances the CQ ring by
-.I cq_count
-entries, and the buffer ring by
-.I buf_count
-entries rather than increment both by the same value.
-
-.SH RETURN VALUE
-None
-.SH SEE ALSO
-.BR io_uring_register_buf_ring (3),
-.BR io_uring_buf_ring_add (3),
-.BR io_uring_buf_ring_advance (3)
diff --git a/src/liburing/man/io_uring_buf_ring_init.3 b/src/liburing/man/io_uring_buf_ring_init.3
deleted file mode 100644
index beabed8ce152..000000000000
--- a/src/liburing/man/io_uring_buf_ring_init.3
+++ /dev/null
@@ -1,36 +0,0 @@
-.\" Copyright (C) 2022 Dylan Yudaken <dylany@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_buf_ring_init 3 "June 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_buf_ring_init \- Initialise a buffer ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_buf_ring_init(struct io_uring_buf_ring *" br ");"
-.fi
-.SH DESCRIPTION
-.PP
-.BR io_uring_buf_ring_init (3)
-initialises
-.IR br
-so that it is ready to be used. It may be called after
-.BR io_uring_register_buf_ring (3)
-but must be called before the buffer ring is used in any other way.
-
-.SH RETURN VALUE
-None
-
-.SH NOTES
-Unless manual setup is needed, it's recommended to use
-.BR io_uring_setup_buf_ring (3)
-as it provides a simpler way to setup a provided buffer ring.
-.
-.SH SEE ALSO
-.BR io_uring_register_buf_ring (3),
-.BR io_uring_setup_buf_ring (3),
-.BR io_uring_buf_ring_add (3)
-.BR io_uring_buf_ring_advance (3),
-.BR io_uring_buf_ring_cq_advance (3)
diff --git a/src/liburing/man/io_uring_buf_ring_mask.3 b/src/liburing/man/io_uring_buf_ring_mask.3
deleted file mode 100644
index 9160663053fd..000000000000
--- a/src/liburing/man/io_uring_buf_ring_mask.3
+++ /dev/null
@@ -1,27 +0,0 @@
-.\" Copyright (C) 2022 Dylan Yudaken <dylany@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_buf_ring_mask 3 "June 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_buf_ring_mask \- Calculate buffer ring mask size
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_buf_ring_mask(__u32 " ring_entries ");"
-.fi
-.SH DESCRIPTION
-.PP
-.BR io_uring_buf_ring_mask (3)
-calculates the appropriate size mask for a buffer ring.
-.IR ring_entries
-is the ring entries as specified in
-.BR io_uring_register_buf_ring (3) .
-
-.SH RETURN VALUE
-Size mask for the buffer ring.
-
-.SH SEE ALSO
-.BR io_uring_register_buf_ring (3),
-.BR io_uring_buf_ring_add (3)
diff --git a/src/liburing/man/io_uring_check_version.3 b/src/liburing/man/io_uring_check_version.3
deleted file mode 100644
index b7d771ab0a33..000000000000
--- a/src/liburing/man/io_uring_check_version.3
+++ /dev/null
@@ -1,72 +0,0 @@
-.\" Copyright (C) 2022 Christian Hergert <chergert@redhat.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_check_version 3 "December 1, 2022" "liburing-2.4" "liburing Manual"
-.SH NAME
-io_uring_check_version \- functions and macros to check the liburing version
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "bool io_uring_check_version(int " major ", int " minor ");"
-.BI "IO_URING_CHECK_VERSION(" major ", " minor ");"
-.PP
-.BI "int io_uring_major_version(void);"
-.BI "IO_URING_VERSION_MAJOR;"
-.PP
-.BI "int io_uring_minor_version(void);"
-.BI "IO_URING_VERSION_MINOR;"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_check_version (3)
-function returns
-.I false
-if the liburing library loaded by the dynamic linker is greater-than
-or equal-to the
-.I major
-and
-.I minor
-numbers provided.
-
-.PP
-The
-.BR IO_URING_CHECK_VERSION (3)
-macro returns
-.I 0
-if the liburing library being compiled against is greater-than or equal-to the
-.I major
-and
-.I minor
-numbers provided.
-
-.PP
-The
-.BR io_uring_major_version (3)
-function returns the
-.I major
-version number of the liburing library loaded by the dynamic linker.
-
-.PP
-The
-.BR IO_URING_VERSION_MAJOR (3)
-macro returns the
-.I major
-version number of the liburing library being compiled against.
-
-.PP
-The
-.BR io_uring_minor_version (3)
-function returns the
-.I minor
-version number of the liburing library loaded by the dynamic linker.
-
-.PP
-The
-.BR IO_URING_VERSION_MINOR (3)
-macro returns the
-.I minor
-version number of the liburing library being compiled against.
-
diff --git a/src/liburing/man/io_uring_clone_buffers.3 b/src/liburing/man/io_uring_clone_buffers.3
deleted file mode 100644
index 3f0a881bf5b0..000000000000
--- a/src/liburing/man/io_uring_clone_buffers.3
+++ /dev/null
@@ -1,168 +0,0 @@
-.\" Copyright (C) 2024 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_clone_buffers 3 "September 12, 2024" "liburing-2.9" "liburing Manual"
-.SH NAME
-io_uring_clone_buffers \- Clones registered buffers between rings
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_clone_buffers(struct io_uring *" dst ","
-.BI " struct io_uring * " src ");"
-.PP
-.BI "int __io_uring_clone_buffers(struct io_uring *" dst ","
-.BI " struct io_uring * " src ","
-.BI " unsigned int " flags ");"
-.PP
-.BI "int io_uring_clone_buffers_offset(struct io_uring *" dst ","
-.BI " struct io_uring * " src ","
-.BI " unsigned int " dst_off ","
-.BI " unsigned int " src_off ","
-.BI " unsigned int " nr ","
-.BI " unsigned int " flags ");"
-.PP
-.BI "int __io_uring_clone_buffers_offset(struct io_uring *" dst ","
-.BI " struct io_uring * " src ","
-.BI " unsigned int " dst_off ","
-.BI " unsigned int " src_off ","
-.BI " unsigned int " nr ","
-.BI " unsigned int " flags ");"
-.PP
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_clone_buffers (3)
-function clones registered buffers from the ring indicated by
-.IR src
-to the ring indicated by
-.IR dst .
-Upon successful completion of this operation,
-.IR src
-and
-.IR dst
-will have the same set of registered buffers. This operation is identical to
-performing a
-.BR io_uring_register_buffers (3)
-operation on the
-.IR dst
-ring, if the
-.IR src
-ring previously had that same buffer registration operating done.
-
-The
-.IR dst
-ring must not have any buffers currently registered. If buffers are currently
-registered on the destination ring, they must be unregistered with
-.BR io_uring_unregister_buffers (3)
-first.
-
-For
-.BR __io_uring_clone_buffers (3) ,
-the only difference is that it takes a
-.IR flags
-argument. By default, if the destination ring has a registered file descriptor
-through
-.BR io_uring_register_ring_fd (3)
-AND the calling application is not the thread that registered that ring, then
-the kernel doesn't know how to look up the destination. This is problematic
-as
-.BR io_uring_clone_buffers (3)
-defaults to using the registered index if the destination is setup as such.
-Use
-.BR __io_uring_clone_buffers (3)
-which doesn't set
-.B IORING_REGISTER_SRC_REGISTERED
-by default. This requires the application to still have the original ring file
-descriptor open. See below for the flag definition.
-
-Available since kernel 6.12.
-
-The
-.BR io_uring_clone_buffers_offset (3)
-function also clones buffers from the
-.IR src
-ring to the
-.IR dst
-ring, however it supports cloning only a subset of the buffers, where
-.BR io_uring_clone_buffers (3)
-always clones all of them.
-.IR dst_off
-indicates at what offset cloning should start in the destination,
-.IR src_off
-indicates at what offset cloning should start in the source, and
-.IR nr
-indicates how many buffers to clone at the given offset. If both
-.IR dst_off ,
-.IR src_off ,
-and
-.IR nr
-are given as
-.B 0 ,
-then
-.BR io_uring_clone_buffers_offset (3)
-performs the same action as
-.BR io_uring_clone_buffers (3) .
-
-While
-.BR io_uring_clone_buffers_offset (3)
-sets
-.B IORING_REGISTER_SRC_REGISTERED
-by default, the
-.BR __io_uring_clone_buffers_offset (3)
-does not. See the explanation for
-.BR __io_uring_clone_buffers (3)
-for details.
-
-.IR flags
-may be set to the following value:
-.TP
-.B IORING_REGISTER_SRC_REGISTERED
-If the source ring is registered AND the calling thread is the one that
-originally registered its ring fd, then this flag may be set to lookup the
-registered index rather than use the normal file descriptor. If the normal
-file descriptor wasn't closed after registering it, there's no need to set
-this flag.
-.TP
-.B 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.
-.PP
-
-Available since kernel 6.13.
-
-.SH NOTES
-The source and target ring must shared address spaces, and hence internal
-kernel accounting.
-.SH RETURN VALUE
-On success
-.BR io_uring_clone_buffers (3)
-and
-.BR io_uring_clone_buffers_offset (3)
-return 0.
-On failure, they returns
-.BR -errno ,
-specifically
-.TP
-.B -EBUSY
-The destination ring already has buffers registered, and
-.B IORING_REGISTER_DST_REPLACE
-wasn't set.
-.TP
-.B -ENOMEM
-The kernel ran out of memory.
-.TP
-.B -ENXIO
-The source ring doesn't have any buffers registered.
-.SH SEE ALSO
-.BR io_uring_register (2),
-.BR io_uring_unregister_buffers (3),
-.BR io_uring_register_buffers (3),
-.BR io_uring_prep_read_fixed (3),
-.BR io_uring_prep_write_fixed (3)
diff --git a/src/liburing/man/io_uring_clone_buffers_offset.3 b/src/liburing/man/io_uring_clone_buffers_offset.3
deleted file mode 120000
index 6d7e5483aa41..000000000000
--- a/src/liburing/man/io_uring_clone_buffers_offset.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_clone_buffers.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_close_ring_fd.3 b/src/liburing/man/io_uring_close_ring_fd.3
deleted file mode 100644
index b5963c9d47b4..000000000000
--- a/src/liburing/man/io_uring_close_ring_fd.3
+++ /dev/null
@@ -1,43 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\" Copyright (C) 2022 Josh Triplett <josh@joshtriplett.org>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_close_ring_fd 3 "September 25, 2022" "liburing-2.4" "liburing Manual"
-.SH NAME
-io_uring_close_ring_fd \- close a ring file descriptor and use it only via registered index
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_close_ring_fd(struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-.BR io_uring_close_ring_fd (3)
-closes the ring file descriptor, which must have been previously registered.
-The file will remain open, but accessible only via the registered index, not
-via any file descriptor. Subsequent liburing calls will continue to work, using
-the registered ring fd.
-
-The kernel must support
-.BR IORING_FEAT_REG_REG_RING .
-
-Libraries that must avoid disrupting their users' uses of file descriptors, and
-must continue working even in the face of
-.BR close_range (2)
-and similar, can use
-.BR io_uring_close_ring_fd (3)
-to work with liburing without having any open file descriptor.
-
-.SH NOTES
-Each thread that wants to make use of io_uring must register the fd. A library
-that may get called from arbitrary theads may need to detect when it gets
-called on a previously unseen thread and create and register a ring for that
-thread.
-.SH RETURN VALUE
-Returns 1 on success, or
-.BR -errno
-on error.
-.SH SEE ALSO
-.BR io_uring_register_ring_fd (3)
diff --git a/src/liburing/man/io_uring_cq_advance.3 b/src/liburing/man/io_uring_cq_advance.3
deleted file mode 100644
index fae257223cf4..000000000000
--- a/src/liburing/man/io_uring_cq_advance.3
+++ /dev/null
@@ -1,49 +0,0 @@
-.\" Copyright (C) 2022 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_cq_advance 3 "January 25, 2022" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_cq_advance \- mark one or more io_uring completion events as consumed
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_cq_advance(struct io_uring *" ring ","
-.BI " unsigned " nr ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_cq_advance (3)
-function marks
-.I nr
-IO completions belonging to the
-.I ring
-param as consumed.
-
-After the caller has submitted a request with
-.BR io_uring_submit (3),
-the application can retrieve the completion with
-.BR io_uring_wait_cqe (3),
-.BR io_uring_peek_cqe (3),
-or any of the other CQE retrieval helpers, and mark it as consumed with
-.BR io_uring_cqe_seen (3).
-
-The function
-.BR io_uring_cqe_seen (3)
-calls the function
-.BR io_uring_cq_advance (3).
-
-Completions must be marked as seen, so their slot can get reused. Failure to do
-so will result in the same completion being returned on the next invocation.
-
-.SH RETURN VALUE
-None
-.SH SEE ALSO
-.BR io_uring_submit (3),
-.BR io_uring_wait_cqe (3),
-.BR io_uring_peek_cqe (3),
-.BR io_uring_wait_cqes (3),
-.BR io_uring_wait_cqe_timeout (3),
-.BR io_uring_cqe_seen (3)
diff --git a/src/liburing/man/io_uring_cq_has_overflow.3 b/src/liburing/man/io_uring_cq_has_overflow.3
deleted file mode 100644
index 8ca0ba86571e..000000000000
--- a/src/liburing/man/io_uring_cq_has_overflow.3
+++ /dev/null
@@ -1,31 +0,0 @@
-.\" Copyright (C) 2022 Dylan Yudaken <dylany@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_cq_has_overflow 3 "September 5, 2022" "liburing-2.3" "liburing Manual"
-.SH NAME
-io_uring_cq_has_overflow \- returns if there are overflow entries waiting to move to the CQ ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "bool io_uring_cq_has_overflow(const struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_cq_has_overflow (3)
-function informs the application if CQ entries have overflowed and are waiting to be flushed to
-the CQ ring. For example using
-.BR io_uring_get_events (3)
-.SH NOTES
-Using this function is only valid if the ring has
-.B IORING_FEAT_NODROP
-set, as it's checking for a flag set by kernels supporting that feature. For
-really old kernels that don't support this feature, if CQE overflow is
-experienced the CQEs are lost. If that happens, the CQ ring overflow offset
-will get incremented.
-.SH RETURN VALUE
-True if there are CQ entries waiting to be flushed to the CQ ring.
-.SH SEE ALSO
-.BR io_uring_get_events (3)
diff --git a/src/liburing/man/io_uring_cq_ready.3 b/src/liburing/man/io_uring_cq_ready.3
deleted file mode 100644
index 641828a840d3..000000000000
--- a/src/liburing/man/io_uring_cq_ready.3
+++ /dev/null
@@ -1,26 +0,0 @@
-.\" Copyright (C) 2022 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_cq_ready 3 "January 25, 2022" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_cq_ready \- returns number of unconsumed ready entries in the CQ ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "unsigned io_uring_cq_ready(const struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_cq_ready (3)
-function returns the number of unconsumed entries that are ready belonging to the
-.I ring
-param.
-
-.SH RETURN VALUE
-Returns the number of unconsumed ready entries in the CQ ring.
-.SH SEE ALSO
-.BR io_uring_submit (3),
-.BR io_uring_wait_cqe (3)
diff --git a/src/liburing/man/io_uring_cqe_get_data.3 b/src/liburing/man/io_uring_cqe_get_data.3
deleted file mode 100644
index a4d2988a49d9..000000000000
--- a/src/liburing/man/io_uring_cqe_get_data.3
+++ /dev/null
@@ -1,53 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_cqe_get_data 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_cqe_get_data \- get user data for completion event
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void *io_uring_cqe_get_data(struct io_uring_cqe *" cqe ");"
-.BI "
-.BI "__u64 io_uring_cqe_get_data64(struct io_uring_cqe *" cqe ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_cqe_get_data (3)
-function returns the user_data with the completion queue entry
-.IR cqe
-as a data pointer.
-
-The
-.BR io_uring_cqe_get_data64 (3)
-function returns the user_data with the completion queue entry
-.IR cqe
-as a 64-bit data value.
-
-After the caller has received a completion queue entry (CQE) with
-.BR io_uring_wait_cqe (3),
-the application can call
-.BR io_uring_cqe_get_data (3)
-or
-.BR io_uring_cqe_get_data64 (3)
-function to retrieve the
-.I user_data
-value. This requires that
-.I user_data
-has been set earlier with the function
-.BR io_uring_sqe_set_data (3)
-or
-.BR io_uring_sqe_set_data64 (3).
-
-.SH RETURN VALUE
-If the
-.I user_data
-value has been set before submitting the request, it will be returned.
-Otherwise, the return value is undefined.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_sqe_set_data (3),
-.BR io_uring_sqe_submit (3)
diff --git a/src/liburing/man/io_uring_cqe_get_data64.3 b/src/liburing/man/io_uring_cqe_get_data64.3
deleted file mode 120000
index 51991c2a145e..000000000000
--- a/src/liburing/man/io_uring_cqe_get_data64.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_cqe_get_data.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_cqe_seen.3 b/src/liburing/man/io_uring_cqe_seen.3
deleted file mode 100644
index 5c9cd4e5ff40..000000000000
--- a/src/liburing/man/io_uring_cqe_seen.3
+++ /dev/null
@@ -1,41 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_cqe_seen 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_cqe_seen \- mark io_uring completion event as consumed
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_cqe_seen(struct io_uring *" ring ","
-.BI " struct io_uring_cqe *" cqe ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_cqe_seen (3)
-function marks the IO completion
-.I cqe
-belonging to the
-.I ring
-param as consumed.
-
-After the caller has submitted a request with
-.BR io_uring_submit (3),
-the application can retrieve the completion with
-.BR io_uring_wait_cqe (3),
-.BR io_uring_peek_cqe (3),
-or any of the other CQE retrieval helpers, and mark it as consumed with
-.BR io_uring_cqe_seen (3).
-
-Completions must be marked as completed so their slot can get reused.
-.SH RETURN VALUE
-None
-.SH SEE ALSO
-.BR io_uring_submit (3),
-.BR io_uring_peek_cqe (3),
-.BR io_uring_wait_cqe (3),
-.BR io_uring_wait_cqes (3),
-.BR io_uring_wait_cqe_timeout (3)
diff --git a/src/liburing/man/io_uring_enable_rings.3 b/src/liburing/man/io_uring_enable_rings.3
deleted file mode 100644
index a01713bea126..000000000000
--- a/src/liburing/man/io_uring_enable_rings.3
+++ /dev/null
@@ -1,40 +0,0 @@
-.\" Copyright (C) 2023 nick black <dankamongmen@gmail.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_enable_rings 3 "July 26, 2024" "liburing-2.7" "liburing Manual"
-.SH NAME
-io_uring_enable_rings \- enable a disabled ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_enable_rings(struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_enable_rings (3)
-function enables a ring after having created it with the
-.B IORING_SETUP_R_DISABLED
-flag to
-.BR io_uring_queue_init (3)
-
-It is not possible to submit work to such a ring until this
-function has been successfully called.
-
-.SH RETURN VALUE
-.BR io_uring_enable_rings (3)
-returns 0 on success. It otherwise returns a negative error code.
-It does not write to
-.BR errno .
-
-.SH ERRORS
-.TP
-.B EBADFD
-The ring was not disabled.
-
-.SH SEE ALSO
-.BR io_uring_queue_init (3),
-.BR io_uring_register (2),
-.BR io_uring_setup (2)
diff --git a/src/liburing/man/io_uring_enter.2 b/src/liburing/man/io_uring_enter.2
deleted file mode 100644
index 99c0ab222675..000000000000
--- a/src/liburing/man/io_uring_enter.2
+++ /dev/null
@@ -1,2066 +0,0 @@
-.\" Copyright (C) 2019 Jens Axboe <axboe@kernel.dk>
-.\" Copyright (C) 2019 Red Hat, Inc.
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_enter 2 2019-01-22 "Linux" "Linux Programmer's Manual"
-.SH NAME
-io_uring_enter \- initiate and/or complete asynchronous I/O
-.SH SYNOPSIS
-.nf
-.BR "#include <liburing.h>"
-.PP
-.BI "int io_uring_enter(unsigned int " fd ", unsigned int " to_submit ,
-.BI " unsigned int " min_complete ", unsigned int " flags ,
-.BI " sigset_t *" sig );
-.PP
-.BI "int io_uring_enter2(unsigned int " fd ", unsigned int " to_submit ,
-.BI " unsigned int " min_complete ", unsigned int " flags ,
-.BI " void *" arg ", size_t " sz );
-.fi
-.PP
-.SH DESCRIPTION
-.PP
-.BR io_uring_enter (2)
-is used to initiate and complete I/O using the shared submission and
-completion queues setup by a call to
-.BR io_uring_setup (2).
-A single call can both submit new I/O and wait for completions of I/O
-initiated by this call or previous calls to
-.BR io_uring_enter (2).
-
-.I fd
-is the file descriptor returned by
-.BR io_uring_setup (2).
-.I to_submit
-specifies the number of I/Os to submit from the submission queue.
-.I flags
-is a bitmask of the following values:
-.TP
-.B IORING_ENTER_GETEVENTS
-If this flag is set, then the system call will wait for the specified
-number of events in
-.I min_complete
-before returning. This flag can be set along with
-.I to_submit
-to both submit and complete events in a single system call.
-If this flag is set either the flag
-.B IORING_SETUP_DEFER_TASKRUN
-must not be set or the thread issuing the syscall must be the thread that
-created the io_uring associated with
-.I fd,
-or be the thread that enabled the ring originally created with
-.B IORING_SETUP_R_DISABLED
-via
-.BR io_uring_register (2)
-or
-.BR io_uring_enable_rings (3).
-.TP
-.B IORING_ENTER_SQ_WAKEUP
-If the ring has been created with
-.B IORING_SETUP_SQPOLL,
-then this flag asks the kernel to wakeup the SQ kernel thread to submit IO.
-.TP
-.B IORING_ENTER_SQ_WAIT
-If the ring has been created with
-.B IORING_SETUP_SQPOLL,
-then the application has no real insight into when the SQ kernel thread has
-consumed entries from the SQ ring. This can lead to a situation where the
-application can no longer get a free SQE entry to submit, without knowing
-when one will become available as the SQ kernel thread consumes them. If
-the system call is used with this flag set, then it will wait until at least
-one entry is free in the SQ ring.
-.TP
-.B IORING_ENTER_EXT_ARG
-By default,
-.I arg
-is a
-.I sigset_t
-pointer. If
-.B IORING_ENTER_EXT_ARG
-is set (supported since kernel 5.11), then
-.I arg
-is instead a pointer to a
-.I struct io_uring_getevents_arg
-and
-.I argsz
-must be set to the size of this structure. The definition is as follows:
-
-.nf
-.BI "struct io_uring_getevents_arg {
-.BI " __u64 sigmask;
-.BI " __u32 sigmask_sz;
-.BI " __u32 pad;
-.BI " __u64 ts;
-.BI "};
-.fi
-
-which allows passing in both a signal mask as well as pointer to a
-.I struct __kernel_timespec
-timeout value. If
-.I ts
-is set to a valid pointer, then this time value indicates the timeout for
-waiting on events. If an application is waiting on events and wishes to
-stop waiting after a specified amount of time, then this can be accomplished
-directly in version 5.11 and newer by using this feature.
-.TP
-.B IORING_ENTER_REGISTERED_RING
-If the ring file descriptor has been registered through use of
-.BR IORING_REGISTER_RING_FDS ,
-then setting this flag will tell the kernel that the
-.I ring_fd
-passed in is the registered ring offset rather than a normal file descriptor.
-
-.TP
-.B IORING_ENTER_ABS_TIMER
-
-When this flag is set, the timeout argument passed in
-.I struct io_uring_getevents_arg
-will be interpreted as an absolute
-time of the registered clock (see
-.BR IORING_REGISTER_CLOCK)
-until which the waiting should end.
-
-Available since 6.12
-
-.TP
-.B IORING_ENTER_EXT_ARG_REG
-
-When this flag is set,
-.IR arg
-is not a pointer to a
-.IR struct io_uring_getevents_arg ,
-but merely an offset into an area of wait regions previously registered with
-.BR io_uring_register (2)
-using the
-.B IORING_REGISTER_MEM_REGION
-operation. Available since 6.13
-
-.PP
-.PP
-If the io_uring instance was configured for polling, by specifying
-.B IORING_SETUP_IOPOLL
-in the call to
-.BR io_uring_setup (2),
-then min_complete has a slightly different meaning. Passing a value
-of 0 instructs the kernel to return any events which are already complete,
-without blocking. If
-.I min_complete
-is a non-zero value, the kernel will still return immediately if any
-completion events are available. If no event completions are
-available, then the call will poll either until one or more
-completions become available, or until the process has exceeded its
-scheduler time slice.
-
-Note that, for interrupt driven I/O (where
-.B IORING_SETUP_IOPOLL
-was not specified in the call to
-.BR io_uring_setup (2)),
-an application may check the completion queue for event completions
-without entering the kernel at all.
-.PP
-When the system call returns that a certain amount of SQEs have been
-consumed and submitted, it's safe to reuse SQE entries in the ring. This is
-true even if the actual IO submission had to be punted to async context,
-which means that the SQE may in fact not have been submitted yet. If the
-kernel requires later use of a particular SQE entry, it will have made a
-private copy of it.
-
-.I sig
-is a pointer to a signal mask (see
-.BR sigprocmask (2));
-if
-.I sig
-is not NULL,
-.BR io_uring_enter (2)
-first replaces the current signal mask by the one pointed to by
-.IR sig ,
-then waits for events to become available in the completion queue, and
-then restores the original signal mask. The following
-.BR io_uring_enter (2)
-call:
-.PP
-.in +4n
-.EX
-ret = io_uring_enter(fd, 0, 1, IORING_ENTER_GETEVENTS, &sig);
-.EE
-.in
-.PP
-is equivalent to
-.I atomically
-executing the following calls:
-.PP
-.in +4n
-.EX
-pthread_sigmask(SIG_SETMASK, &sig, &orig);
-ret = io_uring_enter(fd, 0, 1, IORING_ENTER_GETEVENTS, NULL);
-pthread_sigmask(SIG_SETMASK, &orig, NULL);
-.EE
-.in
-.PP
-See the description of
-.BR pselect (2)
-for an explanation of why the
-.I sig
-parameter is necessary.
-
-Submission queue entries are represented using the following data
-structure:
-.PP
-.in +4n
-.EX
-/*
- * IO submission data structure (Submission Queue Entry)
- */
-struct io_uring_sqe {
- __u8 opcode; /* type of operation for this sqe */
- __u8 flags; /* IOSQE_ flags */
- __u16 ioprio; /* ioprio for the request */
- __s32 fd; /* file descriptor to do IO on */
- union {
- __u64 off; /* offset into file */
- __u64 addr2;
- struct {
- __u32 cmd_op;
- __u32 __pad1;
- };
- };
- union {
- __u64 addr; /* pointer to buffer or iovecs */
- __u64 splice_off_in;
- struct {
- __u32 level;
- __u32 optname;
- };
- };
- __u32 len; /* buffer size or number of iovecs */
- union {
- __kernel_rwf_t rw_flags;
- __u32 fsync_flags;
- __u16 poll_events; /* compatibility */
- __u32 poll32_events; /* word-reversed for BE */
- __u32 sync_range_flags;
- __u32 msg_flags;
- __u32 timeout_flags;
- __u32 accept_flags;
- __u32 cancel_flags;
- __u32 open_flags;
- __u32 statx_flags;
- __u32 fadvise_advice;
- __u32 splice_flags;
- __u32 rename_flags;
- __u32 unlink_flags;
- __u32 hardlink_flags;
- __u32 xattr_flags;
- __u32 msg_ring_flags;
- __u32 uring_cmd_flags;
- __u32 waitid_flags;
- __u32 futex_flags;
- __u32 install_fd_flags;
- __u32 nop_flags;
- };
- __u64 user_data; /* data to be passed back at completion time */
- /* pack this to avoid bogus arm OABI complaints */
- union {
- /* index into fixed buffers, if used */
- __u16 buf_index;
- /* for grouped buffer selection */
- __u16 buf_group;
- } __attribute__((packed));
- /* personality to use, if used */
- __u16 personality;
- union {
- __s32 splice_fd_in;
- __u32 file_index;
- __u32 optlen;
- struct {
- __u16 addr_len;
- __u16 __pad3[1];
- };
- };
- union {
- struct {
- __u64 addr3;
- __u64 __pad2[1];
- };
- __u64 optval;
- /*
- * If the ring is initialized with IORING_SETUP_SQE128, then
- * this field is used for 80 bytes of arbitrary command data
- */
- __u8 cmd[0];
- };
-};
-.EE
-.in
-.PP
-The
-.I opcode
-describes the operation to be performed. It can be one of:
-.TP
-.B IORING_OP_NOP
-Do not perform any I/O. This is useful for testing the performance of
-the io_uring implementation itself.
-.TP
-.B IORING_OP_READV
-.TP
-.B IORING_OP_WRITEV
-Vectored read and write operations, similar to
-.BR preadv2 (2)
-and
-.BR pwritev2 (2).
-If the file is not seekable,
-.I off
-must be set to zero or -1.
-
-.TP
-.B IORING_OP_READ_FIXED
-.TP
-.B IORING_OP_WRITE_FIXED
-Read from or write to pre-mapped buffers. See
-.BR io_uring_register (2)
-for details on how to setup a context for fixed reads and writes.
-
-.TP
-.B IORING_OP_FSYNC
-File sync. See also
-.BR fsync (2).
-Optionally
-.I off
-and
-.I len
-can be used to specify a range within the file to be synced rather than
-syncing the entire file, which is the default behavior.
-Note that, while I/O is initiated in the order in which it appears in
-the submission queue, completions are unordered. For example, an
-application which places a write I/O followed by an fsync in the
-submission queue cannot expect the fsync to apply to the write. The
-two operations execute in parallel, so the fsync may complete before
-the write is issued to the storage. The same is also true for
-previously issued writes that have not completed prior to the fsync.
-To enforce ordering one may utilize linked SQEs,
-.B IOSQE_IO_DRAIN
-or wait for the arrival of CQEs of requests which have to be ordered
-before a given request before submitting its SQE.
-
-.TP
-.B IORING_OP_POLL_ADD
-Poll the
-.I fd
-specified in the submission queue entry for the events
-specified in the
-.I poll_events
-field. Unlike poll or epoll without
-.BR EPOLLONESHOT ,
-by default this interface always works in one shot mode. That is, once the poll
-operation is completed, it will have to be resubmitted.
-
-If
-.B IORING_POLL_ADD_MULTI
-is set in the SQE
-.I len
-field, then the poll will work in multi shot mode instead. That means it'll
-repatedly trigger when the requested event becomes true, and hence multiple
-CQEs can be generated from this single SQE. The CQE
-.I flags
-field will have
-.B IORING_CQE_F_MORE
-set on completion if the application should expect further CQE entries from
-the original request. If this flag isn't set on completion, then the poll
-request has been terminated and no further events will be generated. This mode
-is available since 5.13.
-
-This command works like
-an async
-.BR poll(2)
-and the completion event result is the returned mask of events.
-
-Without
-.B IORING_POLL_ADD_MULTI
-and the initial poll operation with
-.B IORING_POLL_ADD_MULTI
-the operation is level triggered, i.e. if there is data ready or events
-pending etc. at the time of submission a corresponding CQE will be posted.
-Potential further completions beyond the first caused by a
-.B IORING_POLL_ADD_MULTI
-are edge triggered.
-
-.TP
-.B IORING_OP_POLL_REMOVE
-Remove or update an existing poll request. If found, the
-.I res
-field of the
-.I "struct io_uring_cqe"
-will contain 0. If not found,
-.I res
-will contain
-.B -ENOENT,
-or
-.B -EALREADY
-if the poll request was in the process of completing already.
-
-If
-.B IORING_POLL_UPDATE_EVENTS
-is set in the SQE
-.I len
-field, then the request will update an existing poll request with the mask of
-events passed in with this request. The lookup is based on the
-.I user_data
-field of the original SQE submitted, and this values is passed in the
-.I addr
-field of the SQE.
-If
-.B IORING_POLL_UPDATE_USER_DATA
-is set in the SQE
-.I len
-field, then the request will update the
-.I user_data
-of an existing poll request based on the value passed in the
-.I off
-field. Updating an existing poll is available since 5.13.
-
-.TP
-.B IORING_OP_EPOLL_CTL
-Add, remove or modify entries in the interest list of
-.BR epoll (7).
-See
-.BR epoll_ctl (2)
-for details of the system call.
-.I fd
-holds the file descriptor that represents the epoll instance,
-.I off
-holds the file descriptor to add, remove or modify,
-.I len
-holds the operation (
-.BR EPOLL_CTL_ADD ,
-.BR EPOLL_CTL_DEL ,
-.BR EPOLL_CTL_MOD )
-to perform and,
-.I addr
-holds a pointer to the
-.I epoll_event
-structure. Available since 5.6.
-
-.TP
-.B IORING_OP_SYNC_FILE_RANGE
-Issue the equivalent of a \fBsync_file_range\fR (2) on the file descriptor. The
-.I fd
-field is the file descriptor to sync, the
-.I off
-field holds the offset in bytes, the
-.I len
-field holds the length in bytes, and the
-.I sync_range_flags
-field holds the flags for the command. See also
-.BR sync_file_range (2)
-for the general description of the related system call. Available since 5.2.
-
-.TP
-.B IORING_OP_SENDMSG
-Issue the equivalent of a
-.BR sendmsg(2)
-system call.
-.I fd
-must be set to the socket file descriptor,
-.I addr
-must contain a pointer to the msghdr structure, and
-.I msg_flags
-holds the flags associated with the system call. See also
-.BR sendmsg (2)
-for the general description of the related system call. Available since 5.3.
-
-This command also supports the following modifiers in
-.I ioprio:
-
-.PP
-.in +12
-.B IORING_RECVSEND_POLL_FIRST
-If set, io_uring will assume the socket is currently full and attempting to
-send data will be unsuccessful. For this case, io_uring will arm internal
-poll and trigger a send of the data when there is enough space available.
-This initial send attempt can be wasteful for the case where the socket
-is expected to be full, setting this flag will bypass the initial send
-attempt and go straight to arming poll. If poll does indicate that data can
-be sent, the operation will proceed.
-.EE
-.in
-.PP
-
-.TP
-.B IORING_OP_RECVMSG
-Works just like IORING_OP_SENDMSG, except for
-.BR recvmsg(2)
-instead. See the description of IORING_OP_SENDMSG. Available since 5.3.
-
-This command also supports the following modifiers in
-.I ioprio:
-
-.PP
-.in +12
-.B IORING_RECVSEND_POLL_FIRST
-If set, io_uring will assume the socket is currently empty and attempting to
-receive data will be unsuccessful. For this case, io_uring will arm internal
-poll and trigger a receive of the data when the socket has data to be read.
-This initial receive attempt can be wasteful for the case where the socket
-is expected to be empty, setting this flag will bypass the initial receive
-attempt and go straight to arming poll. If poll does indicate that data is
-ready to be received, the operation will proceed.
-.EE
-.in
-.PP
-
-.TP
-.B IORING_OP_SEND
-Issue the equivalent of a
-.BR send(2)
-system call.
-.I fd
-must be set to the socket file descriptor,
-.I addr
-must contain a pointer to the buffer,
-.I len
-denotes the length of the buffer to send, and
-.I msg_flags
-holds the flags associated with the system call. See also
-.BR send(2)
-for the general description of the related system call. Available since 5.6.
-
-This command also supports the following modifiers in
-.I ioprio:
-
-.PP
-.in +12
-.B IORING_RECVSEND_POLL_FIRST
-If set, io_uring will assume the socket is currently full and attempting to
-send data will be unsuccessful. For this case, io_uring will arm internal
-poll and trigger a send of the data when there is enough space available.
-This initial send attempt can be wasteful for the case where the socket
-is expected to be full, setting this flag will bypass the initial send
-attempt and go straight to arming poll. If poll does indicate that data can
-be sent, the operation will proceed.
-.EE
-.in
-.PP
-
-.TP
-.B IORING_OP_RECV
-Works just like IORING_OP_SEND, except for
-.BR recv(2)
-instead. See the description of IORING_OP_SEND. Available since 5.6.
-
-This command also supports the following modifiers in
-.I ioprio:
-
-.PP
-.in +12
-.B IORING_RECVSEND_POLL_FIRST
-If set, io_uring will assume the socket is currently empty and attempting to
-receive data will be unsuccessful. For this case, io_uring will arm internal
-poll and trigger a receive of the data when the socket has data to be read.
-This initial receive attempt can be wasteful for the case where the socket
-is expected to be empty, setting this flag will bypass the initial receive
-attempt and go straight to arming poll. If poll does indicate that data is
-ready to be received, the operation will proceed.
-.EE
-.in
-.PP
-
-.TP
-.B IORING_OP_TIMEOUT
-This command will register a timeout operation. The
-.I addr
-field must contain a pointer to a struct __kernel_timespec structure,
-.I len
-must contain 1 to signify one __kernel_timespec structure,
-.I timeout_flags
-may contain
-.B IORING_TIMEOUT_ABS
-for an absolute timeout value, or 0 for a relative timeout.
-.I off
-may contain a completion event count. A timeout
-will trigger a wakeup event on the completion ring for anyone waiting for
-events. A timeout condition is met when either the specified timeout expires,
-or the specified number of events have completed. Either condition will
-trigger the event. If set to 0, completed events are not counted, which
-effectively acts like a timer. io_uring timeouts use the
-.B CLOCK_MONOTONIC
-as the default clock source. The request will complete with
-.B -ETIME
-if the timeout got completed through expiration of the timer, or
-.I 0
-if the timeout got completed through requests completing on their own. If
-the timeout was canceled before it expired, the request will complete with
-.B -ECANCELED.
-Available since 5.4.
-
-Since 5.15, this command also supports the following modifiers in
-.I timeout_flags:
-
-.PP
-.in +12
-.B IORING_TIMEOUT_BOOTTIME
-If set, then the clocksource used is
-.B CLOCK_BOOTTIME
-instead of
-.BR CLOCK_MONOTONIC .
-This clocksource differs in that it includes time elapsed if the system was
-suspend while having a timeout request in-flight.
-
-.B IORING_TIMEOUT_REALTIME
-If set, then the clocksource used is
-.B CLOCK_REALTIME
-instead of
-.BR CLOCK_MONOTONIC .
-.EE
-.in
-.PP
-
-.PP
-.in +7
-Since 5.16,
-.B IORING_TIMEOUT_ETIME_SUCCESS
-can be set in
-.IR timeout_flags ,
-which will result in the expiration of the timer and subsequent completion
-with
-.B -ETIME
-not being interpreted as an error. This is mostly relevant for linked SQEs, as
-subsequent requests in the chain would not get canceled by the timeout, if
-this flag is set. See
-.B IOSQE_IO_LINK
-for more details on linked SQEs.
-.in
-.PP
-
-.PP
-.in +7
-Since 6.4,
-.B IORING_TIMEOUT_MULTISHOT
-can be set in
-.IR timeout_flags ,
-which will result in the timer producing multiple consecutive completions
-like other multi shot operations e.g.
-.B IORING_OP_READ_MULTISHOT
-or
-.BR IORING_POLL_ADD_MULTI .
-.I off
-must be set to the amount of desired completions.
-.B IORING_TIMEOUT_MULTISHOT
-must not be used with
-.BR IORING_TIMEOUT_ABS .
-.in
-.PP
-
-.TP
-.B IORING_OP_TIMEOUT_REMOVE
-If
-.I timeout_flags
-are zero, then it attempts to remove an existing timeout operation.
-.I addr
-must contain the
-.I user_data
-field of the previously issued timeout operation. If the specified timeout
-request is found and canceled successfully, this request will terminate
-with a result value of
-.I 0
-If the timeout request was found but expiration was already in progress,
-this request will terminate with a result value of
-.B -EBUSY
-If the timeout request wasn't found, the request will terminate with a result
-value of
-.B -ENOENT
-Available since 5.5.
-
-If
-.I timeout_flags
-contain
-.BR IORING_TIMEOUT_UPDATE ,
-instead of removing an existing operation, it updates it.
-.I addr
-and return values are same as before.
-.I addr2
-field must contain a pointer to a struct __kernel_timespec structure.
-.I timeout_flags
-may also contain IORING_TIMEOUT_ABS, in which case the value given is an
-absolute one, not a relative one.
-Available since 5.11.
-
-.TP
-.B IORING_OP_ACCEPT
-Issue the equivalent of an
-.BR accept4 (2)
-system call.
-.I fd
-must be set to the socket file descriptor,
-.I addr
-must contain the pointer to the sockaddr structure, and
-.I addr2
-must contain a pointer to the socklen_t addrlen field. Flags can be passed using
-the
-.I accept_flags
-field. See also
-.BR accept4 (2)
-for the general description of the related system call. Available since 5.5.
-
-If the
-.I file_index
-field is set to a positive number, the file won't be installed into the
-normal file table as usual but will be placed into the fixed file table at index
-.I file_index
-- 1.
-In this case, instead of returning a file descriptor, the result will contain
-either 0 on success or an error. If the index points to a valid empty slot, the
-installation is guaranteed to not fail. If there is already a file in the slot,
-it will be replaced, similar to
-.B IORING_OP_FILES_UPDATE.
-Please note that only io_uring has access to such files and no other syscall
-can use them. See
-.B IOSQE_FIXED_FILE
-and
-.BR IORING_REGISTER_FILES .
-
-Available since 5.5.
-
-.TP
-.B IORING_OP_ASYNC_CANCEL
-Attempt to cancel an already issued request.
-.I addr
-must contain the
-.I user_data
-field of the request that should be canceled. The cancelation request will
-complete with one of the following results codes. If found, the
-.I res
-field of the cqe will contain 0. If not found,
-.I res
-will contain
-.BR -ENOENT .
-If found and attempted canceled, the
-.I res
-field will contain
-.BR -EALREADY .
-In this case, the request may or may not
-terminate. In general, requests that are interruptible (like socket IO) will
-get canceled, while disk IO requests cannot be canceled if already started.
-Available since 5.5.
-
-.TP
-.B IORING_OP_LINK_TIMEOUT
-This request must be linked with another request through
-.B IOSQE_IO_LINK
-which is described below. Unlike
-.BR IORING_OP_TIMEOUT ,
-.B IORING_OP_LINK_TIMEOUT
-acts on the linked request, not the completion queue. The format of the command
-is otherwise like
-.BR IORING_OP_TIMEOUT ,
-except there's no completion event count as it's tied to a specific request.
-If used, the timeout specified in the command will cancel the linked command,
-unless the linked command completes before the timeout. The timeout will
-complete with
-.B -ETIME
-if the timer expired and the linked request was attempted canceled, or
-.B -ECANCELED
-if the timer got canceled because of completion of the linked request. Like
-.B IORING_OP_TIMEOUT
-the clock source used is
-.B CLOCK_MONOTONIC
-Available since 5.5.
-
-
-.TP
-.B IORING_OP_CONNECT
-Issue the equivalent of a
-.BR connect (2)
-system call.
-.I fd
-must be set to the socket file descriptor,
-.I addr
-must contain the const pointer to the sockaddr structure, and
-.I off
-must contain the socklen_t addrlen field. See also
-.BR connect (2)
-for the general description of the related system call. Available since 5.5.
-
-.TP
-.B IORING_OP_FALLOCATE
-Issue the equivalent of a
-.BR fallocate (2)
-system call.
-.I fd
-must be set to the file descriptor,
-.I len
-must contain the mode associated with the operation,
-.I off
-must contain the offset on which to operate, and
-.I addr
-must contain the length. See also
-.BR fallocate (2)
-for the general description of the related system call. Available since 5.6.
-
-.TP
-.B IORING_OP_FADVISE
-Issue the equivalent of a
-.BR posix_fadvise (2)
-system call.
-.I fd
-must be set to the file descriptor,
-.I off
-must contain the offset on which to operate,
-.I len
-must contain the length, and
-.I fadvise_advice
-must contain the advice associated with the operation. See also
-.BR posix_fadvise (2)
-for the general description of the related system call. Available since 5.6.
-
-.TP
-.B IORING_OP_MADVISE
-Issue the equivalent of a
-.BR madvise (2)
-system call.
-.I addr
-must contain the address to operate on,
-.I len
-must contain the length on which to operate,
-and
-.I fadvise_advice
-must contain the advice associated with the operation. See also
-.BR madvise (2)
-for the general description of the related system call. Available since 5.6.
-
-.TP
-.B IORING_OP_OPENAT
-Issue the equivalent of a
-.BR openat (2)
-system call.
-.I fd
-is the
-.I dirfd
-argument,
-.I addr
-must contain a pointer to the
-.I *pathname
-argument,
-.I open_flags
-should contain any flags passed in, and
-.I len
-is access mode of the file. See also
-.BR openat (2)
-for the general description of the related system call. Available since 5.6.
-
-If the
-.I file_index
-field is set to a positive number, the file won't be installed into the
-normal file table as usual but will be placed into the fixed file table at index
-.I file_index - 1.
-In this case, instead of returning a file descriptor, the result will contain
-either 0 on success or an error. If the index points to a valid empty slot, the
-installation is guaranteed to not fail. If there is already a file in the slot,
-it will be replaced, similar to
-.B IORING_OP_FILES_UPDATE.
-Please note that only io_uring has access to such files and no other syscall
-can use them. See
-.B IOSQE_FIXED_FILE
-and
-.BR IORING_REGISTER_FILES .
-
-Available since 5.15.
-
-.TP
-.B IORING_OP_OPENAT2
-Issue the equivalent of a
-.BR openat2 (2)
-system call.
-.I fd
-is the
-.I dirfd
-argument,
-.I addr
-must contain a pointer to the
-.I *pathname
-argument,
-.I len
-should contain the size of the open_how structure, and
-.I off
-should be set to the address of the open_how structure. See also
-.BR openat2 (2)
-for the general description of the related system call. Available since 5.6.
-
-If the
-.I file_index
-field is set to a positive number, the file won't be installed into the
-normal file table as usual but will be placed into the fixed file table at index
-.I file_index - 1.
-In this case, instead of returning a file descriptor, the result will contain
-either 0 on success or an error. If the index points to a valid empty slot, the
-installation is guaranteed to not fail. If there is already a file in the slot,
-it will be replaced, similar to
-.BR IORING_OP_FILES_UPDATE .
-Please note that only io_uring has access to such files and no other syscall
-can use them. See
-.B IOSQE_FIXED_FILE
-and
-.BR IORING_REGISTER_FILES .
-
-Available since 5.15.
-
-.TP
-.B IORING_OP_CLOSE
-Issue the equivalent of a
-.BR close (2)
-system call.
-.I fd
-is the file descriptor to be closed. See also
-.BR close (2)
-for the general description of the related system call. Available since 5.6.
-If the
-.I file_index
-field is set to a positive number, this command can be used to close files
-that were direct opened through
-.BR IORING_OP_OPENAT ,
-.BR IORING_OP_OPENAT2 ,
-or
-.B IORING_OP_ACCEPT
-using the io_uring specific direct descriptors. Note that only one of the
-descriptor fields may be set. The direct close feature is available since
-the 5.15 kernel, where direct descriptors were introduced.
-
-.TP
-.B IORING_OP_STATX
-Issue the equivalent of a
-.BR statx (2)
-system call.
-.I fd
-is the
-.I dirfd
-argument,
-.I addr
-must contain a pointer to the
-.I *pathname
-string,
-.I statx_flags
-is the
-.I flags
-argument,
-.I len
-should be the
-.I mask
-argument, and
-.I off
-must contain a pointer to the
-.I statxbuf
-to be filled in. See also
-.BR statx (2)
-for the general description of the related system call. Available since 5.6.
-
-.TP
-.B IORING_OP_READ
-.TP
-.B IORING_OP_WRITE
-Issue the equivalent of a
-.BR pread (2)
-or
-.BR pwrite (2)
-system call.
-.I fd
-is the file descriptor to be operated on,
-.I addr
-contains the buffer in question,
-.I len
-contains the length of the IO operation, and
-.I offs
-contains the read or write offset. If
-.I fd
-does not refer to a seekable file,
-.I off
-must be set to zero or -1. If
-.I offs
-is set to
-.B -1
-, the offset will use (and advance) the file position, like the
-.BR read (2)
-and
-.BR write (2)
-system calls. These are non-vectored versions of the
-.B IORING_OP_READV
-and
-.B IORING_OP_WRITEV
-opcodes. See also
-.BR read (2)
-and
-.BR write (2)
-for the general description of the related system call. Available since 5.6.
-
-.TP
-.B IORING_OP_SPLICE
-Issue the equivalent of a
-.BR splice (2)
-system call.
-.I splice_fd_in
-is the file descriptor to read from,
-.I splice_off_in
-is an offset to read from,
-.I fd
-is the file descriptor to write to,
-.I off
-is an offset from which to start writing to. A sentinel value of
-.B -1
-is used to pass the equivalent of a NULL for the offsets to
-.BR splice (2).
-.I len
-contains the number of bytes to copy.
-.I splice_flags
-contains a bit mask for the flag field associated with the system call.
-Please note that one of the file descriptors must refer to a pipe.
-See also
-.BR splice (2)
-for the general description of the related system call. Available since 5.7.
-
-.TP
-.B IORING_OP_TEE
-Issue the equivalent of a
-.BR tee (2)
-system call.
-.I splice_fd_in
-is the file descriptor to read from,
-.I fd
-is the file descriptor to write to,
-.I len
-contains the number of bytes to copy, and
-.I splice_flags
-contains a bit mask for the flag field associated with the system call.
-Please note that both of the file descriptors must refer to a pipe.
-See also
-.BR tee (2)
-for the general description of the related system call. Available since 5.8.
-
-.TP
-.B IORING_OP_FILES_UPDATE
-This command is an alternative to using
-.B IORING_REGISTER_FILES_UPDATE
-which then works in an async fashion, like the rest of the io_uring commands.
-The arguments passed in are the same.
-.I addr
-must contain a pointer to the array of file descriptors,
-.I len
-must contain the length of the array, and
-.I off
-must contain the offset at which to operate. Note that the array of file
-descriptors pointed to in
-.I addr
-must remain valid until this operation has completed. Available since 5.6.
-
-.TP
-.B IORING_OP_PROVIDE_BUFFERS
-This command allows an application to register a group of buffers to be used
-by commands that read/receive data. Using buffers in this manner can eliminate
-the need to separate the poll + read, which provides a convenient point in
-time to allocate a buffer for a given request. It's often infeasible to have
-as many buffers available as pending reads or receive. With this feature, the
-application can have its pool of buffers ready in the kernel, and when the
-file or socket is ready to read/receive data, a buffer can be selected for the
-operation.
-.I fd
-must contain the number of buffers to provide,
-.I addr
-must contain the starting address to add buffers from,
-.I len
-must contain the length of each buffer to add from the range,
-.I buf_group
-must contain the group ID of this range of buffers, and
-.I off
-must contain the starting buffer ID of this range of buffers. With that set,
-the kernel adds buffers starting with the memory address in
-.I addr,
-each with a length of
-.I len.
-Hence the application should provide
-.I len * fd
-worth of memory in
-.I addr.
-Buffers are grouped by the group ID, and each buffer within this group will be
-identical in size according to the above arguments. This allows the application
-to provide different groups of buffers, and this is often used to have
-differently sized buffers available depending on what the expectations are of
-the individual request. When submitting a request that should use a provided
-buffer, the
-.B IOSQE_BUFFER_SELECT
-flag must be set, and
-.I buf_group
-must be set to the desired buffer group ID where the buffer should be selected
-from. Available since 5.7.
-
-.TP
-.B IORING_OP_REMOVE_BUFFERS
-Remove buffers previously registered with
-.BR IORING_OP_PROVIDE_BUFFERS .
-.I fd
-must contain the number of buffers to remove, and
-.I buf_group
-must contain the buffer group ID from which to remove the buffers. Available
-since 5.7.
-
-.TP
-.B IORING_OP_SHUTDOWN
-Issue the equivalent of a
-.BR shutdown (2)
-system call.
-.I fd
-is the file descriptor to the socket being shutdown, and
-.I len
-must be set to the
-.I how
-argument. No no other fields should be set. Available since 5.11.
-
-.TP
-.B IORING_OP_RENAMEAT
-Issue the equivalent of a
-.BR renameat2 (2)
-system call.
-.I fd
-should be set to the
-.IR olddirfd ,
-.I addr
-should be set to the
-.IR oldpath ,
-.I len
-should be set to the
-.IR newdirfd ,
-.I addr
-should be set to the
-.IR oldpath ,
-.I addr2
-should be set to the
-.IR newpath ,
-and finally
-.I rename_flags
-should be set to the
-.I flags
-passed in to
-.BR renameat2 (2).
-Available since 5.11.
-
-.TP
-.B IORING_OP_UNLINKAT
-Issue the equivalent of a
-.BR unlinkat (2)
-system call.
-.I fd
-should be set to the
-.IR dirfd ,
-.I addr
-should be set to the
-.IR pathname ,
-and
-.I unlink_flags
-should be set to the
-.I flags
-being passed in to
-.BR unlinkat (2).
-Available since 5.11.
-
-.TP
-.B IORING_OP_MKDIRAT
-Issue the equivalent of a
-.BR mkdirat (2)
-system call.
-.I fd
-should be set to the
-.IR dirfd ,
-.I addr
-should be set to the
-.IR pathname ,
-and
-.I len
-should be set to the
-.I mode
-being passed in to
-.BR mkdirat (2).
-Available since 5.15.
-
-.TP
-.B IORING_OP_SYMLINKAT
-Issue the equivalent of a
-.BR symlinkat (2)
-system call.
-.I fd
-should be set to the
-.IR newdirfd ,
-.I addr
-should be set to the
-.I target
-and
-.I addr2
-should be set to the
-.I linkpath
-being passed in to
-.BR symlinkat (2).
-Available since 5.15.
-
-.TP
-.B IORING_OP_LINKAT
-Issue the equivalent of a
-.BR linkat (2)
-system call.
-.I fd
-should be set to the
-.IR olddirfd ,
-.I addr
-should be set to the
-.IR oldpath ,
-.I len
-should be set to the
-.IR newdirfd ,
-.I addr2
-should be set to the
-.IR newpath ,
-and
-.I hardlink_flags
-should be set to the
-.I flags
-being passed in to
-.BR linkat (2).
-Available since 5.15.
-
-.TP
-.B IORING_OP_MSG_RING
-Send a message to an io_uring.
-.I fd
-must be set to a file descriptor of a ring that the application has access to,
-.I len
-can be set to any 32-bit value that the application wishes to pass on, and
-.I off
-should be set any 64-bit value that the application wishes to send. On the
-target ring, a CQE will be posted with the
-.I res
-field matching the
-.I len
-set, and a
-.I user_data
-field matching the
-.I off
-value being passed in. This request type can be used to either just wake or
-interrupt anyone waiting for completions on the target ring, or it can be used
-to pass messages via the two fields. Available since 5.18.
-
-.TP
-.B IORING_OP_SOCKET
-Issue the equivalent of a
-.BR socket (2)
-system call.
-.I fd
-must contain the communication domain,
-.I off
-must contain the communication type,
-.I len
-must contain the protocol, and
-.I rw_flags
-is currently unused and must be set to zero. See also
-.BR socket (2)
-for the general description of the related system call. Available since 5.19.
-
-If the
-.I file_index
-field is set to a positive number, the file won't be installed into the
-normal file table as usual but will be placed into the fixed file table at index
-.I file_index
-- 1.
-In this case, instead of returning a file descriptor, the result will contain
-either 0 on success or an error. If the index points to a valid empty slot, the
-installation is guaranteed to not fail. If there is already a file in the slot,
-it will be replaced, similar to
-.BR IORING_OP_FILES_UPDATE .
-Please note that only io_uring has access to such files and no other syscall
-can use them. See
-.B IOSQE_FIXED_FILE
-and
-.BR IORING_REGISTER_FILES .
-
-Available since 5.19.
-
-.TP
-.B IORING_OP_URING_CMD
-Issues an asynchronous, per-file private operation, similar to
-.BR ioctl (2).
-Further information may be found in the dedicated man page of
-.BR IORING_OP_URING_CMD .
-
-Available since 5.19.
-
-.TP
-.B IORING_OP_SEND_ZC
-Issue the zerocopy equivalent of a
-.BR send(2)
-system call. Similar to
-.BR IORING_OP_SEND ,
-but tries to avoid making intermediate
-copies of data. Zerocopy execution is not guaranteed and may fall back to
-copying. The request may also fail with
-.BR -EOPNOTSUPP ,
-when a protocol doesn't support zerocopy, in which case users are recommended
-to use copying sends instead.
-
-The
-.I flags
-field of the first
-.I "struct io_uring_cqe"
-may likely contain
-.BR IORING_CQE_F_MORE ,
-which means that there will be a second completion event / notification for
-the request, with the
-.I user_data
-field set to the same value. The user must not modify the data buffer until the
-notification is posted. The first cqe follows the usual rules and so its
-.I res
-field will contain the number of bytes sent or a negative error code. The
-notification's
-.I res
-field will be set to zero and the
-.I flags
-field will contain
-.BR IORING_CQE_F_NOTIF .
-The two step model is needed because the kernel may hold on to buffers for a
-long time, e.g. waiting for a TCP ACK, and having a separate cqe for request
-completions allows userspace to push more data without extra delays. Note,
-notifications are only responsible for controlling the lifetime of the buffers,
-and as such don't mean anything about whether the data has atually been sent
-out or received by the other end. Even errored requests may generate a
-notification, and the user must check for
-.B IORING_CQE_F_MORE
-rather than relying on the result.
-
-.I fd
-must be set to the socket file descriptor,
-.I addr
-must contain a pointer to the buffer,
-.I len
-denotes the length of the buffer to send, and
-.I msg_flags
-holds the flags associated with the system call. When
-.I addr2
-is non-zero it points to the address of the target with
-.I addr_len
-specifying its size, turning the request into a
-.BR sendto (2)
-system call equivalent.
-
-Available since 6.0.
-
-This command also supports the following modifiers in
-.I ioprio:
-
-.PP
-.in +12
-.B IORING_RECVSEND_POLL_FIRST
-If set, io_uring will assume the socket is currently full and attempting to
-send data will be unsuccessful. For this case, io_uring will arm internal
-poll and trigger a send of the data when there is enough space available.
-This initial send attempt can be wasteful for the case where the socket
-is expected to be full, setting this flag will bypass the initial send
-attempt and go straight to arming poll. If poll does indicate that data can
-be sent, the operation will proceed.
-
-.B IORING_RECVSEND_FIXED_BUF
-If set, instructs io_uring to use a pre-mapped buffer. The
-.I buf_index
-field should contain an index into an array of fixed buffers. See
-.BR io_uring_register (2)
-for details on how to setup a context for fixed buffer I/O.
-.EE
-.in
-.PP
-
-.TP
-.B IORING_OP_SENDMSG_ZC
-Issue the zerocopy equivalent of a
-.BR sendmsg (2)
-system call.
-Works just like
-.BR IORING_OP_SENDMSG ,
-but like
-.B IORING_OP_SEND_ZC
-supports
-.BR IORING_RECVSEND_FIXED_BUF .
-For additional notes regarding zero copy see
-.BR IORING_OP_SEND_ZC .
-
-Available since 6.1
-
-.TP
-.B IORING_OP_WAITID
-Issue the equivalent of a
-.BR waitid (2)
-system call.
-.I len
-must contain the idtype being queried/waited for and
-.I fd
-must contain the 'pid' (or id) being waited for.
-.I file_index
-is the 'options' being set (the child state changes to wait for).
-.I addr2
-is a pointer to siginfo_t, if any, being filled in. See also
-.BR waitid (2)
-for the general description of the related system call. Available since 6.5.
-
-.TP
-.B IORING_OP_SETXATTR
-.TP
-.B IORING_OP_GETXATTR
-.TP
-.B IORING_OP_FSETXATTR
-.TP
-.B IORING_OP_FGETXATTR
-Issue the equivalent of a
-.BR setxattr (2)
-or
-.BR getxattr (2)
-or
-.BR fsetxattr (2)
-or
-.BR fgetxattr (2)
-system call.
-.I addr
-must contain a pointer to a buffer containing the name of the extended
-attribute.
-.I addr2
-must contain a pointer to a buffer of maximum length
-.IR len ,
-in which the value of the extended attribute is to be placed or is read from.
-Additional flags maybe provided in
-.IR xattr_flags .
-For
-.BR setxattr (2)
-or
-.BR getxattr (2)
-.I addr3
-must contain a pointer to the path of the file.
-For
-.BR fsetxattr (2)
-or
-.BR fgetxattr (2)
-.I fd
-must contain the file descriptor of the file.
-
-Available since 5.19.
-
-.TP
-.B IORING_OP_BIND
-Issues the equivalent of the
-.BR bind (2)
-system call.
-.I fd
-must contain the file descriptor of the socket,
-.I addr
-must contain a pointer to the sockaddr struct containing the address to assign
-and
-.I addr2
-must contain the length of the address.
-
-Available since 6.11.
-
-.TP
-.B IORING_OP_LISTEN
-Issues the equivalent of the
-.BR listen (2)
-system call.
-.I fd
-must contain the file descriptor of the socket and
-.I addr
-must contain the backlog parameter, i.e. the maximum amount of pending
-queued connections.
-
-Available since 6.11.
-
-.TP
-.B IORING_OP_FTRUNCATE
-Issues the equivalent of the
-.BR ftruncate (2)
-system call.
-.I fd
-must contain the file descriptor of the file to truncate and
-.I off
-must contain the length to which the file will be truncated.
-
-Available since 6.9.
-
-.TP
-.B IORING_OP_READ_MULTISHOT
-Like
-.BR IORING_OP_READ ,
-but similar to requests prepared with
-.IR io_uring_prep_multishot_accept (3)
-additional reads and thus CQEs will be performed based on this single SQE once
-there is more data available.
-Is restricted to pollable files and will fall back to single shot if the file
-does not support
-.BR NOWAIT .
-Like other multishot type requests, the application should look at the CQE
-flags and see if
-.B IORING_CQE_F_MORE
-is set on completion as an indication of whether or not the read request will
-generate further CQEs. Available since 6.7.
-
-.TP
-.B IORING_OP_FUTEX_WAIT
-Issues the equivalent of the
-.BR futex_wait (2)
-system call.
-.I addr
-must hold a pointer to the futex,
-.I addr2
-must hold the value to which the futex has to be changed so this caller to
-.BR futex_wait (2)
-can be woken by a call to
-.BR futex_wake (2),
-.I addr3
-must hold the bitmask of this
-.BR futex_wait (2)
-caller.
-For a caller of
-.BR futex_wake (2)
-to wake a waiter additionally the bitmask of the waiter and waker must have
-at least one set bit in common.
-.I fd
-must contain additional flags passed in.
-
-Available since 6.7.
-
-.TP
-.B IORING_OP_FUTEX_WAKE
-Issues the equivalent of the
-.BR futex_wake (2)
-system call.
-.I addr
-must hold a pointer to the futex,
-.I addr2
-must hold the maximum number of waiters waiting on this futex to wake,
-.I addr3
-must hold the bitmask of this
-.BR futex_wake (2)
-call.
-To wake a waiter additionally the bitmask of the waiter and waker must have
-at least one set bit in common.
-.I fd
-must contain additional flags passed in.
-
-Available since 6.7.
-
-.TP
-.B IORING_OP_FUTEX_WAITV
-Issues the equivalent of the
-.BR futex_waitv (2)
-system call.
-.I addr
-must hold a pointer to the futexv struct,
-.I len
-must hold the length of the futexv struct, which may not be 0 and must be
-smaller than
-.B FUTEX_WAITV_MAX
-(as of 6.11 == 128).
-
-Available since 6.7.
-
-.TP
-.B IORING_OP_FIXED_FD_INSTALL
-This operation is used to insert a registered file into the regular process
-file table.
-Consequently
-.I fd
-must contain the file index and
-.B IOSQE_FIXED_FILE
-must be set.
-The resulting regular fd is returned via cqe->res.
-Additional flags may be passed in via
-.IR install_fd_flags .
-Currently supported flags are:
-.BR IORING_FIXED_FD_NO_CLOEXEC ,
-which overrides a potentially set
-.B O_CLOEXEC
-flag set on the initial file.
-
-Available since 6.8.
-
-.PP
-The
-.I flags
-field is a bit mask. The supported flags are:
-.TP
-.B IOSQE_FIXED_FILE
-When this flag is specified,
-.I fd
-is an index into the files array registered with the io_uring instance (see the
-.B IORING_REGISTER_FILES
-section of the
-.BR io_uring_register (2)
-man page). Note that this isn't always available for all commands. If used on
-a command that doesn't support fixed files, the SQE will error with
-.BR -EBADF .
-Available since 5.1.
-.TP
-.B IOSQE_IO_DRAIN
-When this flag is specified, the SQE will not be started before previously
-submitted SQEs have completed, and new SQEs will not be started before this
-one completes. Available since 5.2.
-.TP
-.B IOSQE_IO_LINK
-When this flag is specified, the SQE forms a link with the next SQE in the
-submission ring. That next SQE will not be started before the previous request
-completes. This, in effect, forms a chain of SQEs, which can be arbitrarily
-long. The tail of the chain is denoted by the first SQE that does not have this
-flag set. Chains are not supported across submission boundaries. Even if the
-last SQE in a submission has this flag set, it will still terminate the current
-chain. This flag has no effect on previous SQE submissions, nor does it impact
-SQEs that are outside of the chain tail. This means that multiple chains can be
-executing in parallel, or chains and individual SQEs. Only members inside the
-chain are serialized. A chain of SQEs will be broken if any request in that
-chain ends in error. io_uring considers any unexpected result an error. This
-means that, eg, a short read will also terminate the remainder of the chain.
-If a chain of SQE links is broken, the remaining unstarted part of the chain
-will be terminated and completed with
-.B -ECANCELED
-as the error code. Available since 5.3.
-.TP
-.B IOSQE_IO_HARDLINK
-Like IOSQE_IO_LINK, but it doesn't sever regardless of the completion result.
-Note that the link will still sever if we fail submitting the parent request,
-hard links are only resilient in the presence of completion results for
-requests that did submit correctly.
-.B IOSQE_IO_HARDLINK
-implies
-.BR IOSQE_IO_LINK .
-Available since 5.5.
-.TP
-.B IOSQE_ASYNC
-Normal operation for io_uring is to try and issue an sqe as non-blocking first,
-and if that fails, execute it in an async manner. To support more efficient
-overlapped operation of requests that the application knows/assumes will
-always (or most of the time) block, the application can ask for an sqe to be
-issued async from the start. Available since 5.6.
-.TP
-.B IOSQE_BUFFER_SELECT
-Used in conjunction with the
-.B IORING_OP_PROVIDE_BUFFERS
-command, which registers a pool of buffers to be used by commands that read
-or receive data. When buffers are registered for this use case, and this
-flag is set in the command, io_uring will grab a buffer from this pool when
-the request is ready to receive or read data. If successful, the resulting CQE
-will have
-.B IORING_CQE_F_BUFFER
-set in the flags part of the struct, and the upper
-.B IORING_CQE_BUFFER_SHIFT
-bits will contain the ID of the selected buffers. This allows the application
-to know exactly which buffer was selected for the operation. If no buffers
-are available and this flag is set, then the request will fail with
-.B -ENOBUFS
-as the error code. Once a buffer has been used, it is no longer available in
-the kernel pool. The application must re-register the given buffer again when
-it is ready to recycle it (eg has completed using it). Available since 5.7.
-.TP
-.B IOSQE_CQE_SKIP_SUCCESS
-Don't generate a CQE if the request completes successfully. If the request
-fails, an appropriate CQE will be posted as usual and if there is no
-.B IOSQE_IO_HARDLINK,
-CQEs for all linked requests will be omitted. The notion of failure/success is
-opcode specific and is the same as with breaking chains of
-.BR IOSQE_IO_LINK .
-One special case is when the request has a linked timeout, then the CQE
-generation for the linked timeout is decided solely by whether it has
-.B IOSQE_CQE_SKIP_SUCCESS
-set, regardless whether it timed out or was canceled. In other words, if a
-linked timeout has the flag set, it's guaranteed to not post a CQE.
-
-The semantics are chosen to accommodate several use cases. First, when all but
-the last request of a normal link without linked timeouts are marked with the
-flag, only one CQE per link is posted. Additionally, it enables suppression of
-CQEs in cases where the side effects of a successfully executed operation is
-enough for userspace to know the state of the system. One such example would
-be writing to a synchronisation file.
-
-This flag is incompatible with
-.BR IOSQE_IO_DRAIN .
-Using both of them in a single ring is undefined behavior, even when they are
-not used together in a single request. Currently, after the first request with
-.BR IOSQE_CQE_SKIP_SUCCESS ,
-all subsequent requests marked with drain will be failed at submission time.
-Note that the error reporting is best effort only, and restrictions may change
-in the future.
-
-Available since 5.17.
-
-.PP
-.I ioprio
-specifies the I/O priority. See
-.BR ioprio_get (2)
-for a description of Linux I/O priorities.
-
-.I fd
-specifies the file descriptor against which the operation will be
-performed, with the exception noted above.
-
-If the operation is one of
-.B IORING_OP_READ_FIXED
-or
-.BR IORING_OP_WRITE_FIXED ,
-.I addr
-and
-.I len
-must fall within the buffer located at
-.I buf_index
-in the fixed buffer array. If the operation is either
-.B IORING_OP_READV
-or
-.BR IORING_OP_WRITEV ,
-then
-.I addr
-points to an iovec array of
-.I len
-entries.
-
-.IR rw_flags ,
-specified for read and write operations, contains a bitwise OR of
-per-I/O flags, as described in the
-.BR preadv2 (2)
-man page.
-
-The
-.I fsync_flags
-bit mask may contain either 0, for a normal file integrity sync, or
-.B IORING_FSYNC_DATASYNC
-to provide data sync only semantics. See the descriptions of
-.B O_SYNC
-and
-.B O_DSYNC
-in the
-.BR open (2)
-manual page for more information.
-
-The bits that may be set in
-.I poll_events
-are defined in \fI<poll.h>\fP, and documented in
-.BR poll (2).
-
-.I user_data
-is an application-supplied value that will be copied into
-the completion queue entry (see below).
-.I buf_index
-is an index into an array of fixed buffers, and is only valid if fixed
-buffers were registered.
-.I personality
-is the credentials id to use for this operation. See
-.BR io_uring_register (2)
-for how to register personalities with io_uring. If set to 0, the current
-personality of the submitting task is used.
-.PP
-Once the submission queue entry is initialized, I/O is submitted by
-placing the index of the submission queue entry into the tail of the
-submission queue. After one or more indexes are added to the queue,
-and the queue tail is advanced, the
-.BR io_uring_enter (2)
-system call can be invoked to initiate the I/O.
-
-Completions use the following data structure:
-.PP
-.in +4n
-.EX
-/*
- * IO completion data structure (Completion Queue Entry)
- */
-struct io_uring_cqe {
- __u64 user_data; /* sqe->data submission passed back */
- __s32 res; /* result code for this event */
- __u32 flags;
-};
-.EE
-.in
-.PP
-.I user_data
-is copied from the field of the same name in the submission queue
-entry. The primary use case is to store data that the application
-will need to access upon completion of this particular I/O. The
-.I flags
-is used for certain commands, like
-.B IORING_OP_POLL_ADD
-or in conjunction with
-.B IOSQE_BUFFER_SELECT
-or
-.BR IORING_OP_MSG_RING ,
-see those entries for details.
-.I res
-is the operation-specific result, but io_uring-specific errors
-(e.g. flags or opcode invalid) are returned through this field.
-They are described in section
-.B CQE
-.BR ERRORS .
-.PP
-For read and write opcodes, the
-return values match
-.I errno
-values documented in the
-.BR preadv2 (2)
-and
-.BR pwritev2 (2)
-man pages, with
-.I
-res
-holding the equivalent of
-.I -errno
-for error cases, or the transferred number of bytes in case the operation
-is successful. Hence both error and success return can be found in that
-field in the CQE. For other request types, the return values are documented
-in the matching man page for that type, or in the opcodes section above for
-io_uring-specific opcodes.
-.PP
-.SH RETURN VALUE
-.BR io_uring_enter (2)
-returns the number of I/Os successfully consumed. This can be zero
-if
-.I to_submit
-was zero or if the submission queue was empty. Note that if the ring was
-created with
-.B IORING_SETUP_SQPOLL
-specified, then the return value will generally be the same as
-.I to_submit
-as submission happens outside the context of the system call.
-
-The errors related to a submission queue entry will be returned through a
-completion queue entry (see section
-.B CQE
-.BR ERRORS ),
-rather than through the system call itself.
-
-Errors that occur not on behalf of a submission queue entry are returned via the
-system call directly. On such an error, a negative error code is returned. The
-caller should not rely on
-.I errno
-variable.
-.PP
-.SH ERRORS
-These are the errors returned by
-.BR io_uring_enter (2)
-system call.
-.TP
-.B EAGAIN
-The kernel was unable to allocate memory for the request, or otherwise ran out
-of resources to handle it. The application should wait for some completions and
-try again.
-.TP
-.B EBADF
-.I fd
-is not a valid file descriptor.
-.TP
-.B EBADFD
-.I fd
-is a valid file descriptor, but the io_uring ring is not in the right state
-(enabled). See
-.BR io_uring_register (2)
-for details on how to enable the ring.
-.TP
-.B EBADR
-At least one CQE was dropped even with the
-.B IORING_FEAT_NODROP
-feature, and there are no otherwise available CQEs. This clears the error state
-and so with no other changes the next call to
-.BR io_uring_enter (2)
-will not have this error. This error should be extremely rare and indicates the
-machine is running critically low on memory. It may be reasonable for the
-application to terminate running unless it is able to safely handle any CQE
-being lost.
-.TP
-.B EBUSY
-If the
-.B IORING_FEAT_NODROP
-feature flag is set, then
-.B EBUSY
-will be returned if there were overflow entries,
-.B IORING_ENTER_GETEVENTS
-flag is set and not all of the overflow entries were able to be flushed to
-the CQ ring.
-
-Without
-.B IORING_FEAT_NODROP
-the application is attempting to overcommit the number of requests it can have
-pending. The application should wait for some completions and try again. May
-occur if the application tries to queue more requests than we have room for in
-the CQ ring, or if the application attempts to wait for more events without
-having reaped the ones already present in the CQ ring.
-.TP
-.B EEXIST
-The thread submitting the work is invalid. This may occur if
-.B IORING_ENTER_GETEVENTS
-and
-.B IORING_SETUP_DEFER_TASKRUN
-is set, but the submitting thread is not the thread that initially created or
-enabled the io_uring associated with
-.I fd.
-.TP
-.B EINVAL
-Some bits in the
-.I flags
-argument are invalid.
-.TP
-.B EFAULT
-An invalid user space address was specified for the
-.I sig
-argument.
-.TP
-.B ENXIO
-The io_uring instance is in the process of being torn down.
-.TP
-.B EOPNOTSUPP
-.I fd
-does not refer to an io_uring instance.
-.TP
-.B EINTR
-The operation was interrupted by a delivery of a signal before it could
-complete; see
-.BR signal (7).
-Can happen while waiting for events with
-.B IORING_ENTER_GETEVENTS.
-.TP
-.B EOWNERDEAD
-The ring has been setup with
-.B IORING_SETUP_SQPOLL
-and the sq poll kernel thread has been killed.
-
-.SH CQE ERRORS
-These io_uring-specific errors are returned as a negative value in the
-.I res
-field of the completion queue entry.
-.TP
-.B EACCES
-The
-.I flags
-field or
-.I opcode
-in a submission queue entry is not allowed due to registered restrictions.
-See
-.BR io_uring_register (2)
-for details on how restrictions work.
-.TP
-.B EBADF
-The
-.I fd
-field in the submission queue entry is invalid, or the
-.B IOSQE_FIXED_FILE
-flag was set in the submission queue entry, but no files were registered
-with the io_uring instance.
-.TP
-.B EFAULT
-buffer is outside of the process' accessible address space
-.TP
-.B EFAULT
-.B IORING_OP_READ_FIXED
-or
-.B IORING_OP_WRITE_FIXED
-was specified in the
-.I opcode
-field of the submission queue entry, but either buffers were not
-registered for this io_uring instance, or the address range described
-by
-.I addr
-and
-.I len
-does not fit within the buffer registered at
-.IR buf_index .
-.TP
-.B EINVAL
-The
-.I flags
-field or
-.I opcode
-in a submission queue entry is invalid.
-.TP
-.B EINVAL
-The
-.I buf_index
-member of the submission queue entry is invalid.
-.TP
-.B EINVAL
-The
-.I personality
-field in a submission queue entry is invalid.
-.TP
-.B EINVAL
-.B IORING_OP_NOP
-was specified in the submission queue entry, but the io_uring context
-was setup for polling
-.RB ( IORING_SETUP_IOPOLL
-was specified in the call to io_uring_setup).
-.TP
-.B EINVAL
-.B IORING_OP_READV
-or
-.B IORING_OP_WRITEV
-was specified in the submission queue entry, but the io_uring instance
-has fixed buffers registered.
-.TP
-.B EINVAL
-.B IORING_OP_READ_FIXED
-or
-.B IORING_OP_WRITE_FIXED
-was specified in the submission queue entry, and the
-.I buf_index
-is invalid.
-.TP
-.B EINVAL
-.BR IORING_OP_READV ,
-.BR IORING_OP_WRITEV ,
-.BR IORING_OP_READ_FIXED ,
-.B IORING_OP_WRITE_FIXED
-or
-.B IORING_OP_FSYNC
-was specified in the submission queue entry, but the io_uring instance
-was configured for IOPOLLing, or any of
-.IR addr ,
-.IR ioprio ,
-.IR off ,
-.IR len ,
-or
-.I buf_index
-was set in the submission queue entry.
-.TP
-.B EINVAL
-.B IORING_OP_POLL_ADD
-or
-.B IORING_OP_POLL_REMOVE
-was specified in the
-.I opcode
-field of the submission queue entry, but the io_uring instance was
-configured for busy-wait polling
-.RB ( IORING_SETUP_IOPOLL ),
-or any of
-.IR ioprio ,
-.IR off ,
-.IR len ,
-or
-.I buf_index
-was non-zero in the submission queue entry.
-.TP
-.B EINVAL
-.B IORING_OP_POLL_ADD
-was specified in the
-.I opcode
-field of the submission queue entry, and the
-.I addr
-field was non-zero.
-.TP
-.B EOPNOTSUPP
-.I opcode
-is valid, but not supported by this kernel.
-.TP
-.B EOPNOTSUPP
-.B IOSQE_BUFFER_SELECT
-was set in the
-.I flags
-field of the submission queue entry, but the
-.I opcode
-doesn't support buffer selection.
-.TP
-.B EINVAL
-.B IORING_OP_TIMEOUT
-was specified, but
-.I timeout_flags
-specified more than one clock source or
-.B IORING_TIMEOUT_MULTISHOT
-was set alongside
-.BR IORING_TIMEOUT_ABS .
diff --git a/src/liburing/man/io_uring_enter2.2 b/src/liburing/man/io_uring_enter2.2
deleted file mode 120000
index 5566c093b8ee..000000000000
--- a/src/liburing/man/io_uring_enter2.2
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_enter.2
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_for_each_cqe.3 b/src/liburing/man/io_uring_for_each_cqe.3
deleted file mode 100644
index 78d8f6fc168d..000000000000
--- a/src/liburing/man/io_uring_for_each_cqe.3
+++ /dev/null
@@ -1,63 +0,0 @@
-.\" Copyright (C) 2023 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_for_each_cqe 3 "June 04, 2023" "liburing-2.4" "liburing Manual"
-.SH NAME
-io_uring_for_each_cqe \- iterate pending completion events
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "io_uring_for_each_cqe(struct io_uring *" ring ","
-.BI " unsigned " head ","
-.BI " struct io_uring_cqe *" cqe ") { }
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_for_each_cqe (3)
-is a macro helper that iterates completion events belonging to the
-.I ring
-using
-.I head
-as a temporary iterator, and points
-.I cqe
-to each pending event when iterating.
-
-This helper provides an efficient way to iterate all pending events in
-the ring, and then advancing the CQ ring by calling
-.BR io_uring_cq_advance (3)
-with the number of CQEs consumed when done. As updating the kernel visible
-CQ ring state involves an ordered write, doing it once for a number of
-events is more efficient than handling each completion separately and
-calling
-.BR io_uring_cqe_seen (3)
-for each of them.
-
-.SH EXAMPLE
-.EX
-void handle_cqes(struct io_uring *ring)
-{
- struct io_uring_cqe *cqe;
- unsigned head;
- unsigned i = 0;
-
- io_uring_for_each_cqe(ring, head, cqe) {
- /* handle completion */
- printf("cqe: %d\\n", cqe->res);
- i++;
- }
-
- io_uring_cq_advance(ring, i);
-}
-.EE
-
-.SH RETURN VALUE
-None
-.SH SEE ALSO
-.BR io_uring_wait_cqe_timeout (3),
-.BR io_uring_wait_cqe (3),
-.BR io_uring_wait_cqes (3),
-.BR io_uring_cqe_seen (3),
-.BR io_uring_buf_ring_cq_advance (3)
diff --git a/src/liburing/man/io_uring_free_buf_ring.3 b/src/liburing/man/io_uring_free_buf_ring.3
deleted file mode 100644
index 649cabb3d16c..000000000000
--- a/src/liburing/man/io_uring_free_buf_ring.3
+++ /dev/null
@@ -1,53 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_free_buf_ring 3 "Mar 07, 2023" "liburing-2.4" "liburing Manual"
-.SH NAME
-io_uring_free_buf_ring \- register and free a buffer ring for provided buffers
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_free_buf_ring(struct io_uring *" ring ",
-.BI " struct io_uring_buf_ring *" br ",
-.BI " unsigned int " nentries ",
-.BI " int " bgid ");"
-.BI "
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_free_buf_ring (3)
-function unregisters a previously registered shared buffer ring. The ring must
-have heen previously returned from
-.BR io_uring_setup_buf_ring (3) .
-
-The
-.I ring
-argument must pointer to the ring for which the provided buffer ring is being
-registered,
-.I br
-must point to a buffer ring previously returned by
-.BR io_uring_setup_buf_ring (3) ,
-.I nentries
-is the number of entries requested in the buffer ring, and
-.I bgid
-is the buffer group ID that
-.I br
-was setup with.
-
-Under the covers, this function uses
-.BR io_uring_unregister_buf_ring (3)
-to unregister the ring, and handles the freeing of the ring rather than
-letting the application open code it.
-
-Available since 5.19.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_free_buf_ring (3)
-returns zero. On failure it returns
-.BR -errno .
-.SH SEE ALSO
-.BR io_uring_setup_buf_ring (3)
diff --git a/src/liburing/man/io_uring_free_probe.3 b/src/liburing/man/io_uring_free_probe.3
deleted file mode 100644
index 960fda39ad6c..000000000000
--- a/src/liburing/man/io_uring_free_probe.3
+++ /dev/null
@@ -1,27 +0,0 @@
-.\" Copyright (C) 2022 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_free_probe 3 "January 25, 2022" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_free_probe \- free probe instance
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_free_probe(struct io_uring_probe *" probe ");"
-.fi
-.SH DESCRIPTION
-.PP
-The function
-.BR io_uring_free_probe (3)
-frees the
-.I probe
-instance allocated with the
-.BR io_uring_get_probe (3)
-function.
-
-.SH RETURN VALUE
-None
-.SH SEE ALSO
-.BR io_uring_get_probe (3)
diff --git a/src/liburing/man/io_uring_free_reg_wait.3 b/src/liburing/man/io_uring_free_reg_wait.3
deleted file mode 100644
index 3a6f9d1a8b34..000000000000
--- a/src/liburing/man/io_uring_free_reg_wait.3
+++ /dev/null
@@ -1,35 +0,0 @@
-.\" Copyright (C) 2024 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_free_reg_wait 3 "November 2, 2024" "liburing-2.9" "liburing Manual"
-.SH NAME
-io_uring_free_reg_wait \- Frees a previously registered wait region
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_free_reg_wait(struct io_uring *" ring ","
-.BI " unsigned " nentries ");"
-.PP
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_free_reg_wait (3)
-function frees a wait region for the ring
-.IR ring
-of
-.IR nentries
-previously setup with
-.BR io_uring_setup_reg_wait (3) .
-As registered wait regions persist for the life time of the ring, on the
-kernel side the wait regions still remain active, and may in fact still
-be used by the application for wait operations. They may just no longer
-be modified by the application.
-
-Available since kernel 6.13.
-
-.SH SEE ALSO
-.BR io_uring_submit_and_wait_reg (3),
-.BR io_uring_free_reg_wait (3)
diff --git a/src/liburing/man/io_uring_get_events.3 b/src/liburing/man/io_uring_get_events.3
deleted file mode 100644
index f2415423953c..000000000000
--- a/src/liburing/man/io_uring_get_events.3
+++ /dev/null
@@ -1,33 +0,0 @@
-.\" Copyright (C) 2022 Dylan Yudaken
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_get_events 3 "September 5, 2022" "liburing-2.3" "liburing Manual"
-.SH NAME
-io_uring_get_events \- Flush outstanding requests to CQE ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_get_events(struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_get_events (3)
-function runs outstanding work and flushes completion events to the CQE ring.
-
-There can be events needing to be flushed if the ring was full and had overflowed.
-Alternatively if the ring was setup with the
-.BR IORING_SETUP_DEFER_TASKRUN
-flag then this will process outstanding tasks, possibly resulting in more CQEs.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_get_events (3)
-returns 0. On failure it returns
-.BR -errno .
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit_and_get_events (3),
-.BR io_uring_cq_has_overflow (3)
diff --git a/src/liburing/man/io_uring_get_probe.3 b/src/liburing/man/io_uring_get_probe.3
deleted file mode 100644
index 353cc7314f4a..000000000000
--- a/src/liburing/man/io_uring_get_probe.3
+++ /dev/null
@@ -1,30 +0,0 @@
-.\" Copyright (C) 2022 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_get_probe 3 "January 25, 2022" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_get_probe \- get probe instance
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "io_uring_probe *io_uring_get_probe(void);"
-.fi
-.SH DESCRIPTION
-.PP
-The function
-.BR io_uring_get_probe (3)
-returns an allocated io_uring_probe structure to the caller. The caller is
-responsible for freeing the structure with the function
-.BR io_uring_free_probe (3).
-
-.SH NOTES
-Earlier versions of the Linux kernel do not support probe. If the kernel
-doesn't support probe, this function will return NULL.
-
-.SH RETURN VALUE
-On success it returns an allocated io_uring_probe structure, otherwise
-it returns NULL.
-.SH SEE ALSO
-.BR io_uring_free_probe (3)
diff --git a/src/liburing/man/io_uring_get_sqe.3 b/src/liburing/man/io_uring_get_sqe.3
deleted file mode 100644
index b257ebb39482..000000000000
--- a/src/liburing/man/io_uring_get_sqe.3
+++ /dev/null
@@ -1,57 +0,0 @@
-.\" Copyright (C) 2020 Jens Axboe <axboe@kernel.dk>
-.\" Copyright (C) 2020 Red Hat, Inc.
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_get_sqe 3 "July 10, 2020" "liburing-0.7" "liburing Manual"
-.SH NAME
-io_uring_get_sqe \- get the next available submission queue entry from the
-submission queue
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "struct io_uring_sqe *io_uring_get_sqe(struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_get_sqe (3)
-function gets the next available submission queue entry from the submission
-queue belonging to the
-.I ring
-param.
-
-On success
-.BR io_uring_get_sqe (3)
-returns a pointer to the submission queue entry. On failure NULL is returned.
-
-If a submission queue entry is returned, it should be filled out via one of the
-prep functions such as
-.BR io_uring_prep_read (3)
-and submitted via
-.BR io_uring_submit (3).
-
-Note that neither
-.BR io_uring_get_sqe
-nor the prep functions set (or clear) the
-.B user_data
-field of the SQE. If the caller expects
-.BR io_uring_cqe_get_data (3)
-or
-.BR io_uring_cqe_get_data64 (3)
-to return valid data when reaping IO completions, either
-.BR io_uring_sqe_set_data (3)
-or
-.BR io_uring_sqe_set_data64 (3)
-.B MUST
-have been called before submitting the request.
-
-.SH RETURN VALUE
-.BR io_uring_get_sqe (3)
-returns a pointer to the next submission queue event on success and NULL on
-failure. If NULL is returned, the SQ ring is currently full and entries must
-be submitted for processing before new ones can get allocated.
-.SH SEE ALSO
-.BR io_uring_submit (3),
-.BR io_uring_sqe_set_data (3)
diff --git a/src/liburing/man/io_uring_major_version.3 b/src/liburing/man/io_uring_major_version.3
deleted file mode 120000
index 21bbf456e240..000000000000
--- a/src/liburing/man/io_uring_major_version.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_check_version.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_minor_version.3 b/src/liburing/man/io_uring_minor_version.3
deleted file mode 120000
index 21bbf456e240..000000000000
--- a/src/liburing/man/io_uring_minor_version.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_check_version.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_opcode_supported.3 b/src/liburing/man/io_uring_opcode_supported.3
deleted file mode 100644
index b981ed7d7dc6..000000000000
--- a/src/liburing/man/io_uring_opcode_supported.3
+++ /dev/null
@@ -1,30 +0,0 @@
-.\" Copyright (C) 2022 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_opcode_supported 3 "January 25, 2022" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_opcode_supported \- is op code supported?
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_opcode_supported(struct io_uring_probe *" probe ","
-.BI " int " opcode ");"
-.fi
-.SH DESCRIPTION
-.PP
-The function
-.BR io_uring_opcode_supported (3)
-allows the caller to determine if the passed in
-.I opcode
-belonging to the
-.I probe
-param is supported. An instance of the io_uring_probe instance can be
-obtained by calling the function
-.BR io_uring_get_probe (3).
-
-.SH RETURN VALUE
-On success it returns 1, otherwise it returns 0.
-.SH SEE ALSO
-.BR io_uring_get_probe (3)
diff --git a/src/liburing/man/io_uring_peek_batch_cqe.3 b/src/liburing/man/io_uring_peek_batch_cqe.3
deleted file mode 120000
index fbf4e4cccb91..000000000000
--- a/src/liburing/man/io_uring_peek_batch_cqe.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_peek_cqe.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_peek_cqe.3 b/src/liburing/man/io_uring_peek_cqe.3
deleted file mode 100644
index 4416e15abfe6..000000000000
--- a/src/liburing/man/io_uring_peek_cqe.3
+++ /dev/null
@@ -1,59 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_peek_cqe 3 "March 12, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_peek_cqe \- check if an io_uring completion event is available
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_peek_cqe(struct io_uring *" ring ","
-.BI " struct io_uring_cqe **" cqe_ptr ");"
-.PP
-.BI "unsigned io_uring_peek_batch_cqe(struct io_uring *" ring ","
-.BI " struct io_uring_cqe **" cqe_ptrs ","
-.BI " unsigned " count ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_peek_cqe (3)
-function returns an IO completion from the queue belonging to the
-.I ring
-param, if one is readily available. On successful return,
-.I cqe_ptr
-param is filled with a valid CQE entry.
-
-This function does not enter the kernel to wait for an event, an event
-is only returned if it's already available in the CQ ring.
-
-The
-.BR io_uring_peek_batch_cqe (3)
-function returns up to
-.I count
-request completions in
-.I cqe_ptrs
-belonging to the
-.I ring
-param, if they are readily available. It will not enter the kernel, unless the
-CQ ring is in an overflow condition. Upon successful return,
-.I cqe_ptrs
-are filled with the number of events indicated by the return value.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_peek_cqe (3)
-returns
-.B 0
-and the cqe_ptr parameter is filled in. On success
-.BR io_uring_peek_batch_cqe (3)
-returns the number of completions filled in. On failure,
-.BR io_uring_peek_cqe (3)
-may return
-.BR -EAGAIN .
-.SH SEE ALSO
-.BR io_uring_submit (3),
-.BR io_uring_wait_cqes (3),
-.BR io_uring_wait_cqe (3)
diff --git a/src/liburing/man/io_uring_prep_accept.3 b/src/liburing/man/io_uring_prep_accept.3
deleted file mode 100644
index 950ab7d40b83..000000000000
--- a/src/liburing/man/io_uring_prep_accept.3
+++ /dev/null
@@ -1,203 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_accept 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_accept \- prepare an accept request
-.SH SYNOPSIS
-.nf
-.B #include <sys/socket.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_accept(struct io_uring_sqe *" sqe ","
-.BI " int " sockfd ","
-.BI " struct sockaddr *" addr ","
-.BI " socklen_t *" addrlen ","
-.BI " int " flags ");"
-.PP
-.BI "void io_uring_prep_accept_direct(struct io_uring_sqe *" sqe ","
-.BI " int " sockfd ","
-.BI " struct sockaddr *" addr ","
-.BI " socklen_t *" addrlen ","
-.BI " int " flags ","
-.BI " unsigned int " file_index ");"
-.PP
-.BI "void io_uring_prep_multishot_accept(struct io_uring_sqe *" sqe ","
-.BI " int " sockfd ","
-.BI " struct sockaddr *" addr ","
-.BI " socklen_t *" addrlen ","
-.BI " int " flags ");"
-.PP
-.BI "void io_uring_prep_multishot_accept_direct(struct io_uring_sqe *" sqe ","
-.BI " int " sockfd ","
-.BI " struct sockaddr *" addr ","
-.BI " socklen_t *" addrlen ","
-.BI " int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_accept (3)
-function and its three variants prepare an accept request similar to
-.BR accept4 (2).
-The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I sockfd
-to start accepting a connection request described by the socket address at
-.I addr
-and of structure length
-.I addrlen
-and using modifier flags in
-.IR flags .
-
-The three variants allow combining the direct file table and multishot features.
-
-Direct descriptors are io_uring private file descriptors. They
-avoid some of the overhead associated with thread shared file tables and
-can be used in any io_uring request that takes a file descriptor.
-The two direct variants here create such direct descriptors.
-Subsequent to their creation, they can be used by setting
-.B IOSQE_FIXED_FILE
-in the SQE
-.I flags
-member, and setting the SQE
-.I fd
-field to the direct descriptor value rather than the regular file
-descriptor. Direct descriptors are managed like registered files.
-
-To use an accept direct variant, the application must first have registered
-a file table of a desired size using
-.BR io_uring_register_files (3)
-or
-.BR io_uring_register_files_sparse (3).
-Once registered,
-.BR io_uring_prep_accept_direct (3)
-allows an entry in that table to be specifically selected through the
-.I file_index
-argument.
-If the specified entry already contains a file, the file will first be removed
-from the table and closed, consistent with the behavior of updating an
-existing file with
-.BR io_uring_register_files_update (3).
-.I file_index
-can also be set to
-.B IORING_FILE_INDEX_ALLOC
-for this variant and
-an unused table index will be dynamically chosen and returned.
-Likewise,
-.B io_uring_prep_multishot_accept_direct
-will have an unused table index dynamically chosen and returned for each connection accepted.
-If both forms of direct selection will be employed, specific and dynamic, see
-.BR io_uring_register_file_alloc_range (3)
-for setting up the table so dynamically chosen entries are made against
-a different range than that targeted by specific requests.
-
-Note that old kernels don't check the SQE
-.I file_index
-field meaning
-applications cannot rely on a
-.B -EINVAL
-CQE
-.I res
-being returned when the kernel is too old because older kernels
-may not recognize they are being asked to use a direct table slot.
-
-When a direct descriptor accept request asks for a table slot to be
-dynamically chosen but there are no free entries,
-.B -ENFILE
-is returned as the CQE
-.IR res .
-
-The multishot variants allow an application to issue
-a single accept request, which will repeatedly trigger a CQE when a connection
-request comes in. Like other multishot type requests, the application should
-look at the CQE
-.I flags
-and see if
-.B IORING_CQE_F_MORE
-is set on completion as an indication of whether or not the accept request
-will generate further CQEs. Note that for the multishot variants, setting
-.B addr
-and
-.B addrlen
-may not make a lot of sense, as the same value would be used for every
-accepted connection. This means that the data written to
-.B addr
-may be overwritten by a new connection before the application has had time
-to process a past connection. If the application knows that a new connection
-cannot come in before a previous one has been processed, it may be used as
-expected. The multishot variants are available since 5.19.
-
-See the man page
-.BR accept4 (2)
-for details of the accept function itself.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation.
-
-.BR io_uring_prep_accept (3)
-generates the installed file descriptor as its result.
-
-.BR io_uring_prep_accept_direct (3)
-and
-.I file_index
-set to a specific direct descriptor
-generates
-.B 0
-on success.
-The caller must remember which direct descriptor was picked for this request.
-
-.BR io_uring_prep_accept_direct (3)
-and
-.I file_index
-set to
-.B IORING_FILE_INDEX_ALLOC
-generates the dynamically chosen direct descriptor.
-
-.BR io_uring_prep_multishot_accept (3)
-generates the installed file descriptor in each result.
-
-.BR io_uring_prep_multishot_accept_direct (3),
-generates the dynamically chosen direct descriptor in each result.
-
-Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it generates the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.P
-Note that the direct versions of accept do not accept
-.B SOCK_CLOEXEC ,
-and setting that flag will result in an
-.B -EINVAL
-error in the CQE.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_register_files (3),
-.BR io_uring_register_files_sparse (3),
-.BR io_uring_register_file_alloc_range (3),
-.BR io_uring_register (2),
-.BR accept4 (2)
diff --git a/src/liburing/man/io_uring_prep_accept_direct.3 b/src/liburing/man/io_uring_prep_accept_direct.3
deleted file mode 120000
index 0404bf59f71a..000000000000
--- a/src/liburing/man/io_uring_prep_accept_direct.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_accept.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_bind.3 b/src/liburing/man/io_uring_prep_bind.3
deleted file mode 100644
index e2a1cf9b6bcf..000000000000
--- a/src/liburing/man/io_uring_prep_bind.3
+++ /dev/null
@@ -1,54 +0,0 @@
-.\" Copyright (C) 2024 SUSE LLC
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_bind 3 "Jun 3, 2024" "liburing-2.7" "liburing Manual"
-.SH NAME
-io_uring_prep_bind \- prepare a bind request
-.SH SYNOPSIS
-.nf
-.B #include <sys/socket.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_bind(struct io_uring_sqe *" sqe ","
-.BI " int " sockfd ","
-.BI " struct sockaddr *" addr ","
-.BI " socklen_t " addrlen ");"
-.fi
-.SH DESCRIPTION
-The
-.BR io_uring_prep_bind (3)
-function prepares a bind request. The submission queue entry
-.I sqe
-is setup to assign the network address at
-.IR addr ,
-of length
-.IR addrlen ,
-to the socket descriptor
-.IR sockfd.
-
-This function prepares an async
-.BR bind (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR bind (2)
diff --git a/src/liburing/man/io_uring_prep_cancel.3 b/src/liburing/man/io_uring_prep_cancel.3
deleted file mode 100644
index 75d4fb55deec..000000000000
--- a/src/liburing/man/io_uring_prep_cancel.3
+++ /dev/null
@@ -1,136 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_cancel 3 "March 12, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_cancel \- prepare a cancelation request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_cancel64(struct io_uring_sqe *" sqe ","
-.BI " __u64 " user_data ","
-.BI " int " flags ");"
-.PP
-.BI "void io_uring_prep_cancel(struct io_uring_sqe *" sqe ","
-.BI " void *" user_data ","
-.BI " int " flags ");"
-.PP
-.BI "void io_uring_prep_cancel_fd(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " unsigned int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_cancel (3)
-function prepares a cancelation request. The submission queue entry
-.I sqe
-is prepared to cancel an existing request identified by
-.IR user_data .
-For the
-.I flags
-argument, see below.
-
-.BR io_uring_prep_cancel64 (3)
-is identical to
-.BR io_uring_prep_cancel (3) ,
-except it takes a 64-bit integer rather than a pointer type.
-
-The cancelation request will attempt to find the previously issued request
-identified by
-.I user_data
-and cancel it. The identifier is what the previously issued request has in
-their
-.I user_data
-field in the SQE.
-
-The
-.BR io_uring_prep_cancel_fd (3)
-function prepares a cancelation request. The submission queue entry
-.I sqe
-is prepared to cancel an existing request that used the file descriptor
-.IR fd .
-For the
-.I flags
-argument, see below.
-
-The cancelation request will attempt to find the previously issued request
-that used
-.I fd
-as the file descriptor and cancel it.
-
-By default, the first request matching the criteria given will be canceled.
-This can be modified with any of the following flags passed in:
-.TP
-.B IORING_ASYNC_CANCEL_ALL
-Cancel all requests that match the given criteria, rather than just canceling
-the first one found. Available since 5.19.
-.TP
-.B IORING_ASYNC_CANCEL_FD
-Match based on the file descriptor used in the original request rather than
-the user_data. This is what
-.BR io_uring_prep_cancel_fd (3)
-sets up. Available since 5.19.
-.TP
-.B IORING_ASYNC_CANCEL_FD_FIXED
-Set in conjunction with
-.B IORING_ASYNC_CANCEL_FD ,
-indicating that the file descriptor given is a direct descriptor rather than
-a normal file descriptor. Available since 6.0.
-.TP
-.B IORING_ASYNC_CANCEL_ANY
-Match any request in the ring, regardless of user_data or file descriptor.
-Can be used to cancel any pending request in the ring. Available since 5.19.
-.TP
-.B IORING_ASYNC_CANCEL_USERDATA
-Match request based on the user data field set in the original request. This
-is the default lookup key, if no other key matching has been specified.
-Available since 6.6.
-.TP
-.B IORING_ASYNC_CANCEL_OP
-Use the original request opcode as the matching key. The opcopde requested
-must be set in the sqe
-.I len
-field after using one of the generic cancel preparation helpers. Available
-since 6.6.
-.P
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-These are the errors that are reported in the CQE
-.I res
-field. If no flags are used to cancel multiple requests,
-.B 0
-is returned on success. If flags are used to match multiple requests, then
-a positive value is returned indicating how many requests were found and
-canceled.
-.TP
-.B -ENOENT
-The request identified by
-.I user_data
-could not be located. This could be because it completed before the cancelation
-request was issued, or if an invalid identifier is used.
-.TP
-.B -EINVAL
-One of the fields set in the SQE was invalid.
-.TP
-.B -EALREADY
-The execution state of the request has progressed far enough that cancelation
-is no longer possible. This should normally mean that it will complete shortly,
-either successfully, or interrupted due to the cancelation.
-.SH NOTES
-Although the cancelation request uses async request syntax, the kernel side of
-the cancelation is always run synchronously. It is guaranteed that a CQE is
-always generated by the time the cancel request has been submitted. If the
-cancelation is successful, the completion for the request targeted for
-cancelation will have been posted by the time submission returns. For
-.B -EALREADY
-it may take a bit of time to do so. For this case, the caller must wait for the
-canceled request to post its completion event.
-.SH SEE ALSO
-.BR io_uring_prep_poll_remove (3),
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3)
diff --git a/src/liburing/man/io_uring_prep_cancel64.3 b/src/liburing/man/io_uring_prep_cancel64.3
deleted file mode 120000
index 347db090d118..000000000000
--- a/src/liburing/man/io_uring_prep_cancel64.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_cancel.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_cancel_fd.3 b/src/liburing/man/io_uring_prep_cancel_fd.3
deleted file mode 120000
index 347db090d118..000000000000
--- a/src/liburing/man/io_uring_prep_cancel_fd.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_cancel.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_close.3 b/src/liburing/man/io_uring_prep_close.3
deleted file mode 100644
index d7eac2e89d0c..000000000000
--- a/src/liburing/man/io_uring_prep_close.3
+++ /dev/null
@@ -1,67 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_close 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_close \- prepare a file descriptor close request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_close(struct io_uring_sqe *" sqe ","
-.BI " int " fd ");"
-.PP
-.BI "void io_uring_prep_close_direct(struct io_uring_sqe *" sqe ","
-.BI " unsigned " file_index ");"
-.PP
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_close (3)
-function prepares a close request. The submission queue entry
-.I sqe
-is setup to close the file descriptor indicated by
-.IR fd .
-
-For a direct descriptor close request, the offset is specified by the
-.I file_index
-argument instead of the
-.IR fd .
-This is identical to unregistering the direct descriptor, and is provided as
-a convenience. Note that even though it's closing a direct descriptor, the
-application must not set
-.B IOSQE_FIXED_FILE
-on the SQE. Otherwise the request will complete with
-.B -EBADF
-as the result.
-
-These functions prepare an async
-.BR close (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. For closing of a direct descriptor, the only
-failure cases are the kernel running completely out of memory, or if the
-application has specified an invalid direct descriptor. Note that where
-synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR close (2)
diff --git a/src/liburing/man/io_uring_prep_close_direct.3 b/src/liburing/man/io_uring_prep_close_direct.3
deleted file mode 120000
index d9ce6a60fa96..000000000000
--- a/src/liburing/man/io_uring_prep_close_direct.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_close.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_cmd.3 b/src/liburing/man/io_uring_prep_cmd.3
deleted file mode 100644
index 76f00b708781..000000000000
--- a/src/liburing/man/io_uring_prep_cmd.3
+++ /dev/null
@@ -1,126 +0,0 @@
-.\" Copyright (C) 2023 Breno Leitao <leitao@debian.org>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_cmd 3 "July 27, 2023" "liburing-2.5" "liburing Manual"
-.SH NAME
-io_uring_prep_cmd_sock \- prepare a command request for a socket
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_cmd_sock(struct io_uring_sqe *" sqe ","
-.BI " int " cmd_op ","
-.BI " int " fd ","
-.BI " int " level ","
-.BI " int " optname ","
-.BI " void " *optval ","
-.BI " int " optlen ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_cmd_sock (3)
-function prepares an cmd request for a socket. The submission queue entry
-.I sqe
-is setup to use the socket file descriptor pointed to by
-.I fd
-to start an command operation defined by
-.I cmd_op.
-
-This is a generic function, and each command has their own individual
-.I level, optname, optval
-values. The optlen defines the size pointed by
-.I optval.
-
-.SH Available commands
-
-.TP
-.B SOCKET_URING_OP_SIOCINQ
-Returns the amount of queued unread data in the receive buffer.
-The socket must not be in LISTEN state, otherwise an error
-.B -EINVAL
-is returned in the CQE
-.I res
-field.
-The following arguments are not used for this command
-.I level, optname, optval
-and
-.I optlen.
-
-Negative return value means an error.
-
-For more information about this command, please check
-.BR unix(7).
-
-Available since 6.7.
-
-.TP
-.B SOCKET_URING_OP_SIOCOUTQ
-Returns the amount of unsent data in the socket send queue.
-The socket must not be in LISTEN state, otherwise an error
-.B -EINVAL
-is returned in the CQE
-.I res.
-field.
-The following arguments are not used for this command
-.I level, optname, optval
-and
-.I optlen.
-
-Negative return value means an error.
-
-For more information about this command, please check
-.BR unix(7).
-
-.TP
-.B SOCKET_URING_OP_GETSOCKOPT
-Command to get options for the socket referred to by the socket file descriptor
-.I fd.
-The arguments are similar to the
-.BR getsockopt(2)
-system call.
-
-The
-.BR SOCKET_URING_OP_GETSOCKOPT
-command is limited to
-.BR SOL_SOCKET
-.I level.
-
-Differently from the
-.BR getsockopt(2)
-system call, the updated
-.I optlen
-value is returned in the CQE
-.I res
-field, on success. On failure, the CQE
-.I res
-contains a negative error number.
-
-.TP
-.B SOCKET_URING_OP_SETSOCKOPT
-Command to set options for the socket referred to by the socket file descriptor
-.I fd.
-The arguments are similar to the
-.BR setsockopt(2)
-system call.
-
-Available since 6.7.
-
-.SH NOTES
-The memory block pointed by
-.I optval
-needs to be valid/live until the CQE returns.
-
-.SH RETURN VALUE
-Dependent on the command.
-
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_register (2),
-.BR unix (7)
diff --git a/src/liburing/man/io_uring_prep_cmd_discard.3 b/src/liburing/man/io_uring_prep_cmd_discard.3
deleted file mode 100644
index 97786726f03b..000000000000
--- a/src/liburing/man/io_uring_prep_cmd_discard.3
+++ /dev/null
@@ -1,64 +0,0 @@
-.\" Copyright (C) 2024 Pavel Begunkov <asml.silence@gmail.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_cmd_discard 3 "Oct 13, 2024" "liburing-2.8" "liburing Manual"
-.SH NAME
-io_uring_prep_cmd_discard \- prepare a discard command
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_cmd_discard(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " uint64_t " offset ","
-.BI " uint64_t " nbytes ");"
-.fi
-.SH DESCRIPTION
-The
-.BR io_uring_prep_cmd_discard (3)
-function prepares a discard command request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.IR fd
-to start discarding
-.I nbytes
-at the specified
-.IR offset .
-
-The command is an asynchronous equivalent of
-.B BLOCK_URING_CMD_DISCARD
-ioctl with a few differences. It allows multiple parallel discards, and it does
-not exclude concurrent writes and reads. As a result, it may lead to races for
-the data on the disk, if the application has IO inflight for the same ranges
-that the discard operates on. It's the user's responsibility to account for that.
-Furthermore, only best efforts are done to invalidate page caches. The user has
-to make sure that no other inflight requests are modifying or reading the
-range(s). If that is the case, it might result in stale page cache and data
-inconsistencies.
-
-Available since 6.12.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. On success, this field will be
-set to
-.B 0 .
-On error, a negative error value is returned. Note that where synchronous
-system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
diff --git a/src/liburing/man/io_uring_prep_connect.3 b/src/liburing/man/io_uring_prep_connect.3
deleted file mode 100644
index 6a7c64a6da7e..000000000000
--- a/src/liburing/man/io_uring_prep_connect.3
+++ /dev/null
@@ -1,66 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_connect 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_connect \- prepare a connect request
-.SH SYNOPSIS
-.nf
-.B #include <sys/types.h>
-.B #include <sys/socket.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_connect(struct io_uring_sqe *" sqe ","
-.BI " int " sockfd ","
-.BI " const struct sockaddr *" addr ","
-.BI " socklen_t " addrlen ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_connect (3)
-function prepares a connect request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I sockfd
-to start connecting to the destination described by the socket address at
-.I addr
-and of structure length
-.IR addrlen .
-
-This function prepares an async
-.BR connect (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR connect (2)
diff --git a/src/liburing/man/io_uring_prep_epoll_wait.3 b/src/liburing/man/io_uring_prep_epoll_wait.3
deleted file mode 100644
index 292f3974d7f8..000000000000
--- a/src/liburing/man/io_uring_prep_epoll_wait.3
+++ /dev/null
@@ -1,64 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_epoll_wait 3 "March 6, 2025" "liburing-2.10" "liburing Manual"
-.SH NAME
-io_uring_prep_epoll_wait \- prepare an epoll wait request
-.SH SYNOPSIS
-.nf
-.B #include <sys/epoll.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_epoll_wait(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " struct epoll_event *" events ","
-.BI " int " maxevents ","
-.BI " unsigned flags ");"
-.PP
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_epoll_wait (3)
-function prepares an epoll_wait request. The submission queue entry
-.I sqe
-is setup to wait on a maximum of
-.IR maxevents
-events on the epoll file descriptor indicated by
-.IR fd ,
-and filling the received events into the memory pointed to by
-.IR events .
-
-This function prepares an async
-.BR epoll_wait (2)
-request. See that man page for details. The use case is mostly for legacy
-event loops, where certain file descriptors may still be using epoll for
-readiness notifications. Normally this would necessitate using epoll_wait
-with the io_uring fd added to that set as well, which is suboptimal as
-epoll doesn't provide the same kind of fine grained batch control and
-wakeup reductions that io_uring does. By using io_uring to read epoll events,
-the event loop can be entirely switched to io_uring, and reap the benefits
-of batch waiting and context switch reductions.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR epoll_wait (2)
diff --git a/src/liburing/man/io_uring_prep_fadvise.3 b/src/liburing/man/io_uring_prep_fadvise.3
deleted file mode 100644
index 226eee59d7fe..000000000000
--- a/src/liburing/man/io_uring_prep_fadvise.3
+++ /dev/null
@@ -1,76 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_fadvise 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_fadvise \- prepare a fadvise request
-.SH SYNOPSIS
-.nf
-.B #include <fcntl.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_fadvise(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " __u64 " offset ","
-.BI " __u32 " len ","
-.BI " int " advice ");"
-.BI "
-.BI "void io_uring_prep_fadvise64(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " __u64 " offset ","
-.BI " off_t " len ","
-.BI " int " advice ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_fadvise (3)
-function prepares an fadvise request. The submission queue entry
-.I sqe
-is setup to use the file descriptor pointed to by
-.I fd
-to start an fadvise operation at
-.I offset
-and of
-.I len
-length in bytes, giving it the advise located in
-.IR advice .
-
-The
-.BR io_uring_prep_fadvise64 (3)
-function works like
-.BR io_uring_prep_fadvise (3)
-except that it takes a 64-bit length rather than just a 32-bit one. Older
-kernels may not support the 64-bit length variant. If this variant is attempted
-used on a kernel that doesn't support 64-bit lengths, then the request will get
-errored with
-.B -EINVAL
-in the results field of the CQE.
-
-This function prepares an async
-.BR posix_fadvise (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_register (2),
-.BR posix_fadvise (2)
diff --git a/src/liburing/man/io_uring_prep_fadvise64.3 b/src/liburing/man/io_uring_prep_fadvise64.3
deleted file mode 120000
index cfd68287ae6c..000000000000
--- a/src/liburing/man/io_uring_prep_fadvise64.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_fadvise.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_fallocate.3 b/src/liburing/man/io_uring_prep_fallocate.3
deleted file mode 100644
index 426e1d52d08e..000000000000
--- a/src/liburing/man/io_uring_prep_fallocate.3
+++ /dev/null
@@ -1,59 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_fallocate 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_fallocate \- prepare a fallocate request
-.SH SYNOPSIS
-.nf
-.B #include <fcntl.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_fallocate(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " int " mode ","
-.BI " __u64 " offset ","
-.BI " __u64 " len ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_fallocate (3)
-function prepares a fallocate request. The submission queue entry
-.I sqe
-is setup to use the file descriptor pointed to by
-.I fd
-to start a fallocate operation described by
-.I mode
-at offset
-.I offset
-and
-.I len
-length in bytes.
-
-This function prepares an async
-.BR fallocate (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR fallocate (2)
diff --git a/src/liburing/man/io_uring_prep_fgetxattr.3 b/src/liburing/man/io_uring_prep_fgetxattr.3
deleted file mode 120000
index fd0634a9aa4f..000000000000
--- a/src/liburing/man/io_uring_prep_fgetxattr.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_getxattr.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_files_update.3 b/src/liburing/man/io_uring_prep_files_update.3
deleted file mode 100644
index bedb85e0debf..000000000000
--- a/src/liburing/man/io_uring_prep_files_update.3
+++ /dev/null
@@ -1,92 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_files_update 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_files_update \- prepare a registered file update request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_files_update(struct io_uring_sqe *" sqe ","
-.BI " int *" fds ","
-.BI " unsigned " nr_fds ","
-.BI " int " offset ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_files_update (3)
-function prepares a request for updating a number of previously registered file
-descriptors. The submission queue entry
-.I sqe
-is setup to use the file descriptor array pointed to by
-.I fds
-and of
-.I nr_fds
-in length to update that amount of previously registered files starting at
-offset
-.IR offset .
-
-Once a previously registered file is updated with a new one, the existing
-entry is updated and then removed from the table. This operation is equivalent to
-first unregistering that entry and then inserting a new one, just bundled into
-one combined operation.
-
-If
-.I offset
-is specified as IORING_FILE_INDEX_ALLOC, io_uring will allocate free direct
-descriptors instead of having the application to pass, and store allocated
-direct descriptors into
-.I fds
-array,
-.I cqe->res
-will return the number of direct descriptors allocated.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-These are the errors that are reported in the CQE
-.I res
-field. On success,
-.I res
-will contain the number of successfully updated file descriptors. On error,
-the following errors can occur.
-.TP
-.B -ENOMEM
-The kernel was unable to allocate memory for the request.
-.TP
-.B -EINVAL
-One of the fields set in the SQE was invalid.
-.TP
-.B -EFAULT
-The kernel was unable to copy in the memory pointed to by
-.IR fds .
-.TP
-.B -EBADF
-On of the descriptors located in
-.I fds
-didn't refer to a valid file descriptor, or one of the file descriptors in
-the array referred to an io_uring instance.
-.TP
-.B -EOVERFLOW
-The product of
-.I offset
-and
-.I nr_fds
-exceed the valid amount or overflowed.
-.SH NOTES
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_register (2)
diff --git a/src/liburing/man/io_uring_prep_fixed_fd_install.3 b/src/liburing/man/io_uring_prep_fixed_fd_install.3
deleted file mode 100644
index 3300c45046c6..000000000000
--- a/src/liburing/man/io_uring_prep_fixed_fd_install.3
+++ /dev/null
@@ -1,70 +0,0 @@
-.\" Copyright (C) 2023 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_fixed_fd_install 3 "December 8, 2023" "liburing-2.6" "liburing Manual"
-.SH NAME
-io_uring_prep_fixed_fd_install \- prepare fixed file fd installation request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_fixed_fd_install(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " unsigned int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_fixed_fd_install (3)
-helper prepares a fixed file descriptor installation. The submission queue entry
-.I sqe
-is setup to install the direct/fixed file descriptor
-.I fd
-with the specified
-.I flags
-file installation flags.
-
-One use case of direct/fixed file descriptors is to turn a regular file
-descriptor into a direct one, reducing the overhead of any request that
-needs to access this file. This helper provides a way to go the other way,
-turning a direct descriptor into a regular file descriptor that can then
-subsequently be used by regular system calls that take a normal file descriptor.
-This can be handy if no regular file descriptor exists for this direct
-descriptor. Either because it was instantiated directly as a fixed descriptor,
-or because the regular file was closed with
-.BR close (2)
-after being turned into a direct descriptor.
-
-Upon successful return of this request, both a normal and fixed file descriptor
-exists for the same file. Either one of them may be used to access the file.
-Either one of them may be closed without affecting the other one.
-
-.I flags
-may be either zero, or set to
-.B IORING_FIXED_FD_NO_CLOEXEC
-to indicate that the new regular file descriptor should not be closed during
-exec. By default,
-.B O_CLOEXEC
-will be set on the new descriptor otherwise. Setting this field to anything but
-those two values will result in the request being failed with
-.B -EINVAL
-in the CQE
-.I res
-field.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation, which in this case will be the
-value of the new regular file descriptor. In case of failure, a negative value
-is returned.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_register_files (3),
-.BR io_uring_unregister_files (3),
-.BR io_uring_prep_close_direct (3),
-.BR io_uring_prep_openat_direct (3)
diff --git a/src/liburing/man/io_uring_prep_fsetxattr.3 b/src/liburing/man/io_uring_prep_fsetxattr.3
deleted file mode 120000
index 724254cda21d..000000000000
--- a/src/liburing/man/io_uring_prep_fsetxattr.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_setxattr.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_fsync.3 b/src/liburing/man/io_uring_prep_fsync.3
deleted file mode 100644
index a3259a0cdef8..000000000000
--- a/src/liburing/man/io_uring_prep_fsync.3
+++ /dev/null
@@ -1,70 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_fsync 3 "March 12, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_fsync \- prepare an fsync request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_fsync(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " unsigned " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_fsync (3)
-function prepares an fsync request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I fd
-that should get synced, with the modifier flags indicated by the
-.I flags
-argument.
-
-This function prepares an fsync request. It can act either like an
-.BR fsync (2)
-operation, which is the default behavior. If
-.B IORING_FSYNC_DATASYNC
-is set in the
-.I flags
-argument, then it behaves like
-.BR fdatasync (2).
-If no range is specified, the
-.I fd
-will be synced from 0 to end-of-file.
-
-It's possible to specify a range to sync, if one is desired. If the
-.I off
-field of the SQE is set to non-zero, then that indicates the offset to
-start syncing at. If
-.I len
-is set in the SQE, then that indicates the size in bytes to sync from the
-offset. Note that these fields are not accepted by this helper, so they have
-to be set manually in the SQE after calling this prep helper.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR fsync (2),
-.BR fdatasync (2)
diff --git a/src/liburing/man/io_uring_prep_ftruncate.3 b/src/liburing/man/io_uring_prep_ftruncate.3
deleted file mode 100644
index e3f1f7e03366..000000000000
--- a/src/liburing/man/io_uring_prep_ftruncate.3
+++ /dev/null
@@ -1,54 +0,0 @@
-.\" Copyright (C) 2024 Tony Solomonik <tony.solomonik@gmail.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_ftruncate 3 "January 23, 2024" "liburing-2.6" "liburing Manual"
-.SH NAME
-io_uring_prep_ftruncate \- prepare an ftruncate request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_ftruncate(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " loff_t " len ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_ftruncate (3)
-function prepares an ftruncate request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I fd
-that should get truncated to the length indicated by the
-.I len
-argument.
-
-Applications must define
-.B _GNU_SOURCE
-to obtain the definition of this helper, as
-.I loff_t
-will not be defined without it.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR ftruncate (2),
diff --git a/src/liburing/man/io_uring_prep_futex_wait.3 b/src/liburing/man/io_uring_prep_futex_wait.3
deleted file mode 100644
index ab891120de4f..000000000000
--- a/src/liburing/man/io_uring_prep_futex_wait.3
+++ /dev/null
@@ -1,94 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_futex_wait 3 "Sep 29, 2023" "liburing-2.5" "liburing Manual"
-.SH NAME
-io_uring_prep_futex_wait \- prepare a futex wait request
-.SH SYNOPSIS
-.nf
-.B #include <linux/futex.h>
-.B #include <unistd.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_futex_wait(struct io_uring_sqe *" sqe ","
-.BI " uint32_t *" futex ","
-.BI " uint64_t " val ","
-.BI " uint64_t " mask ","
-.BI " uint32_t " futex_flags ","
-.BI " unsigned int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_futex_wait (3)
-function prepares a futex wait request. The submission queue entry
-.I sqe
-is setup for waiting on a futex at address
-.I futex
-and which still has the value
-.I val
-and with
-.BR futex2 (2)
-flags of
-.I futex_flags
-and io_uring futex flags of
-.I flags .
-
-.I mask
-can be set to a specific bitset mask, which will be matched by the waking
-side to decide who to wake up. To always get woken, an application may use
-.B FUTEX_BITSET_MATCH_ANY .
-
-.I futex_flags
-follows the
-.BR futex2 (2)
-flags, not the
-.BR futex (2)
-v1 interface flags.
-
-.I flags
-are currently unused and hence
-.B 0
-must be passed.
-
-This function prepares an async
-.BR futex (2)
-wait request. See that man page for details. Note that the io_uring futex
-wait request is similar to the
-.B FUTEX_WAIT_BITSET
-operation, as
-.B FUTEX_WAIT
-is a strict subset of that.
-
-Available since kernel 6.7.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-Unlike the sync futex syscalls that wait on a futex, io_uring does not support
-passing in a timeout for the request. Instead, applications are encouraged
-to use a linked timeout to abort the futex request at a given time, if desired.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_prep_futex_waitv (3),
-.BR io_uring_prep_futex_wake (3),
-.BR io_uring_prep_link_timeout (3),
-.BR futex (2)
-.BR futex2 (2)
diff --git a/src/liburing/man/io_uring_prep_futex_waitv.3 b/src/liburing/man/io_uring_prep_futex_waitv.3
deleted file mode 100644
index c4baf5ae1997..000000000000
--- a/src/liburing/man/io_uring_prep_futex_waitv.3
+++ /dev/null
@@ -1,78 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_futex_waitv 3 "Sep 29, 2023" "liburing-2.5" "liburing Manual"
-.SH NAME
-io_uring_prep_futex_waitv \- prepare a futex waitv request
-.SH SYNOPSIS
-.nf
-.B #include <linux/futex.h>
-.B #include <unistd.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_futex_waitv(struct io_uring_sqe *" sqe ","
-.BI " struct futex_waitv *" futexv ","
-.BI " uint32_t " nr_futex ","
-.BI " unsigned int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_futex_waitv (3)
-function prepares a futex wait request for multiple futexes at the same time.
-The submission queue entry
-.I sqe
-is setup for waiting on all futexes given by
-.I futexv
-and
-.I nr_futex
-is the number of futexes in that array.
-.I flags
-must be set to the io_uring specific futex flags.
-
-Unlike
-.BR io_uring_prep_futex_wait (3),
-the desired bitset mask and values are passed in
-.IR futexv .
-
-.I flags
-are currently unused and hence
-.B 0
-must be passed.
-
-This function prepares an async
-.BR futex (2)
-waitv request. See that man page for details.
-
-Available since kernel 6.7.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-Unlike the sync futex syscalls that wait on a futex, io_uring does not support
-passing in a timeout for the request. Instead, applications are encouraged
-to use a linked timeout to abort the futex request at a given time, if desired.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_prep_futex_wait (3),
-.BR io_uring_prep_futex_wake (3),
-.BR io_uring_prep_link_timeout (3),
-.BR futex (2)
-.BR futex2 (2)
diff --git a/src/liburing/man/io_uring_prep_futex_wake.3 b/src/liburing/man/io_uring_prep_futex_wake.3
deleted file mode 100644
index 1f52b1150672..000000000000
--- a/src/liburing/man/io_uring_prep_futex_wake.3
+++ /dev/null
@@ -1,86 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_futex_wake 3 "Sep 29, 2023" "liburing-2.5" "liburing Manual"
-.SH NAME
-io_uring_prep_futex_wake \- prepare a futex wake request
-.SH SYNOPSIS
-.nf
-.B #include <linux/futex.h>
-.B #include <unistd.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_futex_wake(struct io_uring_sqe *" sqe ","
-.BI " uint32_t *" futex ","
-.BI " uint64_t " val ","
-.BI " uint64_t " mask ","
-.BI " uint32_t " futex_flags ","
-.BI " unsigned int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_futex_wake (3)
-function prepares a futex wake request. The submission queue entry
-.I sqe
-is setup for waking any waiters on the futex indicated by
-.I futex
-and at most
-.I val
-futexes.
-.I futex_flags
-indicates the
-.BR futex2 (2)
-modifier flags, and io_uring futex flags of
-.I flags .
-
-If a given bitset for who to wake is desired, then that must be set in
-.I mask .
-Use
-.B FUTEX_BITSET_MATCH_ANY
-to match any waiter on the given futex.
-
-.I flags
-are currently unused and hence
-.B 0
-must be passed.
-
-This function prepares an async
-.BR futex (2)
-wake request. See that man page for details. Note that the io_uring futex
-wake request is similar to the
-.B FUTEX_WAKE_BITSET
-operation, as
-.B FUTEX_WAKE
-is a strict subset of that.
-
-Available since kernel 6.7.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. On success, the value will be
-the index into
-.I futexv
-which received a wakeup. See the related man page for details on possible
-values for errors. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_prep_futex_wait (3),
-.BR io_uring_prep_futex_waitv (3),
-.BR futex (2)
-.BR futex2 (2)
diff --git a/src/liburing/man/io_uring_prep_getxattr.3 b/src/liburing/man/io_uring_prep_getxattr.3
deleted file mode 100644
index 612740566c24..000000000000
--- a/src/liburing/man/io_uring_prep_getxattr.3
+++ /dev/null
@@ -1,61 +0,0 @@
-.\" Copyright (C) 2023 Rutvik Patel <heyrutvik@gmail.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_getxattr 3 "January 23, 2023" "liburing-2.4" "liburing Manual"
-.SH NAME
-io_uring_prep_getxattr, io_uring_prep_fgetxattr \- prepare a request to get an
-extended attribute value
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_getxattr(struct io_uring_sqe *" sqe ","
-.BI " const char *" name ","
-.BI " char *" value ","
-.BI " const char *" path ","
-.BI " unsigned int " len ");"
-.PP
-.BI "void io_uring_prep_fgetxattr(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " const char *" name ","
-.BI " char *" value ","
-.BI " unsigned int " len ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_getxattr (3)
-function prepares a request to get an extended attribute value. The submission
-queue entry
-.I sqe
-is setup to get the
-.I value
-of the extended attribute identified by
-.I name
-and associated with the given
-.I path
-in the filesystem.
-The
-.I len
-argument specifies the size (in bytes) of
-.IR value .
-
-.BR io_uring_prep_fgetxattr (3)
-is identical to
-.BR io_uring_prep_getxattr (3),
-only the open file referred to by
-.I fd
-is interrogated in place of
-.IR path .
-
-This function prepares an async
-.BR getxattr (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR getxattr (2)
diff --git a/src/liburing/man/io_uring_prep_link.3 b/src/liburing/man/io_uring_prep_link.3
deleted file mode 120000
index 6d3059de30f4..000000000000
--- a/src/liburing/man/io_uring_prep_link.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_linkat.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_link_timeout.3 b/src/liburing/man/io_uring_prep_link_timeout.3
deleted file mode 100644
index a4c6c08ea4da..000000000000
--- a/src/liburing/man/io_uring_prep_link_timeout.3
+++ /dev/null
@@ -1,98 +0,0 @@
-.\" Copyright (C) 2023 Rutvik Patel <heyrutvik@gmail.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_link_timeout 3 "January 23, 2023" "liburing-2.4" "liburing Manual"
-.SH NAME
-io_uring_prep_link_timeout \- a timeout request for linked sqes
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_link_timeout(struct io_uring_sqe *" sqe ","
-.BI " struct __kernel_timespec *" ts ","
-.BI " unsigned " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_link_timeout (3)
-function prepares a timeout request for linked sqes. The submission queue entry
-.I sqe
-is setup for with timeout specified by
-.IR ts .
-The flags argument holds modifier
-.I flags
-for the timeout behaviour of the request.
-
-The
-.I ts
-argument must be filled in with the appropriate information for the timeout. It
-looks as follows:
-.PP
-.in +4n
-.EX
-struct __kernel_timespec {
- __kernel_time64_t tv_sec;
- long long tv_nsec;
-};
-.EE
-.in
-.PP
-
-The
-.I flags
-argument may contain:
-.TP
-.B IORING_TIMEOUT_ABS
-The value specified in
-.I ts
-is an absolute value rather than a relative one.
-.TP
-.B IORING_TIMEOUT_BOOTTIME
-The boottime clock source should be used.
-.TP
-.B IORING_TIMEOUT_REALTIME
-The realtime clock source should be used.
-.TP
-.B IORING_TIMEOUT_ETIME_SUCCESS
-Consider an expired timeout a success in terms of the posted completion.
-.PP
-
-It is invalid to create a chain (linked sqes) consisting only of a link timeout
-request. If all the requests in the chain are completed before timeout, then the
-link timeout request gets canceled. Upon timeout, all the uncompleted requests
-in the chain get canceled.
-
-.SH RETURN VALUE
-None
-
-.SH ERRORS
-.PP
-These are the errors that are reported in the CQE
-.I res
-field. On success,
-.B 0
-is returned.
-.TP
-.B -ETIME
-The specified timeout occurred and triggered the completion event.
-.TP
-.B -EINVAL
-One of the fields set in the SQE was invalid. For example, two clock sources
-where given, or the specified timeout seconds or nanoseconds where < 0.
-.TP
-.B -EFAULT
-io_uring was unable to access the data specified by ts.
-.TP
-.B -ECANCELED
-The timeout was canceled because all submitted requests were completed successfully
-or one of the requests resulted in failure.
-.TP
-.B -ENOENT
-The request to which the linked timeout was linked already completed and could
-not be found when the timer expired.
-
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_prep_timeout (3)
diff --git a/src/liburing/man/io_uring_prep_linkat.3 b/src/liburing/man/io_uring_prep_linkat.3
deleted file mode 100644
index 0949e3b42fb5..000000000000
--- a/src/liburing/man/io_uring_prep_linkat.3
+++ /dev/null
@@ -1,91 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_linkat 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_linkat \- prepare a linkat request
-.SH SYNOPSIS
-.nf
-.B #include <fcntl.h>
-.B #include <unistd.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_linkat(struct io_uring_sqe *" sqe ","
-.BI " int " olddirfd ","
-.BI " const char *" oldpath ","
-.BI " int " newdirfd ","
-.BI " const char *" newpath ","
-.BI " int " flags ");"
-.PP
-.BI "void io_uring_prep_link(struct io_uring_sqe *" sqe ","
-.BI " const char *" oldpath ","
-.BI " const char *" newpath ","
-.BI " int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_linkat (3)
-function prepares a linkat request. The submission queue entry
-.I sqe
-is setup to use the old directory file descriptor pointed to by
-.I olddirfd
-and old path pointed to by
-.I oldpath
-with the new directory file descriptor pointed to by
-.I newdirfd
-and the new path pointed to by
-.I newpath
-and using the specified flags in
-.IR flags .
-
-The
-.BR io_uring_prep_link (3)
-function prepares a link request. The submission queue entry
-.I sqe
-is setup to use the old path pointed to by
-.I oldpath
-and the new path pointed to by
-.IR newpath ,
-both relative to the current working directory and using the specified flags in
-.IR flags .
-
-These functions prepare an async
-.BR linkat (2)
-or
-.BR link (2)
-request. See those man pages for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR linkat (2),
-.BR link (2)
diff --git a/src/liburing/man/io_uring_prep_listen.3 b/src/liburing/man/io_uring_prep_listen.3
deleted file mode 100644
index b765298aaf45..000000000000
--- a/src/liburing/man/io_uring_prep_listen.3
+++ /dev/null
@@ -1,52 +0,0 @@
-.\" Copyright (C) 2024 SUSE LLC.
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_listen 3 "Jun 3, 2024" "liburing-2.7" "liburing Manual"
-.SH NAME
-io_uring_prep_listen \- prepare a listen request
-.SH SYNOPSIS
-.nf
-.B #include <sys/socket.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_listen(struct io_uring_sqe *" sqe ","
-.BI " int " sockfd ","
-.BI " int" backlog ");"
-.fi
-.SH DESCRIPTION
-The
-.BR io_uring_prep_listen (3)
-function prepares a listen request. The submission queue entry
-.I sqe
-is setup to place the socket file descriptor pointed by
-.IR sockfd
-into a state to accept incoming connections. The parameter
-.IR backlog ,
-defines the maximum length of the queue of pending connections.
-
-This function prepares an async
-.BR listen (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR listen (2)
diff --git a/src/liburing/man/io_uring_prep_madvise.3 b/src/liburing/man/io_uring_prep_madvise.3
deleted file mode 100644
index f29fa920de3c..000000000000
--- a/src/liburing/man/io_uring_prep_madvise.3
+++ /dev/null
@@ -1,72 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_madvise 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_madvise \- prepare a madvise request
-.SH SYNOPSIS
-.nf
-.B #include <sys/mman.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_madvise(struct io_uring_sqe *" sqe ","
-.BI " void *" addr ","
-.BI " __u32 " len ","
-.BI " int " advice ");"
-.BI "
-.BI "void io_uring_prep_madvise64(struct io_uring_sqe *" sqe ","
-.BI " void *" addr ","
-.BI " off_t " len ","
-.BI " int " advice ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_madvise (3)
-function prepares an madvise request. The submission queue entry
-.I sqe
-is setup to start an madvise operation at the virtual address of
-.I addr
-and of
-.I len
-length in bytes, giving it the advise located in
-.IR advice .
-
-The
-.BR io_uring_prep_madvise64 (3)
-function works like
-.BR io_uring_prep_madvise (3)
-except that it takes a 64-bit length rather than just a 32-bit one. Older
-kernels may not support the 64-bit length variant. If this variant is attempted
-used on a kernel that doesn't support 64-bit lengths, then the request will get
-errored with
-.B -EINVAL
-in the results field of the CQE.
-
-This function prepares an async
-.BR madvise (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_register (2),
-.BR madvise (2)
diff --git a/src/liburing/man/io_uring_prep_madvise64.3 b/src/liburing/man/io_uring_prep_madvise64.3
deleted file mode 120000
index 1a368eead297..000000000000
--- a/src/liburing/man/io_uring_prep_madvise64.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_madvise.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_mkdir.3 b/src/liburing/man/io_uring_prep_mkdir.3
deleted file mode 120000
index b3412d1d2c41..000000000000
--- a/src/liburing/man/io_uring_prep_mkdir.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_mkdirat.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_mkdirat.3 b/src/liburing/man/io_uring_prep_mkdirat.3
deleted file mode 100644
index a98b4e354078..000000000000
--- a/src/liburing/man/io_uring_prep_mkdirat.3
+++ /dev/null
@@ -1,83 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_mkdirat 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_mkdirat \- prepare an mkdirat request
-.SH SYNOPSIS
-.nf
-.B #include <fcntl.h>
-.B #include <sys/stat.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_mkdirat(struct io_uring_sqe *" sqe ","
-.BI " int " dirfd ","
-.BI " const char *" path ","
-.BI " mode_t " mode ");"
-.PP
-.BI "void io_uring_prep_mkdir(struct io_uring_sqe *" sqe ","
-.BI " const char *" path ","
-.BI " mode_t " mode ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_mkdirat (3)
-function prepares a mkdirat request. The submission queue entry
-.I sqe
-is setup to use the directory file descriptor pointed to by
-.I dirfd
-to start a mkdirat operation on the path identified by
-.I path
-with the mode given in
-.IR mode .
-
-The
-.BR io_uring_prep_mkdir (3)
-function prepares a mkdir request. The submission queue entry
-.I sqe
-is setup to use the current working directory to start a mkdir
-operation on the path identified by
-.I path
-with the mode given in
-.IR mode .
-
-These functions prepare an async
-.BR mkdir (2)
-or
-.BR mkdirat (2)
-request. See those man pages for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR mkdirat (2),
-.BR mkdir (2)
diff --git a/src/liburing/man/io_uring_prep_msg_ring.3 b/src/liburing/man/io_uring_prep_msg_ring.3
deleted file mode 100644
index 70caebe770b4..000000000000
--- a/src/liburing/man/io_uring_prep_msg_ring.3
+++ /dev/null
@@ -1,92 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_msg_ring 3 "March 10, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_msg_ring \- send a message to another ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_msg_ring(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " unsigned int " len ","
-.BI " __u64 " data ","
-.BI " unsigned int " flags ");"
-.PP
-.BI "void io_uring_prep_msg_ring_cqe_flags(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " unsigned int " len ","
-.BI " __u64 " data ","
-.BI " unsigned int " flags ","
-.BI " unsigned int " cqe_flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-.BR io_uring_prep_msg_ring (3)
-prepares to send a CQE to an io_uring file descriptor. The submission queue
-entry
-.I sqe
-is setup to use the file descriptor
-.IR fd ,
-which must identify a io_uring context, to post a CQE on that ring where the
-target CQE
-.B res
-field will contain the content of
-.I len
-and the
-.B user_data
-of
-.I data
-with the request modifier flags set by
-.IR flags .
-Currently there are no valid flag modifiers, this field must contain
-.BR 0 .
-
-The targeted ring may be any ring that the user has access to, even the ring
-itself. This request can be used for simple message passing to another ring,
-allowing 32+64 bits of data to be transferred through the
-.I len
-and
-.I data
-fields. The use case may be anything from simply waking up someone waiting
-on the targeted ring, or it can be used to pass messages between the two
-rings.
-
-.BR io_uring_prep_msg_ring_cqe_flags (3)
-is similar to
-.BR io_uring_prep_msg_ring (3) .
-But has an addition
-.I cqe_flags
-parameter, which is used to set
-.I flags
-field on CQE side. That way, you can set the CQE flags field
-.I cqe->flags
-when sending a message. Be aware that io_uring could potentially set additional
-bits into this field.
-
-.SH RETURN VALUE
-None
-
-.SH ERRORS
-These are the errors that are reported in the CQE
-.I res
-field.
-.TP
-.B -ENOMEM
-The kernel was unable to allocate memory for the request.
-.TP
-.B -EINVAL
-One of the fields set in the SQE was invalid.
-.TP
-.B -EBADFD
-The descriptor passed in
-.I fd
-does not refer to an io_uring file descriptor, or the ring is in a disabled
-state.
-.TP
-.B -EOVERFLOW
-The kernel was unable to fill a CQE on the target ring. This can happen if
-the target CQ ring is in an overflow state and the kernel wasn't able to
-allocate memory for a new CQE entry.
diff --git a/src/liburing/man/io_uring_prep_msg_ring_cqe_flags.3 b/src/liburing/man/io_uring_prep_msg_ring_cqe_flags.3
deleted file mode 120000
index c96663b8cb91..000000000000
--- a/src/liburing/man/io_uring_prep_msg_ring_cqe_flags.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_msg_ring.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_msg_ring_fd.3 b/src/liburing/man/io_uring_prep_msg_ring_fd.3
deleted file mode 100644
index 39cd34aa454d..000000000000
--- a/src/liburing/man/io_uring_prep_msg_ring_fd.3
+++ /dev/null
@@ -1,83 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_msg_ring_fd 3 "Mar 16, 2023" "liburing-2.4" "liburing Manual"
-.SH NAME
-io_uring_prep_msg_ring_fd \- send a direct descriptor to another ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_msg_ring_fd(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " int " source_fd ","
-.BI " int " target_fd ","
-.BI " __u64 " data ","
-.BI " unsigned int " flags ");"
-.PP
-.BI "void io_uring_prep_msg_ring_fd_alloc(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " int " source_fd ","
-.BI " __u64 " data ","
-.BI " unsigned int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-.BR io_uring_prep_msg_ring_fd (3)
-prepares an SQE to send a direct file descriptor to another ring. The submission
-queue entry
-.I sqe
-is setup to use the file descriptor
-.IR fd ,
-which must identify a target io_uring context, to send the locally registered
-file descriptor with value
-.I source_fd
-to the destination ring into index
-.I target_fd
-and passing
-.I data
-as the user data in the target CQE with the request modifier flags set by
-.IR flags .
-Currently there are no valid flag modifiers, this field must contain
-.BR 0 .
-
-.BR io_uring_prep_msg_ring_fd_alloc (3)
-is similar to
-.BR io_uring_prep_msg_ring_fd (3) ,
-but doesn't specify a target index for the direct descriptor. Instead, this
-index is allocated in the target ring and returned in the CQE
-.IR res
-field.
-
-.SH RETURN VALUE
-None
-
-.SH ERRORS
-These are the errors that are reported in the CQE
-.I res
-field.
-.TP
-.B -ENOMEM
-The kernel was unable to allocate memory for the request.
-.TP
-.B -EINVAL
-One of the fields set in the SQE was invalid.
-.TP
-.B -EINVAL
-Target ring is identical to the source ring.
-.TP
-.B -EBADFD
-The descriptor passed in
-.I fd
-does not refer to an io_uring file descriptor, or the ring is in a disabled
-state.
-.TP
-.B -EOVERFLOW
-The kernel was unable to fill a CQE on the target ring. This can happen if
-the target CQ ring is in an overflow state and the kernel wasn't able to
-allocate memory for a new CQE entry.
-.TP
-.B -ENFILE
-The direct descriptor table in the target ring was full, no new descriptors
-could be successfully allocated.
diff --git a/src/liburing/man/io_uring_prep_msg_ring_fd_alloc.3 b/src/liburing/man/io_uring_prep_msg_ring_fd_alloc.3
deleted file mode 120000
index a3a7731f8c94..000000000000
--- a/src/liburing/man/io_uring_prep_msg_ring_fd_alloc.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_msg_ring_fd.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_multishot_accept.3 b/src/liburing/man/io_uring_prep_multishot_accept.3
deleted file mode 120000
index 0404bf59f71a..000000000000
--- a/src/liburing/man/io_uring_prep_multishot_accept.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_accept.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_multishot_accept_direct.3 b/src/liburing/man/io_uring_prep_multishot_accept_direct.3
deleted file mode 120000
index 0404bf59f71a..000000000000
--- a/src/liburing/man/io_uring_prep_multishot_accept_direct.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_accept.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_nop.3 b/src/liburing/man/io_uring_prep_nop.3
deleted file mode 100644
index 81853d776391..000000000000
--- a/src/liburing/man/io_uring_prep_nop.3
+++ /dev/null
@@ -1,28 +0,0 @@
-.\" Copyright (C) 2022 Samuel Williams
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_nop 3 "October 20, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_nop \- prepare a nop request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_nop(struct io_uring_sqe *" sqe ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_nop (3)
-function prepares nop (no operation) request. The submission queue entry
-.I sqe
-does not require any additional setup.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-None
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
diff --git a/src/liburing/man/io_uring_prep_open.3 b/src/liburing/man/io_uring_prep_open.3
deleted file mode 120000
index 67f501e5ced1..000000000000
--- a/src/liburing/man/io_uring_prep_open.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_openat.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_open_direct.3 b/src/liburing/man/io_uring_prep_open_direct.3
deleted file mode 120000
index 67f501e5ced1..000000000000
--- a/src/liburing/man/io_uring_prep_open_direct.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_openat.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_openat.3 b/src/liburing/man/io_uring_prep_openat.3
deleted file mode 100644
index 071a9f832e94..000000000000
--- a/src/liburing/man/io_uring_prep_openat.3
+++ /dev/null
@@ -1,138 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_openat 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_openat \- prepare an openat request
-.SH SYNOPSIS
-.nf
-.B #include <sys/types.h>
-.B #include <sys/stat.h>
-.B #include <fcntl.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_open(struct io_uring_sqe *" sqe ","
-.BI " const char *" path ","
-.BI " int " flags ","
-.BI " mode_t " mode ");"
-.PP
-.BI "void io_uring_prep_open_direct(struct io_uring_sqe *" sqe ","
-.BI " const char *" path ","
-.BI " int " flags ","
-.BI " mode_t " mode ","
-.BI " unsigned " file_index ");"
-.PP
-.BI "void io_uring_prep_openat(struct io_uring_sqe *" sqe ","
-.BI " int " dfd ","
-.BI " const char *" path ","
-.BI " int " flags ","
-.BI " mode_t " mode ");"
-.PP
-.BI "void io_uring_prep_openat_direct(struct io_uring_sqe *" sqe ","
-.BI " int " dfd ","
-.BI " const char *" path ","
-.BI " int " flags ","
-.BI " mode_t " mode ","
-.BI " unsigned " file_index ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_openat (3)
-function prepares an openat request. The submission queue entry
-.I sqe
-is setup to use the directory file descriptor
-.I dfd
-to start opening a file described by
-.I path
-and using the open flags in
-.I flags
-and using the file mode bits specified in
-.IR mode .
-Similarly
-.BR io_uring_prep_open (3)
-prepares an open request.
-
-If the direct variant is used, the application must first have registered
-a file table using
-.BR io_uring_register_files (3)
-of the appropriate size. Once registered, a direct accept request may use any
-entry in that table and is specified in
-.I file_index
-, as long as it is within the size of the registered table.
-If a specified entry already contains a file, the file will first be removed
-from the table and closed. It's consistent with the behavior of updating an
-existing file with
-.BR io_uring_register_files_update (3).
-
-If
-.B IORING_FILE_INDEX_ALLOC
-is used as the
-.I file_index
-for a direct open, then io_uring will allocate a free direct descriptor in
-the existing table. The allocated descriptor is returned in the CQE
-.I res
-field just like it would be for a non-direct open request. If no more entries
-are available in the direct descriptor table,
-.B -ENFILE
-is returned instead.
-
-Direct descriptors are io_uring private file descriptors. They
-avoid some of the overhead associated with thread shared file tables, and
-can be used in any subsequent io_uring request that takes a file descriptor. To do so,
-.B IOSQE_FIXED_FILE
-must be set in the SQE
-.I flags
-member, and the SQE
-.I fd
-field should use the direct descriptor value rather than the regular file
-descriptor. Direct descriptors are managed like registered files.
-
-The directory file descriptor
-.I dfd
-is always a regular file descriptor.
-
-Note that old kernels don't check the SQE
-.I file_index
-field, which is not a problem for liburing helpers, but users of the raw
-io_uring interface need to zero SQEs to avoid unexpected behavior.
-
-These functions prepare an async
-.BR openat (2)
-or
-.BR open (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_register (2),
-.BR openat (2)
diff --git a/src/liburing/man/io_uring_prep_openat2.3 b/src/liburing/man/io_uring_prep_openat2.3
deleted file mode 100644
index 88b1c90a6a63..000000000000
--- a/src/liburing/man/io_uring_prep_openat2.3
+++ /dev/null
@@ -1,119 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_openat2 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_openat2 \- prepare an openat2 request
-.SH SYNOPSIS
-.nf
-.B #include <sys/types.h>
-.B #include <sys/stat.h>
-.B #include <fcntl.h>
-.B #include <linux/openat2.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_openat2(struct io_uring_sqe *" sqe ","
-.BI " int " dfd ","
-.BI " const char *" path ","
-.BI " struct open_how *" how ");"
-.PP
-.BI "void io_uring_prep_openat2_direct(struct io_uring_sqe *" sqe ","
-.BI " int " dfd ","
-.BI " const char *" path ","
-.BI " struct open_how *" how ","
-.BI " unsigned " file_index ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_openat2 (3)
-function prepares an openat2 request. The submission queue entry
-.I sqe
-is setup to use the directory file descriptor
-.I dfd
-to start opening a file described by
-.I path
-and using the instructions on how to open the file given in
-.IR how .
-
-If the direct variant is used, the application must first have registered
-a file table using
-.BR io_uring_register_files (3)
-of the appropriate size. Once registered, a direct request may use any
-entry in that table and is specified in
-.I file_index
-, as long as it is within the size of the registered table.
-If the specified entry already contains a file, the file will first be removed
-from the table and closed. It's consistent with the behavior of updating an
-existing file with
-.BR io_uring_register_files_update (3).
-
-If
-.B IORING_FILE_INDEX_ALLOC
-is used as the
-.I file_index
-for a direct open, then io_uring will allocate a free direct descriptor in
-the existing table. The allocated descriptor is returned in the CQE
-.I res
-field just like it would be for a non-direct open request. If no more entries
-are available in the direct descriptor table,
-.B -ENFILE
-is returned instead.
-
-Direct descriptors are io_uring private file descriptors. They
-avoid some of the overhead associated with thread shared file tables, and
-can be used in any subsequent io_uring request that takes a file descriptor. To do so,
-.B IOSQE_FIXED_FILE
-must be set in the SQE
-.I flags
-member, and the SQE
-.I fd
-field should use the direct descriptor value rather than the regular file
-descriptor. Direct descriptors are managed like registered files.
-
-The directory file descriptor
-.I dfd
-is always a regular file descriptor.
-
-Note that old kernels don't check the SQE
-.I file_index
-field, which is not a problem for liburing helpers, but users of the raw
-io_uring interface need to zero SQEs to avoid unexpected behavior.
-
-These functions prepare an async
-.BR openat2 (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_register (2),
-.BR openat2 (2)
diff --git a/src/liburing/man/io_uring_prep_openat2_direct.3 b/src/liburing/man/io_uring_prep_openat2_direct.3
deleted file mode 120000
index 2c0e6c9c3de4..000000000000
--- a/src/liburing/man/io_uring_prep_openat2_direct.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_openat2.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_openat_direct.3 b/src/liburing/man/io_uring_prep_openat_direct.3
deleted file mode 120000
index 67f501e5ced1..000000000000
--- a/src/liburing/man/io_uring_prep_openat_direct.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_openat.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_poll_add.3 b/src/liburing/man/io_uring_prep_poll_add.3
deleted file mode 100644
index 82539b9aef68..000000000000
--- a/src/liburing/man/io_uring_prep_poll_add.3
+++ /dev/null
@@ -1,72 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_poll_add 3 "March 12, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_poll_add \- prepare a poll request
-.SH SYNOPSIS
-.nf
-.B #include <poll.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_poll_add(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " unsigned " poll_mask ");"
-.PP
-.BI "void io_uring_prep_poll_multishot(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " unsigned " poll_mask ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_poll_add (3)
-function prepares a poll request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I fd
-that should get polled, with the events desired specified in the
-.I poll_mask
-argument.
-
-The default behavior is a single-shot poll request. When the specified event
-has triggered, a completion CQE is posted and no more events will be generated
-by the poll request.
-.BR io_uring_prep_poll_multishot (3)
-behaves identically in terms of events, but it persists across notifications
-and will repeatedly post notifications for the same registration. A CQE
-posted from a multishot poll request will have
-.B IORING_CQE_F_MORE
-set in the CQE
-.I flags
-member, indicating that the application should expect more completions from
-this request. If the multishot poll request gets terminated or experiences
-an error, this flag will not be set in the CQE. If this happens, the application
-should not expect further CQEs from the original request and must reissue a
-new one if it still wishes to get notifications on this file descriptor.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation, which is a bitmask of the
-events notified. See the
-.BR poll (2)
-man page for details. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR poll (2),
-.BR epoll_ctl (3)
diff --git a/src/liburing/man/io_uring_prep_poll_multishot.3 b/src/liburing/man/io_uring_prep_poll_multishot.3
deleted file mode 120000
index ac8fb8fdb468..000000000000
--- a/src/liburing/man/io_uring_prep_poll_multishot.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_poll_add.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_poll_remove.3 b/src/liburing/man/io_uring_prep_poll_remove.3
deleted file mode 100644
index b6f4b2637240..000000000000
--- a/src/liburing/man/io_uring_prep_poll_remove.3
+++ /dev/null
@@ -1,55 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_poll_remove 3 "March 12, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_poll_remove \- prepare a poll deletion request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_poll_remove(struct io_uring_sqe *" sqe ","
-.BI " __u64 " user_data ");"
-.BI "
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_poll_remove (3)
-function prepares a poll removal request. The submission queue entry
-.I sqe
-is setup to remove a poll request identified by
-.I user_data
-
-Works like
-.BR io_uring_prep_cancel (3)
-except only looks for poll requests. Apart from that, behavior is identical.
-See that man page for specific details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-These are the errors that are reported in the CQE
-.I res
-field. On success,
-.B 0
-is returned.
-.TP
-.B -ENOENT
-The request identified by
-.I user_data
-could not be located. This could be because it completed before the cancelation
-request was issued, or if an invalid identifier is used.
-.TP
-.B -EINVAL
-One of the fields set in the SQE was invalid.
-.TP
-.B -EALREADY
-The execution state of the request has progressed far enough that cancelation
-is no longer possible. This should normally mean that it will complete shortly,
-either successfully, or interrupted due to the cancelation.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_prep_cancel (3)
diff --git a/src/liburing/man/io_uring_prep_poll_update.3 b/src/liburing/man/io_uring_prep_poll_update.3
deleted file mode 100644
index 41cf7766a864..000000000000
--- a/src/liburing/man/io_uring_prep_poll_update.3
+++ /dev/null
@@ -1,101 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_poll_update 3 "March 12, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_poll_update \- update an existing poll request
-.SH SYNOPSIS
-.nf
-.B #include <poll.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_poll_update(struct io_uring_sqe *" sqe ","
-.BI " __u64 " old_user_data ","
-.BI " __u64 " new_user_data ","
-.BI " unsigned " poll_mask ","
-.BI " unsigned " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_poll_update (3)
-function prepares a poll update request. The submission queue entry
-.I sqe
-is setup to update a poll request identified by
-.IR old_user_data ,
-replacing it with the
-.I new_user_data
-information. The
-.I poll_mask
-arguments contains the new mask to use for the poll request, and
-.I flags
-argument contains modifier flags telling io_uring what fields to update.
-
-The
-.I flags
-modifier flags is a bitmask and may contain and OR'ed mask of:
-.TP
-.B IORING_POLL_UPDATE_EVENTS
-If set, the poll update request will replace the existing events being waited
-for with the ones specified in the
-.I poll_mask
-argument to the function. Note that only the lower 16 bits of events can
-be updated. This includes things like
-.B EPOLLIN
-and
-.B EPOLLOUT .
-Higher order masks/settings are included as internal state, and cannot be
-modified. That includes settings like
-.B EPOLLONESHOT ,
-.B EPOLLEXCLUSIVE ,
-and
-.B EPOLLET .
-If an application wishes to modify these, it must cancel/remove the existing
-poll request and arm a new one.
-.TP
-.B IORING_POLL_UPDATE_USER_DATA
-If set, the poll update request will update the existing user_data of the
-request with the value passed in as the
-.I new_user_data
-argument.
-.TP
-.B IORING_POLL_ADD_MULTI
-If set, this will change the poll request from a singleshot to a multishot
-request. This must be used along with
-.B IORING_POLL_UPDATE_EVENTS
-as the event field must be updated to enable multishot.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-These are the errors that are reported in the CQE
-.I res
-field. On success,
-.B 0
-is returned.
-.TP
-.B -ENOENT
-The request identified by
-.I user_data
-could not be located. This could be because it completed before the cancelation
-request was issued, or if an invalid identifier is used.
-.TP
-.B -EINVAL
-One of the fields set in the SQE was invalid.
-.TP
-.B -EALREADY
-The execution state of the request has progressed far enough that cancelation
-is no longer possible. This should normally mean that it will complete shortly,
-either successfully, or interrupted due to the cancelation.
-.TP
-.B -ECANCELED
-.B IORING_POLL_UPDATE_EVENTS
-was set and an error occurred re-arming the poll request with the new mask.
-The original poll request is terminated if this happens, and that termination
-CQE will contain the reason for the error re-arming.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_prep_poll_add (3),
-.BR io_uring_prep_poll_multishot (3)
diff --git a/src/liburing/man/io_uring_prep_provide_buffers.3 b/src/liburing/man/io_uring_prep_provide_buffers.3
deleted file mode 100644
index ae51c1dc8688..000000000000
--- a/src/liburing/man/io_uring_prep_provide_buffers.3
+++ /dev/null
@@ -1,140 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_provide_buffers 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_provide_buffers \- prepare a provide buffers request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_provide_buffers(struct io_uring_sqe *" sqe ","
-.BI " void *" addr ","
-.BI " int " len ","
-.BI " int " nr ","
-.BI " int " bgid ","
-.BI " int " bid ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_provide_buffers (3)
-function prepares a request for providing the kernel with buffers. The
-submission queue entry
-.I sqe
-is setup to consume
-.I nr
-number of
-.I len
-sized buffers starting at
-.I addr
-and identified by the buffer group ID of
-.I bgid
-and numbered sequentially starting at
-.IR bid .
-
-This function sets up a request to provide buffers to the io_uring context
-that can be used by read or receive operations. This is done by filling in
-the SQE
-.I buf_group
-field and setting
-.B IOSQE_BUFFER_SELECT
-in the SQE
-.I flags
-member. If buffer selection is used for a request, no buffer should be provided
-in the address field. Instead, the group ID is set to match one that was
-previously provided to the kernel. The kernel will then select a buffer from
-this group for the IO operation. On successful completion of the IO request,
-the CQE
-.I flags
-field will have
-.B IORING_CQE_F_BUFFER
-set and the selected buffer ID will be indicated by the upper 16-bits of the
-.I flags
-field.
-
-Different buffer group IDs can be used by the application to have different
-sizes or types of buffers available. Once a buffer has been consumed for an
-operation, it is no longer known to io_uring. It must be re-provided if so
-desired or freed by the application if no longer needed.
-
-The buffer IDs are internally tracked from
-.I bid
-and sequentially ascending from that value. If
-.B 16
-buffers are provided and start with an initial
-.I bid
-of 0, then the buffer IDs will range from
-.BR 0..15 .
-The application must be aware of this to make sense of the buffer ID passed
-back in the CQE.
-
-Buffer IDs always range from
-.B 0
-to
-.B 65535 ,
-as there are only 16-bits available in the CQE to pass them back. This range
-is independent of how the buffer group initially got created. Attempting to
-add buffer IDs larger than that, or buffer IDs that will wrap when cast to
-a 16-bit value, will cause the request to fail with
-.B -E2BIG
-or
-.B -EINVAL .
-
-Not all requests support buffer selection, as it only really makes sense for
-requests that receive data from the kernel rather than write or provide data.
-Currently, this mode of operation is supported for any file read or socket
-receive request. Attempting to use
-.B IOSQE_BUFFER_SELECT
-with a command that doesn't support it will result in a CQE
-.I res
-error of
-.BR -EINVAL .
-Buffer selection will work with operations that take a
-.B struct iovec
-as its data destination, but only if 1 iovec is provided.
-.
-.SH RETURN VALUE
-None
-.SH ERRORS
-These are the errors that are reported in the CQE
-.I res
-field. On success,
-.I res
-will contain
-.B 0
-or the number of successfully provided buffers.
-.TP
-.B -ENOMEM
-The kernel was unable to allocate memory for the request.
-.TP
-.B -EINVAL
-One of the fields set in the SQE was invalid.
-.TP
-.B -E2BIG
-The number of buffers provided was too big, or the
-.I bid
-was too big. A max value of
-.B USHRT_MAX
-buffers can be specified.
-.TP
-.B -EFAULT
-Some of the user memory given was invalid for the application.
-.TP
-.B -EOVERFLOW
-The product of
-.I len
-and
-.I nr
-exceed the valid amount or overflowed, or the sum of
-.I addr
-and the length of buffers overflowed.
-.TP
-.B -EBUSY
-Attempt to update a slot that is already used.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_register (2),
-.BR io_uring_prep_remove_buffers (3)
diff --git a/src/liburing/man/io_uring_prep_read.3 b/src/liburing/man/io_uring_prep_read.3
deleted file mode 100644
index a7636087013b..000000000000
--- a/src/liburing/man/io_uring_prep_read.3
+++ /dev/null
@@ -1,69 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_read 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_prep_read \- prepare I/O read request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_read(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " void *" buf ","
-.BI " unsigned " nbytes ","
-.BI " __u64 " offset ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_read (3)
-prepares an IO read request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I fd
-to start reading
-.I nbytes
-into the buffer
-.I buf
-at the specified
-.IR offset .
-
-On files that support seeking, if the offset is set to
-.BR -1 ,
-the read operation commences at the file offset, and the file offset is
-incremented by the number of bytes read. See
-.BR read (2)
-for more details. Note that for an async API, reading and updating the
-current file offset may result in unpredictable behavior, unless access
-to the file is serialized. It is not encouraged to use this feature, if it's
-possible to provide the desired IO offset from the application or library.
-
-On files that are not capable of seeking, the offset must be 0 or -1.
-
-After the read has been prepared it can be submitted with one of the submit
-functions.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_prep_readv (3),
-.BR io_uring_prep_readv2 (3),
-.BR io_uring_submit (3)
diff --git a/src/liburing/man/io_uring_prep_read_fixed.3 b/src/liburing/man/io_uring_prep_read_fixed.3
deleted file mode 100644
index 5b7c1c6653b6..000000000000
--- a/src/liburing/man/io_uring_prep_read_fixed.3
+++ /dev/null
@@ -1,72 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_read_fixed 3 "February 13, 2022" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_prep_read_fixed \- prepare I/O read request with registered buffer
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_read_fixed(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " void *" buf ","
-.BI " unsigned " nbytes ","
-.BI " __u64 " offset ","
-.BI " int " buf_index ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_read_fixed (3)
-prepares an IO read request with a previously registered IO buffer. The
-submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I fd
-to start reading
-.I nbytes
-into the buffer
-.I buf
-at the specified
-.IR offset ,
-and with the buffer matching the registered index of
-.IR buf_index .
-
-This works just like
-.BR io_uring_prep_read (3)
-except it requires the use of buffers that have been registered with
-.BR io_uring_register_buffers (3).
-The
-.I buf
-and
-.I nbytes
-arguments must fall within a region specified by
-.I buf_index
-in the previously registered buffer. The buffer need not be aligned with
-the start of the registered buffer.
-
-After the read has been prepared it can be submitted with one of the submit
-functions.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_prep_read (3),
-.BR io_uring_register_buffers (3)
diff --git a/src/liburing/man/io_uring_prep_read_multishot.3 b/src/liburing/man/io_uring_prep_read_multishot.3
deleted file mode 100644
index 29953579b061..000000000000
--- a/src/liburing/man/io_uring_prep_read_multishot.3
+++ /dev/null
@@ -1,100 +0,0 @@
-.\" Copyright (C) 2023 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_read_multishot 3 "September 12, 2023" "liburing-2.5" "liburing Manual"
-.SH NAME
-io_uring_prep_read_multishot \- prepare I/O read multishot request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_read_multishot(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " unsigned " nbytes ","
-.BI " __u64 " offset ","
-.BI " int " buf_group ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_read_multishot (3)
-helper prepares an IO read multishot request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I fd
-to start reading
-into a buffer from the provided buffer group with ID
-.I buf_group
-at the specified
-.IR offset .
-
-.I nbytes
-must be set to zero, as the size read will be given by the size of the
-buffers in the indicated buffer group IO.
-
-On files that are not capable of seeking, the offset must be 0 or -1.
-
-If
-.I nbytes
-exceeds the size of the buffers in the specified buffer group, or if
-.I nbytes
-is
-.B 0 ,
-then the size of the buffer in that group will be used for the transfer.
-
-A multishot read request will repeatedly trigger a completion event
-whenever data is available to read from the file. Because of that,
-this type of request can only be used with a file type that is pollable.
-Examples of that include pipes, tun devices, etc. If used with a regular
-file, or a wrong file type in general, the request will fail with
-.B -EBADFD
-in the CQE
-.I res
-field.
-
-Since multishot requests repeatedly trigger completion events as data
-arrives, it must be used with provided buffers. With provided buffers, the
-application provides buffers to io_uring upfront, and then the kernel picks
-a buffer from the specified group in
-.I buf_group
-when the request is ready to transfer data.
-
-A multishot request will persist as long as no errors are encountered
-doing handling of the request. For each CQE posted on behalf of this request,
-the CQE
-.I flags
-will have
-.B IORING_CQE_F_MORE
-set if the application should expect more completions from this request.
-If this flag isn't set, then that signifies termination of the multishot
-read request.
-
-After the read has been prepared it can be submitted with one of the submit
-functions.
-
-Available since 6.7.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_prep_read (3),
-.BR io_uring_buf_ring_init (3)
-.BR io_uring_buf_ring_add (3),
-.BR io_uring_submit (3)
diff --git a/src/liburing/man/io_uring_prep_readv.3 b/src/liburing/man/io_uring_prep_readv.3
deleted file mode 100644
index 81d8fad4f366..000000000000
--- a/src/liburing/man/io_uring_prep_readv.3
+++ /dev/null
@@ -1,85 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_readv 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_prep_readv \- prepare vector I/O read request
-.SH SYNOPSIS
-.nf
-.B #include <sys/uio.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_readv(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " const struct iovec *" iovecs ","
-.BI " unsigned " nr_vecs ","
-.BI " __u64 " offset ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_readv (3)
-prepares a vectored IO read request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I fd
-to start reading
-.I nr_vecs
-into the
-.I iovecs
-array at the specified
-.IR offset .
-
-On files that support seeking, if the offset is set to
-.BR -1 ,
-the read operation commences at the file offset, and the file offset is
-incremented by the number of bytes read. See
-.BR read (2)
-for more details. Note that for an async API, reading and updating the
-current file offset may result in unpredictable behavior, unless access
-to the file is serialized. It is not encouraged to use this feature, if it's
-possible to provide the desired IO offset from the application or library.
-
-On files that are not capable of seeking, the offset must be 0 or -1.
-
-After the read has been prepared it can be submitted with one of the submit
-functions.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-Unless an application explicitly needs to pass in more than one iovec, it
-is more efficient to use
-.BR io_uring_prep_read (3)
-rather than this function, as no state has to be maintained for a
-non-vectored IO request.
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_prep_read (3),
-.BR io_uring_prep_readv2 (3),
-.BR io_uring_submit (3)
diff --git a/src/liburing/man/io_uring_prep_readv2.3 b/src/liburing/man/io_uring_prep_readv2.3
deleted file mode 100644
index 842b787c392d..000000000000
--- a/src/liburing/man/io_uring_prep_readv2.3
+++ /dev/null
@@ -1,111 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_readv2 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_prep_readv2 \- prepare vector I/O read request with flags
-.SH SYNOPSIS
-.nf
-.B #include <sys/uio.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_readv2(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " const struct iovec *" iovecs ","
-.BI " unsigned " nr_vecs ","
-.BI " __u64 " offset ","
-.BI " int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_readv2 (3)
-prepares a vectored IO read request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I fd
-to start reading
-.I nr_vecs
-into the
-.I iovecs
-array at the specified
-.IR offset .
-The behavior of the function can be controlled with the
-.I flags
-parameter.
-
-Supported values for
-.I flags
-are:
-.TP
-.B RWF_HIPRI
-High priority request, poll if possible
-.TP
-.B RWF_DSYNC
-per-IO O_DSYNC
-.TP
-.B RWF_SYNC
-per-IO O_SYNC
-.TP
-.B RWF_NOWAIT
-per-IO, return
-.B -EAGAIN
-if operation would block
-.TP
-.B RWF_APPEND
-per-IO O_APPEND
-
-.P
-On files that support seeking, if the offset is set to
-.BR -1 ,
-the read operation commences at the file offset, and the file offset is
-incremented by the number of bytes read. See
-.BR read (2)
-for more details. Note that for an async API, reading and updating the
-current file offset may result in unpredictable behavior, unless access
-to the file is serialized. It is not encouraged to use this feature, if it's
-possible to provide the desired IO offset from the application or library.
-
-On files that are not capable of seeking, the offset must be 0 or -1.
-
-After the read has been prepared, it can be submitted with one of the submit
-functions.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-Unless an application explicitly needs to pass in more than one iovec, it
-is more efficient to use
-.BR io_uring_prep_read (3)
-rather than this function, as no state has to be maintained for a
-non-vectored IO request.
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_prep_read (3),
-.BR io_uring_prep_readv (3),
-.BR io_uring_submit (3)
diff --git a/src/liburing/man/io_uring_prep_recv.3 b/src/liburing/man/io_uring_prep_recv.3
deleted file mode 100644
index 34b4ce8f8442..000000000000
--- a/src/liburing/man/io_uring_prep_recv.3
+++ /dev/null
@@ -1,139 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_recv 3 "March 12, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_recv \- prepare a recv request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_recv(struct io_uring_sqe *" sqe ","
-.BI " int " sockfd ","
-.BI " void *" buf ","
-.BI " size_t " len ","
-.BI " int " flags ");"
-.PP
-.BI "void io_uring_prep_recv_multishot(struct io_uring_sqe *" sqe ","
-.BI " int " sockfd ","
-.BI " void *" buf ","
-.BI " size_t " len ","
-.BI " int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_recv (3)
-function prepares a recv request. The submission
-queue entry
-.I sqe
-is setup to use the file descriptor
-.I sockfd
-to start receiving the data into the destination buffer
-.I buf
-of size
-.I len
-and with modifier flags
-.IR flags .
-
-This function prepares an async
-.BR recv (2)
-request. See that man page for details on the arguments specified to this
-prep helper.
-
-The multishot version allows the application to issue a single receive request,
-which repeatedly posts a CQE when data is available. It requires length to
-be 0, the
-.B IOSQE_BUFFER_SELECT
-flag to be set and no
-.B MSG_WAITALL
-flag to be set.
-Therefore each CQE will take a buffer out of a provided buffer pool for receiving.
-The application should check the flags of each CQE, regardless of its result.
-If a posted CQE does not have the
-.B IORING_CQE_F_MORE
-flag set, then the multishot receive is done and the application must issue a
-new request if it still wishes to receive data from the socket.
-Multishot variants are available since kernel 6.0.
-
-
-After calling this function, additional io_uring internal modifier flags
-may be set in the SQE
-.I ioprio
-field. The following flags are supported:
-.TP
-.B IORING_RECVSEND_POLL_FIRST
-If set, io_uring will assume the socket is currently empty and attempting to
-receive data will be unsuccessful. For this case, io_uring will arm internal
-poll and trigger a receive of the data when the socket has data to be read.
-This initial receive attempt can be wasteful for the case where the socket
-is expected to be empty, setting this flag will bypass the initial receive
-attempt and go straight to arming poll. If poll does indicate that data is
-ready to be received, the operation will proceed.
-
-Can be used with the CQE
-.B IORING_CQE_F_SOCK_NONEMPTY
-flag, which io_uring will set on CQEs after a
-.BR recv (2)
-or
-.BR recvmsg (2)
-operation. If set, the socket still had data to be read after the operation
-completed. Both these flags are available since 5.19.
-
-.TP
-.B IORING_RECVSEND_BUNDLE
-If set and provided buffers are used with
-.B IOSQE_BUFFER_SELECT ,
-the receive operation will attempt to fill multiple buffers with rather than
-just pick a single buffer to fill. To receive multiple buffers in a single
-receive, the buffer group ID set in the SQE must be of the ring provided type.
-If set, the CQE
-.I res
-field indicates the total number of bytes received, and the buffer ID returned
-in the CQE
-.I flags
-field indicates the first buffer in the receive operation. The application must
-process the indicated initial buffer ID and until all
-.I res
-bytes have been seen to know which is the last buffer in the receive operation.
-The buffers consumed will be contiguous from the initial buffer, in the order
-in which they appear in the buffer ring. The CQE struct does not contain
-the position of the buffer in the buffer ring, therefore in order to identify
-buffers contained by the bundle, it is advised to maintain the cached head
-index per buffer ring. This uint16_t index represents the position of the next
-buffer to be consumed within the ring. Upon completion of a receive operation,
-the cached head index should be incremented accordingly.
-Receiving in bundles can improve performance when more than one chunk of
-data is available to receive,
-by eliminating redundant round trips through the networking stack. Receive
-bundles may be used by both single shot and multishot receive operations. Note
-that, internally, bundles rely on the networking stack passing back how much
-data is left in the socket after the initial receive. This means that the
-initial receive may contain less buffers than what is available, with the
-followup receive(s) containing more buffers. Available since 6.10.
-.P
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_buf_ring_init (3),
-.BR io_uring_buf_ring_add (3),
-.BR recv (2)
diff --git a/src/liburing/man/io_uring_prep_recv_multishot.3 b/src/liburing/man/io_uring_prep_recv_multishot.3
deleted file mode 120000
index 71fe277d6aeb..000000000000
--- a/src/liburing/man/io_uring_prep_recv_multishot.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_recv.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_recvmsg.3 b/src/liburing/man/io_uring_prep_recvmsg.3
deleted file mode 100644
index aaa39f77d184..000000000000
--- a/src/liburing/man/io_uring_prep_recvmsg.3
+++ /dev/null
@@ -1,126 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_recvmsg 3 "March 12, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_recvmsg \- prepare a recvmsg request
-.SH SYNOPSIS
-.nf
-.B #include <sys/types.h>
-.B #include <sys/socket.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_recvmsg(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " struct msghdr *" msg ","
-.BI " unsigned " flags ");"
-.PP
-.BI "void io_uring_prep_recvmsg_multishot(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " struct msghdr *" msg ","
-.BI " unsigned " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_recvmsg (3)
-function prepares a recvmsg request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I fd
-to start receiving the data indicated by
-.I msg
-with the
-.BR recvmsg (2)
-defined flags in the
-.I flags
-argument.
-
-This function prepares an async
-.BR recvmsg (2)
-request. See that man page for details on the arguments specified to this
-prep helper.
-
-The multishot version allows the application to issue a single receive request,
-which repeatedly posts a CQE when data is available. It requires the
-.B IOSQE_BUFFER_SELECT
-flag to be set and no
-.B MSG_WAITALL
-flag to be set.
-Therefore each CQE will take a buffer out of a provided buffer pool for receiving.
-The application should check the flags of each CQE, regardless of its result.
-If a posted CQE does not have the
-.B IORING_CQE_F_MORE
-flag set, then the multishot receive is done and the application must issue a
-new request if it still wishes to receive data from the socket.
-
-Unlike
-.BR recvmsg (2),
-multishot recvmsg will prepend a
-.I struct io_uring_recvmsg_out
-which describes the layout of the rest of the buffer in combination with the initial
-.I struct msghdr
-submitted with the request. See
-.BR io_uring_recvmsg_out (3)
-for more information on accessing the data.
-
-Multishot variants are available since kernel 6.0.
-
-After calling this function, additional io_uring internal modifier flags
-may be set in the SQE
-.I ioprio
-field. The following flags are supported:
-.TP
-.B IORING_RECVSEND_POLL_FIRST
-If set, io_uring will assume the socket is currently empty and attempting to
-receive data will be unsuccessful. For this case, io_uring will arm internal
-poll and trigger a receive of the data when the socket has data to be read.
-This initial receive attempt can be wasteful for the case where the socket
-is expected to be empty, setting this flag will bypass the initial receive
-attempt and go straight to arming poll. If poll does indicate that data is
-ready to be received, the operation will proceed.
-
-Can be used with the CQE
-.B IORING_CQE_F_SOCK_NONEMPTY
-flag, which io_uring will set on CQEs after a
-.BR recv (2)
-or
-.BR recvmsg (2)
-operation. If set, the socket still had data to be read after the operation
-completed. Both these flags are available since 5.19.
-.P
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_buf_ring_init (3),
-.BR io_uring_buf_ring_add (3),
-.BR recvmsg (2)
diff --git a/src/liburing/man/io_uring_prep_recvmsg_multishot.3 b/src/liburing/man/io_uring_prep_recvmsg_multishot.3
deleted file mode 120000
index cd9566f2c2be..000000000000
--- a/src/liburing/man/io_uring_prep_recvmsg_multishot.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_recvmsg.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_remove_buffers.3 b/src/liburing/man/io_uring_prep_remove_buffers.3
deleted file mode 100644
index cf4f22640829..000000000000
--- a/src/liburing/man/io_uring_prep_remove_buffers.3
+++ /dev/null
@@ -1,52 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_remove_buffers 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_remove_buffers \- prepare a remove buffers request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_remove_buffers(struct io_uring_sqe *" sqe ","
-.BI " int " nr ","
-.BI " int " bgid ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_remove_buffers (3)
-function prepares a request for removing previously supplied buffers. The
-submission queue entry
-.I sqe
-is setup to remove
-.I nr
-number of buffers from the buffer group ID indicated by
-.IR bgid .
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-These are the errors that are reported in the CQE
-.I res
-field. On success,
-.I res
-will contain the number of successfully removed buffers. On error,
-the following errors can occur.
-.TP
-.B -ENOMEM
-The kernel was unable to allocate memory for the request.
-.TP
-.B -EINVAL
-One of the fields set in the SQE was invalid.
-.TP
-.B -ENOENT
-No buffers exist at the specified
-.I bgid
-buffer group ID.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_register (2),
-.BR io_uring_prep_provide_buffers (3)
diff --git a/src/liburing/man/io_uring_prep_rename.3 b/src/liburing/man/io_uring_prep_rename.3
deleted file mode 120000
index 785b55eb0d63..000000000000
--- a/src/liburing/man/io_uring_prep_rename.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_renameat.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_renameat.3 b/src/liburing/man/io_uring_prep_renameat.3
deleted file mode 100644
index 1ecdc2abbda2..000000000000
--- a/src/liburing/man/io_uring_prep_renameat.3
+++ /dev/null
@@ -1,95 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_renameat 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_renameat \- prepare a renameat request
-.SH SYNOPSIS
-.nf
-.B #include <fcntl.h>
-.B #include <stdio.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_renameat(struct io_uring_sqe *" sqe ","
-.BI " int " olddirfd ","
-.BI " const char *" oldpath ","
-.BI " int " newdirfd ","
-.BI " const char *" newpath ","
-.BI " unsigned int " flags ");"
-.PP
-.BI "void io_uring_prep_rename(struct io_uring_sqe *" sqe ","
-.BI " const char *" oldpath ","
-.BI " const char *" newpath ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_renameat (3)
-function prepares a renameat request. The submission queue entry
-.I sqe
-is setup to use the old directory file descriptor pointed to by
-.I olddirfd
-and old path pointed to by
-.I oldpath
-with the new directory file descriptor pointed to by
-.I newdirfd
-and the new path pointed to by
-.I newpath
-and using the specified flags in
-.IR flags .
-
-The
-.BR io_uring_prep_rename (3)
-function prepares a rename request. The submission queue entry
-.I sqe
-is setup to use the old path pointed to by
-.I oldpath
-with the new path pointed to by
-.IR newpath ,
-both relative to the current working directory and using the specified flags in
-.IR flags .
-
-These functions prepare an async
-.BR renameat2 (2)
-or
-.BR rename (2)
-request. If
-.I flags
-is zero, then this call is similar to the
-.BR renameat (2)
-system call. See those man pages for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR renameat (2),
-.BR renameat2 (2),
-.BR rename (2)
diff --git a/src/liburing/man/io_uring_prep_send.3 b/src/liburing/man/io_uring_prep_send.3
deleted file mode 100644
index e61ea432cb75..000000000000
--- a/src/liburing/man/io_uring_prep_send.3
+++ /dev/null
@@ -1,146 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_send 3 "March 12, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_send \- prepare a send request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_send(struct io_uring_sqe *" sqe ","
-.BI " int " sockfd ","
-.BI " const void *" buf ","
-.BI " size_t " len ","
-.BI " int " flags ");"
-.PP
-.BI "void io_uring_prep_sendto(struct io_uring_sqe *" sqe ","
-.BI " int " sockfd ","
-.BI " const void *" buf ","
-.BI " size_t " len ","
-.BI " int " flags ","
-.BI " const struct sockaddr *" addr ","
-.BI " socklen_t " addrlen ");"
-.PP
-.BI "void io_uring_prep_send_bundle(struct io_uring_sqe *" sqe ","
-.BI " int " sockfd ","
-.BI " size_t " len ","
-.BI " int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_send (3)
-function prepares a send request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I sockfd
-to start sending the data from
-.I buf
-of size
-.I len
-bytes and with modifier flags
-.IR flags .
-
-Note that using
-.B IOSQE_IO_LINK
-with this request type requires the setting of
-.B MSG_WAITALL
-in the
-.IR flags
-argument, as a short send isn't a considered an error condition without
-that being set.
-
-This function prepares an async
-.BR send (2)
-request. See that man page for details.
-
-The
-.BR io_uring_prep_sendto (3)
-function prepares a sendto request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I sockfd
-to start sending the data from
-.I buf
-of size
-.I len
-bytes and with modifier flags
-.IR flags .
-The destination address is specified by
-.I addr
-and
-.I addrlen
-and must be a valid address for the socket type.
-
-This function prepares an async
-.BR sendto (2)
-request. See that man page for details.
-
-Both of the above send variants may be used with provided buffers, where rather
-than pass a buffer in directly with the request,
-.B IOSQE_BUFFER_SELECT
-is set in the SQE
-.I flags
-field, and additionally a buffer group ID is set in the SQE
-.I buf_group
-field. By using provided buffers with send requests, the application can
-prevent any kind of reordering of the outgoing data which can otherwise
-occur if the application has more than one send request inflight for a single
-socket. This provides better pipelining of data, where previously the app
-needed to manually serialize sends.
-
-The bundle version allows the application to issue a single send request,
-with a buffer group ID given in the SQE
-.I buf_group
-field, which keeps sending from that buffer group until it runs out of buffers.
-As with any other request using provided buffers,
-.B IOSQE_BUFFER_SELECT
-must also be set in the SQE
-.I flags
-before submission. Currently
-.I len
-must be given as
-.B 0
-otherwise the request will be errored with
-.B -EINVAL
-as the result code. Future versions may allow setting
-.I
-to limit the transfer size. A single CQE is posted for the send, with the result
-being how many bytes were sent, on success. When used with provided buffers,
-send or send bundle will contain the starting buffer group ID in the CQE
-.I flags
-field. The number of bytes sent starts from there, and will be in contiguous
-buffer IDs after that. Send bundle, and send with provided buffers in general,
-are available since kernel 6.10, and can be further identified by checking for
-the
-.B IORING_FEAT_SEND_BUF_SELECT
-flag returned in when using
-.BR io_uring_init_queue_params (3)
-to setup the ring.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_buf_ring_init (3),
-.BR io_uring_buf_ring_add (3),
-.BR send (2)
-.BR sendto (2)
diff --git a/src/liburing/man/io_uring_prep_send_bundle.3 b/src/liburing/man/io_uring_prep_send_bundle.3
deleted file mode 120000
index ba85e68453fe..000000000000
--- a/src/liburing/man/io_uring_prep_send_bundle.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_send.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_send_set_addr.3 b/src/liburing/man/io_uring_prep_send_set_addr.3
deleted file mode 100644
index 5adcdbc8e8b2..000000000000
--- a/src/liburing/man/io_uring_prep_send_set_addr.3
+++ /dev/null
@@ -1,38 +0,0 @@
-.\" Copyright (C) 2023 Rutvik Patel <heyrutvik@gmail.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_send_set_addr 3 "January 23, 2023" "liburing-2.4" "liburing Manual"
-.SH NAME
-io_uring_prep_send_set_addr \- set address details for send requests
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_send_set_addr(struct io_uring_sqe *" sqe ","
-.BI " const struct sockaddr *" dest_addr ","
-.BI " __u16 " addr_len ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_send_set_addr (3)
-function sets a socket destination address specified by
-.I dest_addr
-and its length using
-.I addr_len
-parameters. It can be used once
-.I sqe
-is prepared using any of the
-.BR send (2)
-io_uring helpers. See man pages of
-.BR io_uring_prep_send (3)
-or
-.BR io_uring_prep_send_zc (3).
-.SH RETURN VALUE
-None
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_prep_send (3),
-.BR io_uring_prep_send_zc (3),
-.BR send (2)
diff --git a/src/liburing/man/io_uring_prep_send_zc.3 b/src/liburing/man/io_uring_prep_send_zc.3
deleted file mode 100644
index f5ec5d298d46..000000000000
--- a/src/liburing/man/io_uring_prep_send_zc.3
+++ /dev/null
@@ -1,96 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_send_zc 3 "September 6, 2022" "liburing-2.3" "liburing Manual"
-.SH NAME
-io_uring_prep_send_zc \- prepare a zerocopy send request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_send_zc(struct io_uring_sqe *" sqe ","
-.BI " int " sockfd ","
-.BI " const void *" buf ","
-.BI " size_t " len ","
-.BI " int " flags ","
-.BI " unsigned " zc_flags ");"
-.PP
-.BI "void io_uring_prep_send_zc_fixed(struct io_uring_sqe *" sqe ","
-.BI " int " sockfd ","
-.BI " const void *" buf ","
-.BI " size_t " len ","
-.BI " int " flags ","
-.BI " unsigned " zc_flags ");"
-.BI " unsigned " buf_index ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_send_zc (3)
-function prepares a zerocopy send request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I sockfd
-to start sending the data from
-.I buf
-of size
-.I len
-bytes with send modifier flags
-.I flags
-and zerocopy modifier flags
-.IR zc_flags .
-
-The
-.BR io_uring_prep_send_zc_fixed (3)
-works just like
-.BR io_uring_prep_send_zc (3)
-except it requires the use of buffers that have been registered with
-.BR io_uring_register_buffers (3).
-The
-.I buf
-and
-.I len
-arguments must fall within a region specified by
-.I buf_index
-in the previously registered buffer. The buffer need not be aligned with the
-start of the registered buffer.
-
-Note that using
-.B IOSQE_IO_LINK
-with this request type requires the setting of
-.B MSG_WAITALL
-in the
-.I flags
-argument, as a short send isn't considered an error condition without
-that being set.
-
-These functions prepare an async zerocopy
-.BR send (2)
-request. See that man page for details. For details on the zerocopy nature
-of it, see
-.BR io_uring_enter (2) .
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_prep_send (3),
-.BR io_uring_enter (2),
-.BR send (2)
diff --git a/src/liburing/man/io_uring_prep_send_zc_fixed.3 b/src/liburing/man/io_uring_prep_send_zc_fixed.3
deleted file mode 120000
index c66c84d631cf..000000000000
--- a/src/liburing/man/io_uring_prep_send_zc_fixed.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_send_zc.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_sendmsg.3 b/src/liburing/man/io_uring_prep_sendmsg.3
deleted file mode 100644
index 7744a4cb5e73..000000000000
--- a/src/liburing/man/io_uring_prep_sendmsg.3
+++ /dev/null
@@ -1,91 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_sendmsg 3 "March 12, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_sendmsg \- prepare a sendmsg request
-.SH SYNOPSIS
-.nf
-.B #include <sys/types.h>
-.B #include <sys/socket.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_sendmsg(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " const struct msghdr *" msg ","
-.BI " unsigned " flags ");"
-.PP
-.BI "void io_uring_prep_sendmsg_zc(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " const struct msghdr *" msg ","
-.BI " unsigned " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_sendmsg (3)
-function prepares a sendmsg request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I fd
-to start sending the data indicated by
-.I msg
-with the
-.BR sendmsg (2)
-defined flags in the
-.I flags
-argument.
-
-The
-.BR io_uring_prep_sendmsg_zc (3)
-accepts the same parameters as
-.BR io_uring_prep_sendmsg (3)
-but prepares a zerocopy sendmsg request.
-
-Note that using
-.B IOSQE_IO_LINK
-with this request type requires the setting of
-.B MSG_WAITALL
-in the
-.I flags
-argument, as a short send isn't considered an error condition without
-that being set.
-
-This function prepares an async
-.BR sendmsg (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_buf_ring_init (3),
-.BR io_uring_buf_ring_add (3),
-.BR sendmsg (2)
diff --git a/src/liburing/man/io_uring_prep_sendmsg_zc.3 b/src/liburing/man/io_uring_prep_sendmsg_zc.3
deleted file mode 120000
index 47599fb0c167..000000000000
--- a/src/liburing/man/io_uring_prep_sendmsg_zc.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_sendmsg.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_sendto.3 b/src/liburing/man/io_uring_prep_sendto.3
deleted file mode 120000
index ba85e68453fe..000000000000
--- a/src/liburing/man/io_uring_prep_sendto.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_send.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_setxattr.3 b/src/liburing/man/io_uring_prep_setxattr.3
deleted file mode 100644
index 5ccff75262b7..000000000000
--- a/src/liburing/man/io_uring_prep_setxattr.3
+++ /dev/null
@@ -1,64 +0,0 @@
-.\" Copyright (C) 2023 Rutvik Patel <heyrutvik@gmail.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_setxattr 3 "January 23, 2023" "liburing-2.4" "liburing Manual"
-.SH NAME
-io_uring_prep_setxattr, io_uring_prep_fsetxattr \- prepare a request to set an
-extended attribute value
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_setxattr(struct io_uring_sqe *" sqe ","
-.BI " const char *" name ","
-.BI " const char *" value ","
-.BI " const char *" path ","
-.BI " int " flags ","
-.BI " unsigned int " len ");"
-.PP
-.BI "void io_uring_prep_fsetxattr(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " const char *" name ","
-.BI " const char *" value ","
-.BI " int " flags ","
-.BI " unsigned int " len ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_setxattr (3)
-function prepares a request to set an extended attribute value. The submission
-queue entry
-.I sqe
-is setup to set the
-.I value
-of the extended attribute identified by
-.I name
-and associated with the given
-.I path
-in the filesystem with modifier flags
-.IR flags .
-The
-.I len
-argument specifies the size (in bytes) of
-.IR value .
-
-.BR io_uring_prep_fsetxattr (3)
-is identical to
-.BR io_uring_prep_setxattr (3),
-only the extended attribute is set on the open file referred to by
-.I fd
-in place of
-.IR path .
-
-This function prepares an async
-.BR setxattr (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR setxattr (2)
diff --git a/src/liburing/man/io_uring_prep_shutdown.3 b/src/liburing/man/io_uring_prep_shutdown.3
deleted file mode 100644
index 9125e95f5cd1..000000000000
--- a/src/liburing/man/io_uring_prep_shutdown.3
+++ /dev/null
@@ -1,53 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_shutdown 3 "March 12, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_shutdown \- prepare a shutdown request
-.SH SYNOPSIS
-.nf
-.B #include <sys/socket.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_shutdown(struct io_uring_sqe *" sqe ","
-.BI " int " sockfd ","
-.BI " int " how ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_shutdown (3)
-function prepares a shutdown request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I sockfd
-that should be shutdown with the
-.I how
-argument.
-
-This function prepares an async
-.BR shutdown (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR shutdown (2)
diff --git a/src/liburing/man/io_uring_prep_socket.3 b/src/liburing/man/io_uring_prep_socket.3
deleted file mode 100644
index 77dba66be459..000000000000
--- a/src/liburing/man/io_uring_prep_socket.3
+++ /dev/null
@@ -1,118 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_socket 3 "May 27, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_socket \- prepare a socket creation request
-.SH SYNOPSIS
-.nf
-.B #include <sys/socket.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_socket(struct io_uring_sqe *" sqe ","
-.BI " int " domain ","
-.BI " int " type ","
-.BI " int " protocol ","
-.BI " unsigned int " flags ");"
-.PP
-.BI "void io_uring_prep_socket_direct(struct io_uring_sqe *" sqe ","
-.BI " int " domain ","
-.BI " int " type ","
-.BI " int " protocol ","
-.BI " unsigned int " file_index ","
-.BI " unsigned int " flags ");"
-.PP
-.BI "void io_uring_prep_socket_direct_alloc(struct io_uring_sqe *" sqe ","
-.BI " int " domain ","
-.BI " int " type ","
-.BI " int " protocol ","
-.BI " unsigned int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_socket (3)
-function prepares a socket creation request. The submission queue entry
-.I sqe
-is setup to use the communication domain defined by
-.I domain
-and use the communication type defined by
-.I type
-and the protocol set by
-.IR protocol .
-The
-.I flags
-argument are currently unused.
-
-The
-.BR io_uring_prep_socket_direct (3)
-helper works just like
-.BR io_uring_prep_socket (3),
-except it maps the socket to a direct descriptor rather than return a normal
-file descriptor. The
-.I file_index
-argument should be set to the slot that should be used for this socket.
-
-The
-.BR io_uring_prep_socket_direct_alloc (3)
-helper works just like
-.BR io_uring_prep_socket_direct (3),
-except it allocates a new direct descriptor rather than pass a free slot in. It
-is equivalent to using
-.BR io_uring_prep_socket_direct (3)
-with
-.B IORING_FILE_INDEX_ALLOC
-as the
-.I
-file_index .
-Upon completion, the
-.I res
-field of the CQE will return the direct slot that was allocated for the
-socket.
-
-If the direct variants are used, the application must first have registered
-a file table using
-.BR io_uring_register_files (3)
-of the appropriate size. Once registered, a direct socket request may use any
-entry in that table, as long as it is within the size of the registered table.
-If a specified entry already contains a file, the file will first be removed
-from the table and closed. It's consistent with the behavior of updating an
-existing file with
-.BR io_uring_register_files_update (3).
-
-For a direct descriptor socket request, the
-.I file_index
-argument can be set to
-.BR IORING_FILE_INDEX_ALLOC ,
-In this case a free entry in io_uring file table will
-be used automatically and the file index will be returned as CQE
-.IR res .
-.B -ENFILE
-is otherwise returned if there is no free entries in the io_uring file table.
-
-These functions prepare an async
-.BR socket (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR socket (2)
diff --git a/src/liburing/man/io_uring_prep_socket_direct.3 b/src/liburing/man/io_uring_prep_socket_direct.3
deleted file mode 120000
index 15d7b7f08e31..000000000000
--- a/src/liburing/man/io_uring_prep_socket_direct.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_socket.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_socket_direct_alloc.3 b/src/liburing/man/io_uring_prep_socket_direct_alloc.3
deleted file mode 120000
index 15d7b7f08e31..000000000000
--- a/src/liburing/man/io_uring_prep_socket_direct_alloc.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_socket.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_splice.3 b/src/liburing/man/io_uring_prep_splice.3
deleted file mode 100644
index 3d6e38f2bd3e..000000000000
--- a/src/liburing/man/io_uring_prep_splice.3
+++ /dev/null
@@ -1,120 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_splice 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_splice \- prepare an splice request
-.SH SYNOPSIS
-.nf
-.B #include <fcntl.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_splice(struct io_uring_sqe *" sqe ","
-.BI " int " fd_in ","
-.BI " int64_t " off_in ","
-.BI " int " fd_out ","
-.BI " int64_t " off_out ","
-.BI " unsigned int " nbytes ","
-.BI " unsigned int " splice_flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_splice (3)
-function prepares a splice request. The submission queue entry
-.I sqe
-is setup to use as input the file descriptor
-.I fd_in
-at offset
-.IR off_in ,
-splicing data to the file descriptor at
-.I fd_out
-and at offset
-.IR off_out .
-.I nbytes
-bytes of data should be spliced between the two descriptors.
-.I splice_flags
-are modifier flags for the operation. See
-.BR splice (2)
-for the generic splice flags.
-
-If the
-.I fd_out
-descriptor,
-.B IOSQE_FIXED_FILE
-can be set in the SQE to indicate that. For the input file, the io_uring
-specific
-.B SPLICE_F_FD_IN_FIXED
-can be set in
-.I splice_flags
-and
-.I fd_in
-given as a registered file descriptor offset.
-
-If
-.I fd_in
-refers to a pipe,
-.I off_in
-is ignored and must be set to -1.
-
-If
-.I fd_in
-does not refer to a pipe and
-.I off_in
-is -1, then
-.I nbytes
-are read from
-.I fd_in
-starting from the file offset, which is incremented by the number of bytes read.
-
-If
-.I fd_in
-does not refer to a pipe and
-.I off_in
-is not -1, then the starting offset of
-.I fd_in
-will be
-.IR off_in .
-
-The same rules apply to
-.I fd_out
-and
-.IR off_out .
-
-This function prepares an async
-.BR splice (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_register (2),
-.BR splice (2)
-
-.SH NOTES
-Note that even if
-.I fd_in
-or
-.I fd_out
-refers to a pipe, the splice operation can still fail with
-.B EINVAL
-if one of the fd doesn't explicitly support splice operation, e.g. reading from
-terminal is unsupported from kernel 5.7 to 5.11.
diff --git a/src/liburing/man/io_uring_prep_statx.3 b/src/liburing/man/io_uring_prep_statx.3
deleted file mode 100644
index d9d983a0470f..000000000000
--- a/src/liburing/man/io_uring_prep_statx.3
+++ /dev/null
@@ -1,74 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_statx 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_statx \- prepare a statx request
-.SH SYNOPSIS
-.nf
-.B #include <sys/types.h>
-.B #include <sys/stat.h>
-.B #include <unistd.h>
-.B #include <fcntl.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_statx(struct io_uring_sqe *" sqe ","
-.BI " int " dirfd ","
-.BI " const char *" path ","
-.BI " int " flags ","
-.BI " unsigned " mask ","
-.BI " struct statx *" statxbuf ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_statx (3)
-function prepares a statx request. The submission queue entry
-.I sqe
-is setup to use the directory file descriptor pointed to by
-.I dirfd
-to start a statx operation on the path identified by
-.I path
-and using the flags given in
-.I flags
-for the fields specified by
-.I mask
-and into the buffer located at
-.IR statxbuf .
-
-This function prepares an async
-.BR statx (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR statx (2)
diff --git a/src/liburing/man/io_uring_prep_symlink.3 b/src/liburing/man/io_uring_prep_symlink.3
deleted file mode 120000
index ae6f41a25c12..000000000000
--- a/src/liburing/man/io_uring_prep_symlink.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_symlinkat.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_symlinkat.3 b/src/liburing/man/io_uring_prep_symlinkat.3
deleted file mode 100644
index b809f938b75f..000000000000
--- a/src/liburing/man/io_uring_prep_symlinkat.3
+++ /dev/null
@@ -1,85 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_symlinkat 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_symlinkat \- prepare a symlinkat request
-.SH SYNOPSIS
-.nf
-.B #include <fcntl.h>
-.B #include <unistd.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_symlinkat(struct io_uring_sqe *" sqe ","
-.BI " const char *" target ","
-.BI " int " newdirfd ","
-.BI " const char *" linkpath ");"
-.PP
-.BI "void io_uring_prep_symlink(struct io_uring_sqe *" sqe ","
-.BI " const char *" target ","
-.BI " const char *" linkpath ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_symlinkat (3)
-function prepares a symlinkat request. The submission queue entry
-.I sqe
-is setup to symlink the target path pointed to by
-.I target
-to the new destination indicated by
-.I newdirfd
-and
-.IR linkpath .
-
-The
-.BR io_uring_prep_symlink (3)
-function prepares a symlink request. The submission queue entry
-.I sqe
-is setup to symlink the target path pointed to by
-.I target
-to the new destination indicated by
-.I linkpath
-relative to the current working directory. This function prepares an async
-.BR symlink (2)
-request. See that man page for details.
-
-These functions prepare an async
-.BR symlinkat (2)
-or
-.BR symlink (2)
-request. See those man pages for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR symlinkat (2),
-.BR symlink (2)
diff --git a/src/liburing/man/io_uring_prep_sync_file_range.3 b/src/liburing/man/io_uring_prep_sync_file_range.3
deleted file mode 100644
index 830e4115064d..000000000000
--- a/src/liburing/man/io_uring_prep_sync_file_range.3
+++ /dev/null
@@ -1,59 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_sync_file_range 3 "March 12, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_sync_file_range \- prepare a sync_file_range request
-.SH SYNOPSIS
-.nf
-.B #include <fcntl.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_sync_file_range(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " unsigned " len ","
-.BI " __u64 " offset ","
-.BI " int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_sync_file_range (3)
-function prepares a sync_file_range request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I fd
-that should get
-.I len
-bytes synced started at offset
-.I offset
-and with modifier flags in the
-.I flags
-argument.
-
-This function prepares an async
-.BR sync_file_range (2)
-request. See that man page for details on the arguments.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR sync_file_range (2)
diff --git a/src/liburing/man/io_uring_prep_tee.3 b/src/liburing/man/io_uring_prep_tee.3
deleted file mode 100644
index 44aaaf60313a..000000000000
--- a/src/liburing/man/io_uring_prep_tee.3
+++ /dev/null
@@ -1,74 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_tee 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_tee \- prepare a tee request
-.SH SYNOPSIS
-.nf
-.B #include <fcntl.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_tee(struct io_uring_sqe *" sqe ","
-.BI " int " fd_in ","
-.BI " int " fd_out ","
-.BI " unsigned int " nbytes ","
-.BI " unsigned int " splice_flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_tee (3)
-function prepares a tee request. The submission queue entry
-.I sqe
-is setup to use as input the file descriptor
-.I fd_in
-and as output the file descriptor
-.I fd_out
-duplicating
-.I nbytes
-bytes worth of data.
-.I splice_flags
-are modifier flags for the operation. See
-.BR tee (2)
-for the generic splice flags.
-
-If the
-.I fd_out
-descriptor,
-.B IOSQE_FIXED_FILE
-can be set in the SQE to indicate that. For the input file, the io_uring
-specific
-.B SPLICE_F_FD_IN_FIXED
-can be set and
-.I fd_in
-given as a registered file descriptor offset.
-
-This function prepares an async
-.BR tee (2)
-request. See that man page for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_register (2),
-.BR splice (2),
-.BR tee (2)
diff --git a/src/liburing/man/io_uring_prep_timeout.3 b/src/liburing/man/io_uring_prep_timeout.3
deleted file mode 100644
index a944d6e76e35..000000000000
--- a/src/liburing/man/io_uring_prep_timeout.3
+++ /dev/null
@@ -1,107 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_timeout 3 "March 12, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_timeout \- prepare a timeout request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_timeout(struct io_uring_sqe *" sqe ","
-.BI " struct __kernel_timespec *" ts ","
-.BI " unsigned " count ","
-.BI " unsigned " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_timeout (3)
-function prepares a timeout request. The submission queue entry
-.I sqe
-is setup to arm a timeout specified by
-.I ts
-and with a timeout count of
-.I count
-completion entries. The
-.I flags
-argument holds modifier flags for the request.
-
-This request type can be used as a timeout waking anyone sleeping
-for events on the CQ ring. The
-.I flags
-argument may contain:
-.TP
-.B IORING_TIMEOUT_ABS
-The value specified in
-.I ts
-is an absolute value rather than a relative one.
-.TP
-.B IORING_TIMEOUT_BOOTTIME
-The boottime clock source should be used.
-.TP
-.B IORING_TIMEOUT_REALTIME
-The realtime clock source should be used.
-.TP
-.B IORING_TIMEOUT_ETIME_SUCCESS
-Consider an expired timeout a success in terms of the posted completion. This
-means it will not sever dependent links, as a failed request normally would. The
-posted CQE result code will still contain
-.B -ETIME
-in the
-.I res
-value.
-.TP
-.B IORING_TIMEOUT_MULTISHOT
-The request will return multiple timeout completions. The completion flag
-IORING_CQE_F_MORE is set if more timeouts are expected. The value specified in
-.I count
-is the number of repeats. A value of 0 means the timeout is indefinite and can
-only be stopped by a removal request. Available since the 6.4 kernel.
-.PP
-If no alternate clock source is given in the above flags, then
-.B CLOCK_MONOTONIC
-is used.
-
-The timeout completion event will trigger if either the specified timeout
-has occurred, or the specified number of events to wait for have been posted
-to the CQ ring.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-These are the errors that are reported in the CQE
-.I res
-field. On success,
-.B 0
-is returned.
-.TP
-.B -ETIME
-The specified timeout occurred and triggered the completion event.
-.TP
-.B -EINVAL
-One of the fields set in the SQE was invalid. For example, two clocksources
-were given, or the specified timeout seconds or nanoseconds were < 0.
-.TP
-.B -EFAULT
-io_uring was unable to access the data specified by
-.IR ts .
-.TP
-.B -ECANCELED
-The timeout was canceled by a removal request.
-.SH NOTES
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_prep_timeout_remove (3),
-.BR io_uring_prep_timeout_update (3)
diff --git a/src/liburing/man/io_uring_prep_timeout_remove.3 b/src/liburing/man/io_uring_prep_timeout_remove.3
deleted file mode 120000
index 5aebd3685124..000000000000
--- a/src/liburing/man/io_uring_prep_timeout_remove.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_timeout_update.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_timeout_update.3 b/src/liburing/man/io_uring_prep_timeout_update.3
deleted file mode 100644
index 606fbc6329bc..000000000000
--- a/src/liburing/man/io_uring_prep_timeout_update.3
+++ /dev/null
@@ -1,99 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_timeout_update 3 "March 12, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_timeout_update \- prepare a request to update an existing timeout
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_timeout_update(struct io_uring_sqe *" sqe ","
-.BI " struct __kernel_timespec *" ts ","
-.BI " __u64 " user_data ","
-.BI " unsigned " flags ");"
-.PP
-.BI "void io_uring_prep_timeout_remove(struct io_uring_sqe *" sqe ","
-.BI " __u64 " user_data ","
-.BI " unsigned " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-These functions modify or cancel an existing timeout request. The submission
-queue entry
-.I sqe
-is setup to arm a timeout update or removal specified by
-.I user_data
-and with modifier flags given by
-.IR flags .
-Additionally, the update request includes a
-.I ts
-structure, which contains new timeout information.
-
-For an update request, the
-.I flags
-member may contain a bitmask of the following values:
-.TP
-.B IORING_TIMEOUT_ABS
-The value specified in
-.I ts
-is an absolute value rather than a relative one.
-.TP
-.B IORING_TIMEOUT_BOOTTIME
-The boottime clock source should be used.
-.TP
-.B IORING_TIMEOUT_REALTIME
-The realtime clock source should be used.
-.TP
-.B IORING_TIMEOUT_ETIME_SUCCESS
-Consider an expired timeout a success in terms of the posted completion.
-Normally a timeout that triggers would return in a
-.B -ETIME
-CQE
-.I res
-value.
-.PP
-The timeout remove command does not currently accept any flags.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-These are the errors that are reported in the CQE
-.I res
-field. On success,
-.B 0
-is returned.
-.TP
-.B -ENOENT
-The timeout identified by
-.I user_data
-could not be found. It may be invalid, or triggered before the update or
-removal request was processed.
-.TP
-.B -EALREADY
-The timeout identified by
-.I user_data
-is already firing and cannot be canceled.
-.TP
-.B -EINVAL
-One of the fields set in the SQE was invalid. For example, two clocksources
-were given, or the specified timeout seconds or nanoseconds were < 0.
-.TP
-.B -EFAULT
-io_uring was unable to access the data specified by
-.IR ts .
-.SH NOTES
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_prep_timeout (3)
diff --git a/src/liburing/man/io_uring_prep_unlink.3 b/src/liburing/man/io_uring_prep_unlink.3
deleted file mode 120000
index 80f86d2dd973..000000000000
--- a/src/liburing/man/io_uring_prep_unlink.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_prep_unlinkat.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_prep_unlinkat.3 b/src/liburing/man/io_uring_prep_unlinkat.3
deleted file mode 100644
index ba2633cf0b91..000000000000
--- a/src/liburing/man/io_uring_prep_unlinkat.3
+++ /dev/null
@@ -1,82 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_unlinkat 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_prep_unlinkat \- prepare an unlinkat request
-.SH SYNOPSIS
-.nf
-.B #include <fcntl.h>
-.B #include <unistd.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_unlinkat(struct io_uring_sqe *" sqe ","
-.BI " int " dirfd ","
-.BI " const char *" path ","
-.BI " int " flags ");"
-.PP
-.BI "void io_uring_prep_unlink(struct io_uring_sqe *" sqe ","
-.BI " const char *" path ","
-.BI " int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_unlinkat (3)
-function prepares an unlinkat request. The submission queue entry
-.I sqe
-is setup to use the directory file descriptor pointed to by
-.I dirfd
-to start an unlinkat operation on the path identified by
-.I path
-and using the flags given in
-.IR flags .
-
-The
-.BR io_uring_prep_unlink (3)
-function prepares an unlink request. The submission queue entry
-.I sqe
-is setup to start an unlinkat operation on the path identified by
-.I path
-relative to the current working directory and using the flags given in
-.IR flags .
-
-These functions prepare an async
-.BR unlinkat (2)
-or
-.BR unlink (2)
-request. See those man pages for details.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR unlinkat (2),
-.BR unlink (2)
diff --git a/src/liburing/man/io_uring_prep_waitid.3 b/src/liburing/man/io_uring_prep_waitid.3
deleted file mode 100644
index 06bda74ed25f..000000000000
--- a/src/liburing/man/io_uring_prep_waitid.3
+++ /dev/null
@@ -1,67 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_waitid 3 "July 14, 2023" "liburing-2.5" "liburing Manual"
-.SH NAME
-io_uring_prep_waitid \- prepare a waitid request
-.SH SYNOPSIS
-.nf
-.B #include <sys/wait.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_waitid(struct io_uring_sqe *" sqe ","
-.BI " idtype_t " idtype ","
-.BI " id_t " id ","
-.BI " siginfo_t *" infop ","
-.BI " int " options ","
-.BI " unsigned int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_waitid (3)
-function prepares a waitid request. The submission queue entry
-.I sqe
-is setup to use the
-.I idtype
-and
-.I id
-arguments select the child(ren), and
-.I options
-to specify the child state changes to wait for. Upon successful
-return, it fills
-.I infop
-with information of the child process, if any.
-.I flags
-is io_uring specific modifier flags. They are currently unused, and hence
-.B 0
-should be passed.
-
-This function prepares an async
-.BR waitid (2)
-request. See that man page for details.
-
-Available since kernel 6.7.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR waitid (2)
diff --git a/src/liburing/man/io_uring_prep_write.3 b/src/liburing/man/io_uring_prep_write.3
deleted file mode 100644
index 794361f05ff7..000000000000
--- a/src/liburing/man/io_uring_prep_write.3
+++ /dev/null
@@ -1,67 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_write 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_prep_write \- prepare I/O write request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_write(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " const void *" buf ","
-.BI " unsigned " nbytes ","
-.BI " __u64 " offset ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_write (3)
-prepares an IO write request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I fd
-to start writing
-.I nbytes
-from the buffer
-.I buf
-at the specified
-.IR offset .
-
-On files that support seeking, if the offset is set to
-.BR -1 ,
-the write operation commences at the file offset, and the file offset is
-incremented by the number of bytes written. See
-.BR write (2)
-for more details. Note that for an async API, reading and updating the
-current file offset may result in unpredictable behavior, unless access
-to the file is serialized. It is not encouraged to use this feature if it's
-possible to provide the desired IO offset from the application or library.
-
-On files that are not capable of seeking, the offset must be 0 or -1.
-
-After the write has been prepared, it can be submitted with one of the submit
-functions.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3)
diff --git a/src/liburing/man/io_uring_prep_write_fixed.3 b/src/liburing/man/io_uring_prep_write_fixed.3
deleted file mode 100644
index 3a98e75e4075..000000000000
--- a/src/liburing/man/io_uring_prep_write_fixed.3
+++ /dev/null
@@ -1,72 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_write_fixed 3 "February 13, 2022" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_prep_write_fixed \- prepare I/O write request with registered buffer
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_write_fixed(struct io_uring_sqe *" sqe ","
-.BI " int " fd ",
-.BI " const void *" buf ","
-.BI " unsigned " nbytes ","
-.BI " __u64 " offset ","
-.BI " int " buf_index ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_write_fixed (3)
-prepares an IO write request with a previously registered IO buffer. The
-submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I fd
-to start writing
-.I nbytes
-from the buffer
-.I buf
-at the specified
-.I offset
-and with the buffer matching the registered index of
-.IR buf_index .
-
-This works just like
-.BR io_uring_prep_write (3)
-except it requires the use of buffers that have been registered with
-.BR io_uring_register_buffers (3).
-The
-.I buf
-and
-.I nbytes
-arguments must fall within a region specified by
-.I buf_index
-in the previously registered buffer. The buffer need not be aligned with
-the start of the registered buffer.
-
-After the write has been prepared it can be submitted with one of the submit
-functions.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH SEE ALSO
-.BR io_uring_prep_write (3),
-.BR io_uring_register_buffers (3)
diff --git a/src/liburing/man/io_uring_prep_writev.3 b/src/liburing/man/io_uring_prep_writev.3
deleted file mode 100644
index b325b35f0805..000000000000
--- a/src/liburing/man/io_uring_prep_writev.3
+++ /dev/null
@@ -1,85 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_writev 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_prep_writev \- prepare vector I/O write request
-.SH SYNOPSIS
-.nf
-.B #include <sys/uio.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_writev(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " const struct iovec *" iovecs ","
-.BI " unsigned " nr_vecs ","
-.BI " __u64 " offset ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_writev (3)
-prepares a vectored IO write request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I fd
-to start writing
-.I nr_vecs
-from the
-.I iovecs
-array at the specified
-.IR offset .
-
-On files that support seeking, if the offset is set to
-.BR -1 ,
-the write operation commences at the file offset, and the file offset is
-incremented by the number of bytes written. See
-.BR write (2)
-for more details. Note that for an async API, reading and updating the
-current file offset may result in unpredictable behavior, unless access
-to the file is serialized. It is not encouraged to use this feature if it's
-possible to provide the desired IO offset from the application or library.
-
-On files that are not capable of seeking, the offset must be 0 or -1.
-
-After the write has been prepared it can be submitted with one of the submit
-functions.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-Unless an application explicitly needs to pass in more than one iovec, it
-is more efficient to use
-.BR io_uring_prep_write (3)
-rather than this function, as no state has to be maintained for a
-non-vectored IO request.
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_prep_write (3),
-.BR io_uring_prep_writev2 (3),
-.BR io_uring_submit (3)
diff --git a/src/liburing/man/io_uring_prep_writev2.3 b/src/liburing/man/io_uring_prep_writev2.3
deleted file mode 100644
index d7cc46ecddfd..000000000000
--- a/src/liburing/man/io_uring_prep_writev2.3
+++ /dev/null
@@ -1,111 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_prep_writev2 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_prep_writev2 \- prepare vector I/O write request with flags
-.SH SYNOPSIS
-.nf
-.B #include <sys/uio.h>
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_prep_writev2(struct io_uring_sqe *" sqe ","
-.BI " int " fd ","
-.BI " const struct iovec *" iovecs ","
-.BI " unsigned " nr_vecs ","
-.BI " __u64 " offset ","
-.BI " int " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_writev2 (3)
-prepares a vectored IO write request. The submission queue entry
-.I sqe
-is setup to use the file descriptor
-.I fd
-to start writing
-.I nr_vecs
-from the
-.I iovecs
-array at the specified
-.IR offset .
-The behavior of the function can be controlled with the
-.I flags
-parameter.
-
-Supported values for
-.I flags
-are:
-.TP
-.B RWF_HIPRI
-High priority request, poll if possible
-.TP
-.B RWF_DSYNC
-per-IO O_DSYNC
-.TP
-.B RWF_SYNC
-per-IO O_SYNC
-.TP
-.B RWF_NOWAIT
-per-IO, return
-.B -EAGAIN
-if operation would block
-.TP
-.B RWF_APPEND
-per-IO O_APPEND
-
-.P
-On files that support seeking, if the offset is set to
-.BR -1 ,
-the write operation commences at the file offset, and the file offset is
-incremented by the number of bytes written. See
-.BR write (2)
-for more details. Note that for an async API, reading and updating the
-current file offset may result in unpredictable behavior, unless access
-to the file is serialized. It is not encouraged to use this feature if it's
-possible to provide the desired IO offset from the application or library.
-
-On files that are not capable of seeking, the offset must be 0 or -1.
-
-After the write has been prepared, it can be submitted with one of the submit
-functions.
-
-.SH RETURN VALUE
-None
-.SH ERRORS
-The CQE
-.I res
-field will contain the result of the operation. See the related man page for
-details on possible values. Note that where synchronous system calls will return
-.B -1
-on failure and set
-.I errno
-to the actual error value, io_uring never uses
-.IR errno .
-Instead it returns the negated
-.I errno
-directly in the CQE
-.I res
-field.
-.SH NOTES
-Unless an application explicitly needs to pass in more than one iovec, it
-is more efficient to use
-.BR io_uring_prep_write (3)
-rather than this function, as no state has to be maintained for a
-non-vectored IO request.
-As with any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_prep_write (3),
-.BR io_uring_prep_writev (3),
-.BR io_uring_submit (3)
diff --git a/src/liburing/man/io_uring_queue_exit.3 b/src/liburing/man/io_uring_queue_exit.3
deleted file mode 100644
index 00f8ae9b1636..000000000000
--- a/src/liburing/man/io_uring_queue_exit.3
+++ /dev/null
@@ -1,26 +0,0 @@
-.\" Copyright (C) 2020 Jens Axboe <axboe@kernel.dk>
-.\" Copyright (C) 2020 Red Hat, Inc.
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_queue_exit 3 "July 10, 2020" "liburing-0.7" "liburing Manual"
-.SH NAME
-io_uring_queue_exit \- tear down io_uring submission and completion queues
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_queue_exit(struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-.BR io_uring_queue_exit (3)
-will release all resources acquired and initialized by
-.BR io_uring_queue_init (3).
-It first unmaps the memory shared between the application and the kernel and then closes the io_uring file descriptor.
-.SH RETURN VALUE
-None
-.SH SEE ALSO
-.BR io_uring_setup (2),
-.BR mmap (2),
-.BR io_uring_queue_init (3)
diff --git a/src/liburing/man/io_uring_queue_init.3 b/src/liburing/man/io_uring_queue_init.3
deleted file mode 100644
index 342604d610f9..000000000000
--- a/src/liburing/man/io_uring_queue_init.3
+++ /dev/null
@@ -1,130 +0,0 @@
-.\" Copyright (C) 2020 Jens Axboe <axboe@kernel.dk>
-.\" Copyright (C) 2020 Red Hat, Inc.
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_queue_init 3 "July 10, 2020" "liburing-0.7" "liburing Manual"
-.SH NAME
-io_uring_queue_init \- setup io_uring submission and completion queues
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_queue_init(unsigned " entries ","
-.BI " struct io_uring *" ring ","
-.BI " unsigned " flags ");"
-.PP
-.BI "int io_uring_queue_init_params(unsigned " entries ","
-.BI " struct io_uring *" ring ","
-.BI " struct io_uring_params *" params ");"
-.PP
-.BI "int io_uring_queue_init_mem(unsigned " entries ","
-.BI " struct io_uring *" ring ","
-.BI " struct io_uring_params *" params ","
-.BI " void *" buf ", size_t " buf_size ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_queue_init (3)
-function executes the
-.BR io_uring_setup (2)
-system call to initialize the submission and completion queues in the kernel
-with at least
-.I entries
-entries in the submission queue and then maps the resulting file descriptor to
-memory shared between the application and the kernel.
-
-By default, the CQ ring will have twice the number of entries as specified by
-.I entries
-for the SQ ring. This is adequate for regular file or storage workloads, but
-may be too small for networked workloads. The SQ ring entries do not impose a
-limit on the number of in-flight requests that the ring can support, it merely
-limits the number that can be submitted to the kernel in one go (batch). If the
-CQ ring overflows, e.g. more entries are generated than fits in the ring before
-the application can reap them, then if the kernel supports
-.B IORING_FEAT_NODROP
-the ring enters a CQ ring overflow state. Otherwise it drops the CQEs and
-increments
-.I cq.koverflow
-in
-.I struct io_uring
-with the number of CQEs dropped. The overflow state is indicated by
-.B IORING_SQ_CQ_OVERFLOW
-being set in the SQ ring flags. Unless the kernel runs out of available memory,
-entries are not dropped, but it is a much slower completion path and will slow
-down request processing. For that reason it should be avoided and the CQ
-ring sized appropriately for the workload. Setting
-.I cq_entries
-in
-.I struct io_uring_params
-will tell the kernel to allocate this many entries for the CQ ring, independent
-of the SQ ring size in given in
-.IR entries .
-If the value isn't a power of 2, it will be rounded up to the nearest power of
-2.
-
-On success,
-.BR io_uring_queue_init (3)
-returns 0 and
-.I ring
-will point to the shared memory containing the io_uring queues. On failure
-.BR -errno
-is returned.
-
-.I flags
-will be passed through to the io_uring_setup syscall (see
-.BR io_uring_setup (2)).
-
-The
-.BR io_uring_queue_init_params (3)
-and
-.BR io_uring_queue_init_mem (3)
-variants will pass the parameters indicated by
-.I params
-straight through to the
-.BR io_uring_setup (2)
-system call.
-
-The
-.BR io_uring_queue_init_mem (3)
-variant uses the provided
-.I buf
-with associated size
-.I buf_size
-as the memory for the ring, using the
-.B IORING_SETUP_NO_MMAP
-flag to
-.BR io_uring_setup (2).
-The buffer passed to
-.BR io_uring_queue_init_mem (3)
-must be page size aligned on the host, and must already be zeroed.
-Typically, the caller should allocate a huge page and pass that in to
-.BR io_uring_queue_init_mem (3).
-Pages allocated by mmap are already zeroed.
-.BR io_uring_queue_init_mem (3)
-returns the number of bytes used from the provided buffer, so that the app can
-reuse the buffer with the returned offset to put more rings in the same huge
-page.
-
-On success, the resources held by
-.I ring
-should be released via a corresponding call to
-.BR io_uring_queue_exit (3).
-.SH RETURN VALUE
-.BR io_uring_queue_init (3)
-and
-.BR io_uring_queue_init_params (3)
-return 0 on success and
-.BR -errno
-on failure.
-
-.BR io_uring_queue_init_mem (3)
-returns the number of bytes used from the provided buffer on success, and
-.BR -errno
-on failure.
-.SH SEE ALSO
-.BR io_uring_setup (2),
-.BR io_uring_register_ring_fd (3),
-.BR mmap (2),
-.BR io_uring_queue_exit (3)
diff --git a/src/liburing/man/io_uring_queue_init_mem.3 b/src/liburing/man/io_uring_queue_init_mem.3
deleted file mode 120000
index c91609e5f561..000000000000
--- a/src/liburing/man/io_uring_queue_init_mem.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_queue_init.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_queue_init_params.3 b/src/liburing/man/io_uring_queue_init_params.3
deleted file mode 120000
index c91609e5f561..000000000000
--- a/src/liburing/man/io_uring_queue_init_params.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_queue_init.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_recvmsg_cmsg_firsthdr.3 b/src/liburing/man/io_uring_recvmsg_cmsg_firsthdr.3
deleted file mode 120000
index 8eb17436288d..000000000000
--- a/src/liburing/man/io_uring_recvmsg_cmsg_firsthdr.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_recvmsg_out.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_recvmsg_cmsg_nexthdr.3 b/src/liburing/man/io_uring_recvmsg_cmsg_nexthdr.3
deleted file mode 120000
index 8eb17436288d..000000000000
--- a/src/liburing/man/io_uring_recvmsg_cmsg_nexthdr.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_recvmsg_out.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_recvmsg_name.3 b/src/liburing/man/io_uring_recvmsg_name.3
deleted file mode 120000
index 8eb17436288d..000000000000
--- a/src/liburing/man/io_uring_recvmsg_name.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_recvmsg_out.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_recvmsg_out.3 b/src/liburing/man/io_uring_recvmsg_out.3
deleted file mode 100644
index 8d605d81352f..000000000000
--- a/src/liburing/man/io_uring_recvmsg_out.3
+++ /dev/null
@@ -1,82 +0,0 @@
-.\" Copyright (C), 2022 Dylan Yudaken <dylany@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_recvmsg_out 3 "July 26, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_recvmsg_out - access data from multishot recvmsg
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "struct io_uring_recvmsg_out *io_uring_recvmsg_validate(void *" buf ","
-.BI " int " buf_len ","
-.BI " struct msghdr *" msgh ");"
-.PP
-.BI "void *io_uring_recvmsg_name(struct io_uring_recvmsg_out *" o ");"
-.PP
-.BI "struct cmsghdr *io_uring_recvmsg_cmsg_firsthdr(struct io_uring_recvmsg_out *" o ","
-.BI " struct msghdr *" msgh ");"
-.BI "struct cmsghdr *io_uring_recvmsg_cmsg_nexthdr(struct io_uring_recvmsg_out *" o ","
-.BI " struct msghdr *" msgh ","
-.BI " struct cmsghdr *" cmsg ");"
-.PP
-.BI "void *io_uring_recvmsg_payload(struct io_uring_recvmsg_out *" o ","
-.BI " struct msghdr *" msgh ");"
-.BI "unsigned int io_uring_recvmsg_payload_length(struct io_uring_recvmsg_out *" o ","
-.BI " int " buf_len ","
-.BI " struct msghdr *" msgh ");"
-.PP
-.fi
-
-.SH DESCRIPTION
-
-These functions are used to access data in the payload delivered by
-.BR io_uring_prep_recvmsg_multishot (3).
-.PP
-.I msgh
-should point to the
-.I struct msghdr
-submitted with the request.
-.PP
-.BR io_uring_recvmsg_validate (3)
-will validate a buffer delivered by
-.BR io_uring_prep_recvmsg_multishot (3)
-and extract the
-.I io_uring_recvmsg_out
-if it is valid, returning a pointer to it or else NULL.
-.PP
-The structure is defined as follows:
-.PP
-.in +4n
-.EX
-
-struct io_uring_recvmsg_out {
- __u32 namelen; /* Name byte count as would have been populated
- * by recvmsg(2) */
- __u32 controllen; /* Control byte count */
- __u32 payloadlen; /* Payload byte count as would have been returned
- * by recvmsg(2) */
- __u32 flags; /* Flags result as would have been populated
- * by recvmsg(2) */
-};
-
-.IP * 3
-.BR io_uring_recvmsg_name (3)
-returns a pointer to the name in the buffer.
-.IP *
-.BR io_uring_recvmsg_cmsg_firsthdr (3)
-returns a pointer to the first cmsg in the buffer, or NULL.
-.IP *
-.BR io_uring_recvmsg_cmsg_nexthdr (3)
-returns a pointer to the next cmsg in the buffer, or NULL.
-.IP *
-.BR io_uring_recvmsg_payload (3)
-returns a pointer to the payload in the buffer.
-.IP *
-.BR io_uring_recvmsg_payload_length (3)
-Calculates the usable payload length in bytes.
-
-
-.SH "SEE ALSO"
-.BR io_uring_prep_recvmsg_multishot (3)
diff --git a/src/liburing/man/io_uring_recvmsg_payload.3 b/src/liburing/man/io_uring_recvmsg_payload.3
deleted file mode 120000
index 8eb17436288d..000000000000
--- a/src/liburing/man/io_uring_recvmsg_payload.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_recvmsg_out.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_recvmsg_payload_length.3 b/src/liburing/man/io_uring_recvmsg_payload_length.3
deleted file mode 120000
index 8eb17436288d..000000000000
--- a/src/liburing/man/io_uring_recvmsg_payload_length.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_recvmsg_out.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_recvmsg_validate.3 b/src/liburing/man/io_uring_recvmsg_validate.3
deleted file mode 120000
index 8eb17436288d..000000000000
--- a/src/liburing/man/io_uring_recvmsg_validate.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_recvmsg_out.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_register.2 b/src/liburing/man/io_uring_register.2
deleted file mode 100644
index fa3c3e8f1ac2..000000000000
--- a/src/liburing/man/io_uring_register.2
+++ /dev/null
@@ -1,1199 +0,0 @@
-.\" Copyright (C) 2019 Jens Axboe <axboe@kernel.dk>
-.\" Copyright (C) 2019 Red Hat, Inc.
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_register 2 2019-01-17 "Linux" "Linux Programmer's Manual"
-.SH NAME
-io_uring_register \- register files or user buffers for asynchronous I/O
-.SH SYNOPSIS
-.nf
-.BR "#include <liburing.h>"
-.PP
-.BI "int io_uring_register(unsigned int " fd ", unsigned int " opcode ,
-.BI " void *" arg ", unsigned int " nr_args );
-.fi
-.PP
-.SH DESCRIPTION
-.PP
-
-The
-.BR io_uring_register (2)
-system call registers resources (e.g. user buffers, files, eventfd,
-personality, restrictions) for use in an
-.BR io_uring (7)
-instance referenced by
-.IR fd .
-Registering files or user buffers allows the kernel to take long term
-references to internal data structures or create long term mappings of
-application memory, greatly reducing per-I/O overhead.
-
-.I fd
-is the file descriptor returned by a call to
-.BR io_uring_setup (2).
-If
-.I opcode
-has the flag
-.B IORING_REGISTER_USE_REGISTERED_RING
-ored into it,
-.I fd
-is instead the index of a registered ring fd.
-
-.I opcode
-can be one of:
-
-.TP
-.B IORING_REGISTER_BUFFERS
-.I arg
-points to a
-.I struct iovec
-array of
-.I nr_args
-entries. The buffers associated with the iovecs will be locked in
-memory and charged against the user's
-.B RLIMIT_MEMLOCK
-resource limit. See
-.BR getrlimit (2)
-for more information. Additionally, there is a size limit of 1GiB per
-buffer. Currently, the buffers must be anonymous, non-file-backed
-memory, such as that returned by
-.BR malloc (3)
-or
-.BR mmap (2)
-with the
-.B MAP_ANONYMOUS
-flag set. It is expected that this limitation will be lifted in the
-future. Huge pages are supported as well. Note that the entire huge
-page will be pinned in the kernel, even if only a portion of it is
-used.
-
-After a successful call, the supplied buffers are mapped into the
-kernel and eligible for I/O. To make use of them, the application
-must specify the
-.B IORING_OP_READ_FIXED
-or
-.B IORING_OP_WRITE_FIXED
-opcodes in the submission queue entry (see the
-.I struct io_uring_sqe
-definition in
-.BR io_uring_enter (2)),
-and set the
-.I buf_index
-field to the desired buffer index. The memory range described by the
-submission queue entry's
-.I addr
-and
-.I len
-fields must fall within the indexed buffer.
-
-It is perfectly valid to setup a large buffer and then only use part
-of it for an I/O, as long as the range is within the originally mapped
-region.
-
-An application can increase or decrease the size or number of
-registered buffers by first unregistering the existing buffers, and
-then issuing a new call to
-.BR io_uring_register (2)
-with the new buffers.
-
-Note that before 5.13 registering buffers would wait for the ring to idle.
-If the application currently has requests in-flight, the registration will
-wait for those to finish before proceeding.
-
-An application need not unregister buffers explicitly before shutting
-down the io_uring instance. Note, however, that shutdown processing may run
-asynchronously within the kernel. As a result, it is not guaranteed that
-pages are immediately unpinned in this case. Available since 5.1.
-
-.TP
-.B IORING_REGISTER_BUFFERS2
-Register buffers for I/O. Similar to
-.B IORING_REGISTER_BUFFERS
-but aims to have a more extensible ABI.
-
-.I arg
-points to a
-.I struct
-.IR io_uring_rsrc_register ,
-and
-.I nr_args
-should be set to the number of bytes in the structure.
-
-.IP
-.in +4n
-.EX
-struct io_uring_rsrc_register {
- __u32 nr;
- __u32 flags;
- __u64 resv2;
- __aligned_u64 data;
- __aligned_u64 tags;
-};
-.EE
-.in
-.IP
-
-The
-.I data
-field contains a pointer to a
-.I struct iovec
-array of
-.I nr
-entries.
-The
-.I tags
-field should either be 0, then tagging is disabled, or point to an array
-of
-.I nr
-"tags" (unsigned 64 bit integers). If a tag is zero, then tagging for this
-particular resource (a buffer in this case) is disabled. Otherwise, after the
-resource had been unregistered and it's not used anymore, a CQE will be
-posted with
-.I user_data
-set to the specified tag and all other fields zeroed.
-
-The
-.I flags
-field supports the following flags:
-
-.IP
-.in +4n
-.B IORING_RSRC_REGISTER_SPARSE
-If set, io_uring will register
-.I nr
-empty buffers, which need to be updated before use. When this flag is set,
-.I data
-and
-.I tags
-must be NULL. Available since 5.19.
-.in
-.IP
-
-Note that resource updates, e.g.
-.BR IORING_REGISTER_BUFFERS_UPDATE ,
-don't necessarily deallocate resources by the time it returns, but they might
-be held alive until all requests using it complete.
-
-Available since 5.13.
-
-.TP
-.B IORING_REGISTER_BUFFERS_UPDATE
-Updates registered buffers with new ones, either turning a sparse entry into
-a real one, or replacing an existing entry.
-
-.I arg
-must contain a pointer to a
-.I struct
-.IR io_uring_rsrc_update2 ,
-which contains
-an offset on which to start the update, and an array of
-.I struct
-.IR iovec .
-.I tags
-points to an array of tags.
-.I nr
-must contain the number of descriptors in the passed in arrays.
-See
-.B IORING_REGISTER_BUFFERS2
-for the resource tagging description.
-
-.PP
-.in +8n
-.EX
-
-struct io_uring_rsrc_update2 {
- __u32 offset;
- __u32 resv;
- __aligned_u64 data;
- __aligned_u64 tags;
- __u32 nr;
- __u32 resv2;
-};
-.EE
-.in
-.PP
-
-.in +8n
-
-Available since 5.13.
-
-.TP
-.B IORING_UNREGISTER_BUFFERS
-This operation takes no argument, and
-.I arg
-must be passed as NULL. All previously registered buffers associated
-with the io_uring instance will be released synchronously. Available since 5.1.
-
-.TP
-.B IORING_REGISTER_FILES
-Register files for I/O.
-.I arg
-contains a pointer to an array of
-.I nr_args
-file descriptors (signed 32 bit integers).
-
-To make use of the registered files, the
-.B IOSQE_FIXED_FILE
-flag must be set in the
-.I flags
-member of the
-.IR "struct io_uring_sqe" ,
-and the
-.I fd
-member is set to the index of the file in the file descriptor array.
-
-The file set may be sparse, meaning that the
-.B fd
-field in the array may be set to
-.BR -1 .
-See
-.B IORING_REGISTER_FILES_UPDATE
-for how to update files in place.
-
-Note that before 5.13 registering files would wait for the ring to idle.
-If the application currently has requests in-flight, the registration will
-wait for those to finish before proceeding. See
-.B IORING_REGISTER_FILES_UPDATE
-for how to update an existing set without that limitation.
-
-Files are automatically unregistered when the io_uring instance is
-torn down. An application needs only unregister if it wishes to
-register a new set of fds. Available since 5.1.
-
-.TP
-.B IORING_REGISTER_FILES2
-Register files for I/O. Similar to
-.BR IORING_REGISTER_FILES .
-
-.I arg
-points to a
-.I struct
-.IR io_uring_rsrc_register ,
-and
-.I nr_args
-should be set to the number of bytes in the structure.
-
-The
-.I data
-field contains a pointer to an array of
-.I nr
-file descriptors (signed 32 bit integers).
-.I tags
-field should either be 0 or or point to an array of
-.I nr
-"tags" (unsigned 64 bit integers). See
-.B IORING_REGISTER_BUFFERS2
-for more info on resource tagging.
-
-Note that resource updates, e.g.
-.BR IORING_REGISTER_FILES_UPDATE ,
-don't necessarily deallocate resources, they might be held until all requests
-using that resource complete.
-
-Available since 5.13.
-
-.TP
-.B IORING_REGISTER_FILES_UPDATE
-This operation replaces existing files in the registered file set with new
-ones, either turning a sparse entry (one where fd is equal to
-.BR -1 )
-into a real one, removing an existing entry (new one is set to
-.BR -1 ),
-or replacing an existing entry with a new existing entry.
-
-.I arg
-must contain a pointer to a
-.I struct
-.IR io_uring_rsrc_update ,
-which contains
-an offset on which to start the update, and an array of file descriptors to
-use for the update.
-.I nr_args
-must contain the number of descriptors in the passed in array. Available
-since 5.5.
-
-File descriptors can be skipped if they are set to
-.BR IORING_REGISTER_FILES_SKIP .
-Skipping an fd will not touch the file associated with the previous
-fd at that index. Available since 5.12.
-
-.TP
-.B IORING_REGISTER_FILES_UPDATE2
-Similar to
-.BR IORING_REGISTER_FILES_UPDATE ,
-replaces existing files in the
-registered file set with new ones, either turning a sparse entry (one where
-fd is equal to
-.BR -1 )
-into a real one, removing an existing entry (new one is set to
-.BR -1 ),
-or replacing an existing entry with a new existing entry.
-
-.I arg
-must contain a pointer to a
-.I struct
-.IR io_uring_rsrc_update2 ,
-which contains
-an offset on which to start the update, and an array of file descriptors to
-use for the update stored in
-.IR data .
-.I tags
-points to an array of tags.
-.I nr
-must contain the number of descriptors in the passed in arrays.
-See
-.B IORING_REGISTER_BUFFERS2
-for the resource tagging description.
-
-Available since 5.13.
-
-.TP
-.B IORING_UNREGISTER_FILES
-This operation requires no argument, and
-.I arg
-must be passed as NULL. All previously registered files associated
-with the io_uring instance will be unregistered. Available since 5.1.
-
-.TP
-.B IORING_REGISTER_EVENTFD
-It's possible to use
-.BR eventfd (2)
-to get notified of completion events on an
-io_uring instance. If this is desired, an eventfd file descriptor can be
-registered through this operation.
-.I arg
-must contain a pointer to the eventfd file descriptor, and
-.I nr_args
-must be 1. Note that while io_uring generally takes care to avoid spurious
-events, they can occur. Similarly, batched completions of CQEs may only trigger
-a single eventfd notification even if multiple CQEs are posted. The application
-should make no assumptions on number of events being available having a direct
-correlation to eventfd notifications posted. An eventfd notification must thus
-only be treated as a hint to check the CQ ring for completions. Available since
-5.2.
-
-An application can temporarily disable notifications, coming through the
-registered eventfd, by setting the
-.B IORING_CQ_EVENTFD_DISABLED
-bit in the
-.I flags
-field of the CQ ring.
-Available since 5.8.
-
-.TP
-.B IORING_REGISTER_EVENTFD_ASYNC
-This works just like
-.BR IORING_REGISTER_EVENTFD ,
-except notifications are only posted for events that complete in an async
-manner. This means that events that complete inline while being submitted
-do not trigger a notification event. The arguments supplied are the same as
-for
-.BR IORING_REGISTER_EVENTFD .
-Available since 5.6.
-
-.TP
-.B IORING_UNREGISTER_EVENTFD
-Unregister an eventfd file descriptor to stop notifications. Since only one
-eventfd descriptor is currently supported, this operation takes no argument,
-and
-.I arg
-must be passed as NULL and
-.I nr_args
-must be zero. Available since 5.2.
-
-.TP
-.B IORING_REGISTER_PROBE
-This operation returns a structure, io_uring_probe, which contains information
-about the opcodes supported by io_uring on the running kernel.
-.I arg
-must contain a pointer to a struct io_uring_probe, and
-.I nr_args
-must contain the size of the ops array in that probe struct. The ops array
-is of the type io_uring_probe_op, which holds the value of the opcode and
-a flags field. If the flags field has
-.B IO_URING_OP_SUPPORTED
-set, then this opcode is supported on the running kernel. Available since 5.6.
-
-.TP
-.B IORING_REGISTER_PERSONALITY
-This operation registers credentials of the running application with io_uring,
-and returns an id associated with these credentials. Applications wishing to
-share a ring between separate users/processes can pass in this credential id
-in the sqe
-.B personality
-field. If set, that particular sqe will be issued with these credentials. Must
-be invoked with
-.I arg
-set to NULL and
-.I nr_args
-set to zero. Available since 5.6.
-
-.TP
-.B IORING_UNREGISTER_PERSONALITY
-This operation unregisters a previously registered personality with io_uring.
-.I nr_args
-must be set to the id in question, and
-.I arg
-must be set to NULL. Available since 5.6.
-
-.TP
-.B IORING_REGISTER_ENABLE_RINGS
-This operation enables an io_uring ring started in a disabled state
-.RB ( IORING_SETUP_R_DISABLED
-was specified in the call to
-.BR io_uring_setup (2)).
-While the io_uring ring is disabled, submissions are not allowed and
-registrations are not restricted.
-
-After the execution of this operation, the io_uring ring is enabled:
-submissions and registration are allowed, but they will
-be validated following the registered restrictions (if any).
-This operation takes no argument, must be invoked with
-.I arg
-set to NULL and
-.I nr_args
-set to zero. Available since 5.10.
-
-.TP
-.B IORING_REGISTER_RESTRICTIONS
-.I arg
-points to a
-.I struct io_uring_restriction
-array of
-.I nr_args
-entries.
-
-With an entry it is possible to allow an
-.BR io_uring_register (2)
-.IR opcode ,
-or specify which
-.I opcode
-and
-.I flags
-of the submission queue entry are allowed,
-or require certain
-.I flags
-to be specified (these flags must be set on each submission queue entry).
-
-All the restrictions must be submitted with a single
-.BR io_uring_register (2)
-call and they are handled as an allowlist (opcodes and flags not registered,
-are not allowed).
-
-Restrictions can be registered only if the io_uring ring started in a disabled
-state
-.RB ( IORING_SETUP_R_DISABLED
-must be specified in the call to
-.BR io_uring_setup (2)).
-
-Available since 5.10.
-
-.TP
-.B IORING_REGISTER_IOWQ_AFF
-By default, async workers created by io_uring will inherit the CPU mask of its
-parent. This is usually all the CPUs in the system, unless the parent is being
-run with a limited set. If this isn't the desired outcome, the application
-may explicitly tell io_uring what CPUs the async workers may run on.
-.I arg
-must point to a
-.B cpu_set_t
-mask, and
-.I nr_args
-the byte size of that mask.
-
-Available since 5.14.
-
-.TP
-.B IORING_UNREGISTER_IOWQ_AFF
-Undoes a CPU mask previously set with
-.BR IORING_REGISTER_IOWQ_AFF .
-Must not have
-.I arg
-or
-.I nr_args
-set.
-
-Available since 5.14.
-
-.TP
-.B IORING_REGISTER_IOWQ_MAX_WORKERS
-By default, io_uring limits the unbounded workers created to the maximum
-processor count set by
-.I RLIMIT_NPROC
-and the bounded workers is a function of the SQ ring size and the number
-of CPUs in the system. Sometimes this can be excessive (or too little, for
-bounded), and this command provides a way to change the count per ring (per NUMA
-node) instead.
-
-.I arg
-must be set to an
-.I unsigned int
-pointer to an array of two values, with the values in the array being set to
-the maximum count of workers per NUMA node. Index 0 holds the bounded worker
-count, and index 1 holds the unbounded worker count. On successful return, the
-passed in array will contain the previous maximum values for each type. If the
-count being passed in is 0, then this command returns the current maximum values
-and doesn't modify the current setting.
-.I nr_args
-must be set to 2, as the command takes two values.
-
-Available since 5.15.
-
-.TP
-.B IORING_REGISTER_RING_FDS
-Whenever
-.BR io_uring_enter (2)
-is called to submit request or wait for completions, the kernel must grab a
-reference to the file descriptor. If the application using io_uring is threaded,
-the file table is marked as shared, and the reference grab and put of the file
-descriptor count is more expensive than it is for a non-threaded application.
-
-Similarly to how io_uring allows registration of files, this allow registration
-of the ring file descriptor itself. This reduces the overhead of the
-.BR io_uring_enter (2)
-system call.
-
-.I arg
-must be set to a pointer to an array of type
-.I struct io_uring_rsrc_update
-of
-.I nr_args
-number of entries. The
-.B data
-field of this struct must contain an io_uring file descriptor, and the
-.B offset
-field can be either
-.B -1
-or an explicit offset desired for the registered file descriptor value. If
-.B -1
-is used, then upon successful return of this system call, the field will
-contain the value of the registered file descriptor to be used for future
-.BR io_uring_enter (2)
-system calls.
-
-On successful completion of this request, the returned descriptors may be used
-instead of the real file descriptor for
-.BR io_uring_enter (2),
-provided that
-.B IORING_ENTER_REGISTERED_RING
-is set in the
-.I flags
-for the system call. This flag tells the kernel that a registered descriptor
-is used rather than a real file descriptor.
-
-Each thread or process using a ring must register the file descriptor directly
-by issuing this request.
-
-The maximum number of supported registered ring descriptors is currently
-limited to
-.B 16.
-
-Available since 5.18.
-
-.TP
-.B IORING_UNREGISTER_RING_FDS
-Unregister descriptors previously registered with
-.BR IORING_REGISTER_RING_FDS .
-
-.I arg
-must be set to a pointer to an array of type
-.I struct io_uring_rsrc_update
-of
-.I nr_args
-number of entries. Only the
-.B offset
-field should be set in the structure, containing the registered file descriptor
-offset previously returned from
-.B IORING_REGISTER_RING_FDS
-that the application wishes to unregister.
-
-Note that this isn't done automatically on ring exit, if the thread or task
-that previously registered a ring file descriptor isn't exiting. It is
-recommended to manually unregister any previously registered ring descriptors
-if the ring is closed and the task persists. This will free up a registration
-slot, making it available for future use.
-
-Available since 5.18.
-
-.TP
-.B IORING_REGISTER_PBUF_RING
-Registers a shared buffer ring to be used with provided buffers. This is a
-newer alternative to using
-.B IORING_OP_PROVIDE_BUFFERS
-which is more efficient, to be used with request types that support the
-.B IOSQE_BUFFER_SELECT
-flag.
-
-The
-.I arg
-argument must be filled in with the appropriate information. It looks as
-follows:
-.PP
-.in +12n
-.EX
-struct io_uring_buf_reg {
- __u64 ring_addr;
- __u32 ring_entries;
- __u16 bgid;
- __u16 pad;
- __u64 resv[3];
-};
-.EE
-.in
-.PP
-.in +8n
-The
-.I ring_addr
-field must contain the address to the memory allocated to fit this ring.
-The memory must be page aligned and hence allocated appropriately using eg
-.BR posix_memalign (3)
-or similar. The size of the ring is the product of
-.I ring_entries
-and the size of
-.IR "struct io_uring_buf" .
-.I ring_entries
-is the desired size of the ring, and must be a power-of-2 in size. The maximum
-size allowed is 2^15 (32768).
-.I bgid
-is the buffer group ID associated with this ring. SQEs that select a buffer
-have a buffer group associated with them in their
-.I buf_group
-field, and the associated CQEs will have
-.B IORING_CQE_F_BUFFER
-set in their
-.I flags
-member, which will also contain the specific ID of the buffer selected. The rest
-of the fields are reserved and must be cleared to zero.
-
-.I nr_args
-must be set to 1.
-
-Also see
-.BR io_uring_register_buf_ring (3)
-for more details. Available since 5.19.
-
-.TP
-.B IORING_UNREGISTER_PBUF_RING
-Unregister a previously registered provided buffer ring.
-.I arg
-must be set to the address of a struct io_uring_buf_reg, with just the
-.I bgid
-field set to the buffer group ID of the previously registered provided buffer
-group.
-.I nr_args
-must be set to 1. Also see
-.BR IORING_REGISTER_PBUF_RING .
-
-Available since 5.19.
-
-.TP
-.B IORING_REGISTER_SYNC_CANCEL
-Performs a synchronous cancelation request, which works in a similar fashion to
-.B IORING_OP_ASYNC_CANCEL
-except it completes inline. This can be useful for scenarios where cancelations
-should happen synchronously, rather than needing to issue an SQE and wait for
-completion of that specific CQE.
-
-.I arg
-must be set to a pointer to a struct io_uring_sync_cancel_reg structure, with
-the details filled in for what request(s) to target for cancelation. See
-.BR io_uring_register_sync_cancel (3)
-for details on that. The return values are the same, except they are passed
-back synchronously rather than through the CQE
-.I res
-field.
-.I nr_args
-must be set to 1.
-
-Available since 6.0.
-
-.TP
-.B IORING_REGISTER_FILE_ALLOC_RANGE
-sets the allowable range for fixed file index allocations within the
-kernel. When requests that can instantiate a new fixed file are used with
-.BR IORING_FILE_INDEX_ALLOC ,
-the application is asking the kernel to allocate a new fixed file descriptor
-rather than pass in a specific value for one. By default, the kernel will
-pick any available fixed file descriptor within the range available.
-This effectively allows the application to set aside a range just for dynamic
-allocations, with the remainder being used for specific values.
-
-.I nr_args
-must be set to 1 and
-.I arg
-must be set to a pointer to a struct io_uring_file_index_range:
-.PP
-.in +12n
-.EX
-struct io_uring_file_index_range {
- __u32 off;
- __u32 len;
- __u64 resv;
-};
-.EE
-.in
-.PP
-.in +8n
-with
-.I off
-being set to the starting value for the range, and
-.I len
-being set to the number of descriptors. The reserved
-.I resv
-field must be cleared to zero.
-
-The application must have registered a file table first.
-
-Available since 6.0.
-
-.TP
-.B IORING_REGISTER_PBUF_STATUS
-Can be used to retrieve the current head of a ringbuffer provided earlier via
-.BR IORING_REGISTER_PBUF_RING .
-.I arg
-must point to a
-.PP
-.in +12
-.EX
-struct io_uring_buf_status {
- __u32 buf_group; /* input */
- __u32 head; /* output */
- __u32 resv[8];
-};
-.EE
-.in
-.PP
-.in +8
-of which
-.I arg->buf_group
-should contain the buffer group ID for the buffer ring in question,
-.I nr_args
-should be set to 1 and
-.I arg->resv
-should be zeroed out.
-The current head of the ringbuffer will be returned in
-.IR arg->head .
-
-Available since 6.8.
-
-.TP
-.B IORING_REGISTER_NAPI
-Registers a napi instance with the io_uring instance of
-.IR fd .
-.I arg
-should point to a
-.PP
-.in +12
-.EX
-struct io_uring_napi {
- __u32 busy_poll_to;
- __u8 prefer_busy_poll;
- __u8 pad[3];
- __u64 resv;
-};
-.EE
-.in
-.PP
-.in +8
-in which
-.I arg->busy_poll_to
-should contain the busy poll timeout in micro seconds and
-.I arg->prefer_busy_poll
-should specify whether busy polling should be used rather than IRQs.
-.I nr_args
-should be set to 1 and
-.I arg->pad
-and
-.I arg->resv
-should be zeroed out.
-On successful return the
-.I io_uring_napi
-struct pointed to by
-.I arg
-will contain the previously used settings.
-Must be used with a ring initially created with
-.BR IORING_SETUP_IOPOLL .
-
-Available since 6.9.
-
-.TP
-.B IORING_UNREGISTER_NAPI
-Unregisters a napi instance previously registered via
-.B IORING_REGISTER_NAPI
-to the io_uring instance of
-.IR fd .
-.I arg
-should point to a
-.I struct
-.IR io_uring_napi .
-On successful return the
-.I io_uring_napi
-struct pointed to by
-.I arg
-will contain the previously used settings.
-
-Available since 6.9.
-
-.TP
-.B IORING_REGISTER_CLOCK
-Specifies which clock id io_uring will use for timers while waiting for
-completion events with
-.BR IORING_ENTER_GETEVENTS .
-It's only effective if the timeout argument in
-.I struct io_uring_getevents_arg
-is passed, ignored otherwise.
-When used in conjunction with
-.BR IORING_ENTER_ABS_TIMER ,
-interprets the timeout argument as absolute time of the specified clock.
-
-The default clock is
-.BR CLOCK_MONOTONIC .
-
-Available since 6.12 and supports
-.B CLOCK_MONOTONIC
-and
-.BR CLOCK_BOOTTIME .
-
-.TP
-.B IORING_REGISTER_CLONE_BUFFERS
-Supports cloning buffers from a source ring to a destination ring, duplicating
-previously registered buffers from source to destination.
-.IR arg
-must be set to a pointer to a
-.I struct io_uring_clone_buffers
-and
-.IR nr_args
-must be set to
-.B 1 .
-.I struct io_uring_buf_reg
-looks as follows:
-.PP
-.in +12n
-.EX
-struct io_uring_clone_buffers {
- __u32 src_fd;
- __u32 flags;
- __u32 src_off;
- __u32 dst_off;
- __u32 nr;
- __u32 pad[3];
-};
-.EE
-.in
-.TP
-.PP
-where
-.IR src_fd
-indicates the fd of the source ring,
-.IR flags
-are modifier flags for the operation,
-.IR src_off
-indicates the offset from where to start the cloning from the source ring,
-.IR dst_off
-indicates the offset from where to start the cloning into the destination ring,
-and
-.IR nr
-indicates the number of buffers to clone at the given offsets.
-.IR pad
-must be zero filled.
-Kernel 6.12 added support for full range cloning, where
-.IR src_off ,
-.IR dst_off ,
-and
-.IR nr
-must all be set to 0, indicating cloning of the entire table in source to
-destination. Kernel 6.13 added support for specifying the offsets and
-how many buffers to clone. Additionally, it added support for cloning into
-a previously registered table in the destination as well, 6.12 would fail
-that operation with
-.B -EBUSY
-if attempted. To replace existing nodes, or clone into an existing table,
-.B IORING_REGISTER_DST_REPLACE
-must be set in the
-.IR flags
-member.
-
-.TP
-.B IORING_REGISTER_SEND_MSG_RING
-Supports sending of the equivalent of a
-.B IORING_OP_MSG_RING
-request, but without having a source ring available. Takes a pointer to a
-.IR struct io_uring_sqe
-which must be prepared with
-.BR io_uring_prep_msg_ring (3)
-before being submitted. Only supports
-.B IORING_MSG_DATA
-type of requests. Available since kernel 6.13.
-
-.TP
-.B IORING_REGISTER_RESIZE_RINGS
-Supports resizing the SQ and CQ rings. Takes a pointer to a
-.IR struct io_uring_params
-as the argument, where
-.IR sq_entries
-and
-.IR cq_entries
-may be set to the desired values. Only supports a limited set of flags set
-in the
-.IR struct io_uring_params
-argument, notably
-.B IORING_SETUP_CQSIZE
-and
-.B IORING_SETUP_CLAMP
-to modify the CQ ring sizing. See
-.BR io_uring_resize_rings (3)
-for details. Note that while liburing takes care of the ring unmap and mapping
-for a resize operation, manual users of this register syscall must perform
-those operations, similarly to when a new ring is created. The
-.IR struct io_uring_params
-structure will get the necessary offsets copied back upon successful completion
-of this system call, which can be used to memory map the ring just like how
-a new ring would've been mapped. Available since kernel 6.13.
-
-.TP
-.B IORING_REGISTER_MEM_REGION
-Supports registering multiple purposes memory regions, avoiding unnecessary
-copying in of
-.IR struct io_uring_getevents_arg
-for wait operations that specify a timeout or minimum timeout. Takes a pointer
-to a
-.IR struct io_uring_mem_region_reg
-structure, which looks as follows:
-.PP
-.in +12n
-.EX
-struct io_uring_mem_region_reg {
- __u64 region_uptr;
- __u64 flags;
- __u64 __resv[2];
-};
-.EE
-.in
-.TP
-.PP
-where
-.IR region_uptr
-must be set to the region being registered as memory regions,
-.IR flags
-specifies modifier flags (must currently be
-.B IORING_MEM_REGION_REG_WAIT_ARG ). The pad fields must all be cleared to
-.B 0 .
-Each memory regions looks as follows:
-.PP
-.in +12n
-.EX
-struct io_uring_region_desc {
- __u64 user_addr;
- __u64 size;
- __u32 flags;
- __u32 id;
- __u64 mmap_offset;
- __u64 __resv[4];
-};
-.EE
-.in
-.TP
-.PP
-where
-.IR user_addr
-points to userspace memory mappings,
-.IR size
-is the size of userspace memory. Current supported userspace memory regions
-looks as follows:
-.PP
-.in +12n
-.EX
-struct io_uring_reg_wait {
- struct __kernel_timespec ts;
- __u32 min_wait_usec;
- __u32 flags;
- __u64 sigmask;
- __u32 sigmask_sz;
- __u32 pad[3];
- __u64 pad2[2];
-};
-.EE
-.in
-.TP
-.PP
-where
-.IR ts
-holds the timeout information for this region
-.IR flags
-holds information about the timeout region,
-.IR sigmask
-is a pointer to a signal mask, if used, and
-.IR sigmask_sz
-is the size of that signal mask. The pad fields must all be cleared to
-.B 0 .
-Currently the only valid flag is
-.B IORING_REG_WAIT_TS ,
-which, if set, says that the values in
-.IR ts
-are valid and should be used for a timeout operation. The
-.IR user_addr
-field of
-.IR struct io_uring_region_desc
-must be set to an address of
-.IR struct io_uring_reg_wait
-members, an up to a page size can be mapped. At the size of 64 bytes per
-region, that allows at least 64 individual regions on a 4k page size system.
-The offsets of these regions are used for an
-.BR io_uring_enter (2)
-system call, with the first one being 0, second one 1, and so forth. After
-registration of the wait regions,
-.BR io_uring_enter (2)
-may be used with the enter flag of
-.B IORING_ENTER_EXT_ARG_REG and an
-.IR argp
-set to the wait region offset, rather than a pointer to a
-.IR struct io_uring_getevent_arg
-structure. If used with
-.B IORING_ENTER_GETEVENTS ,
-then the wait operation will use the information in the registered wait
-region rather than needing a io_uring_getevent_arg structure copied for each
-operation. For high frequency waits, this can save considerable CPU cycles.
-Note: once a region has been registered, it cannot get unregistered. It lives
-for the life of the ring. Individual wait region offset may be modified before
-any
-.BR io_uring_enter (2)
-system call. Available since kernel 6.13.
-
-.SH RETURN VALUE
-On success,
-.BR io_uring_register (2)
-returns either 0 or a positive value, depending on the
-.I opcode
-used. On error, a negative error value is returned. The caller should not rely
-on the
-.I errno
-variable.
-
-.SH ERRORS
-.TP
-.B EACCES
-The
-.I opcode
-field is not allowed due to registered restrictions.
-.TP
-.B EBADF
-One or more fds in the
-.I fd
-array are invalid.
-.TP
-.B EBADFD
-.B IORING_REGISTER_ENABLE_RINGS
-or
-.B IORING_REGISTER_RESTRICTIONS
-was specified, but the io_uring ring is not disabled.
-.TP
-.B EBUSY
-.B IORING_REGISTER_BUFFERS
-or
-.B IORING_REGISTER_FILES
-or
-.B IORING_REGISTER_RESTRICTIONS
-was specified, but there were already buffers, files, or restrictions
-registered.
-.TP
-.B EEXIST
-The thread performing the registration is invalid.
-.TP
-.B EFAULT
-buffer is outside of the process' accessible address space, or
-.I iov_len
-is greater than 1GiB.
-.TP
-.B EINVAL
-.B IORING_REGISTER_BUFFERS
-or
-.B IORING_REGISTER_FILES
-was specified, but
-.I nr_args
-is 0.
-.TP
-.B EINVAL
-.B IORING_REGISTER_BUFFERS
-was specified, but
-.I nr_args
-exceeds
-.B UIO_MAXIOV
-.TP
-.B EINVAL
-.B IORING_UNREGISTER_BUFFERS
-or
-.B IORING_UNREGISTER_FILES
-was specified, and
-.I nr_args
-is non-zero or
-.I arg
-is non-NULL.
-.TP
-.B EINVAL
-.B IORING_REGISTER_RESTRICTIONS
-was specified, but
-.I nr_args
-exceeds the maximum allowed number of restrictions or restriction
-.I opcode
-is invalid.
-.TP
-.B EMFILE
-.B IORING_REGISTER_FILES
-was specified and
-.I nr_args
-exceeds the maximum allowed number of files in a fixed file set.
-.TP
-.B EMFILE
-.B IORING_REGISTER_FILES
-was specified and adding
-.I nr_args
-file references would exceed the maximum allowed number of files the user
-is allowed to have according to the
-.B RLIMIT_NOFILE
-resource limit and the caller does not have
-.B CAP_SYS_RESOURCE
-capability. Note that this is a per user limit, not per process.
-.TP
-.B ENOMEM
-Insufficient kernel resources are available, or the caller had a
-non-zero
-.B RLIMIT_MEMLOCK
-soft resource limit, but tried to lock more memory than the limit
-permitted. This limit is not enforced if the process is privileged
-.RB ( CAP_IPC_LOCK ).
-.TP
-.B ENXIO
-.B IORING_UNREGISTER_BUFFERS
-or
-.B IORING_UNREGISTER_FILES
-was specified, but there were no buffers or files registered.
-.TP
-.B ENXIO
-Attempt to register files or buffers on an io_uring instance that is already
-undergoing file or buffer registration, or is being torn down.
-.TP
-.B EOPNOTSUPP
-User buffers point to file-backed memory.
-.TP
-.B EFAULT
-User buffers point to file-backed memory (newer kernels).
-.TP
-.B ENOENT
-.B IORING_REGISTER_PBUF_STATUS
-was specified, but
-.I buf_group
-did not refer to a currently valid buffer group.
-.TP
-.B EINVAL
-.B IORING_REGISTER_PBUF_STATUS
-was specified, but the valid buffer group specified by
-.I buf_group
-did not refer to a buffer group registered via
-.BR IORING_REGISTER_PBUF_RING .
-.TP
-.B EINVAL
-.B IORING_REGISTER_NAPI
-was specified, but the ring associated with
-.I fd
-has not been created with
-.BR IORING_SETUP_IOPOLL .
diff --git a/src/liburing/man/io_uring_register_buf_ring.3 b/src/liburing/man/io_uring_register_buf_ring.3
deleted file mode 100644
index f7265a7572f7..000000000000
--- a/src/liburing/man/io_uring_register_buf_ring.3
+++ /dev/null
@@ -1,157 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_register_buf_ring 3 "May 18, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_register_buf_ring \- register buffer ring for provided buffers
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_register_buf_ring(struct io_uring *" ring ",
-.BI " struct io_uring_buf_reg *" reg ",
-.BI " unsigned int " flags ");"
-.BI "
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_register_buf_ring (3)
-function registers a shared buffer ring to be used with provided buffers. For
-the request types that support it, provided buffers are given to the ring and
-one is selected by a request if it has
-.B IOSQE_BUFFER_SELECT
-set in the SQE
-.IR flags ,
-when the request is ready to receive data. This allows both clear ownership
-of the buffer lifetime, and a way to have more read/receive type of operations
-in flight than buffers available.
-
-The
-.I reg
-argument must be filled in with the appropriate information. It looks as
-follows:
-.PP
-.in +4n
-.EX
-struct io_uring_buf_reg {
- __u64 ring_addr;
- __u32 ring_entries;
- __u16 bgid;
- __u16 pad;
- __u64 resv[3];
-};
-.EE
-.in
-.PP
-The
-.I ring_addr
-field must contain the address to the memory allocated to fit this ring.
-The memory must be page aligned and hence allocated appropriately using eg
-.BR posix_memalign (3)
-or similar. The size of the ring is the product of
-.I ring_entries
-and the size of
-.IR "struct io_uring_buf" .
-.I ring_entries
-is the desired size of the ring, and must be a power-of-2 in size. The maximum
-size allowed is 2^15 (32768).
-.I bgid
-is the buffer group ID associated with this ring. SQEs that select a buffer
-have a buffer group associated with them in their
-.I buf_group
-field, and the associated CQEs will have
-.B IORING_CQE_F_BUFFER
-set in their
-.I flags
-member, which will also contain the specific ID of the buffer selected. The rest
-of the fields are reserved and must be cleared to zero.
-
-The
-.I flags
-argument can be set to one of the following values:
-.TP
-.B IOU_PBUF_RING_INC
-The buffers in this ring can be incrementally consumed. With partial
-consumption, each completion of a given buffer ID will continue where the
-previous one left off, or from the start if no completions have been seen yet.
-When more completions should be expected for a given buffer ID, the CQE will
-have
-.B IORING_CQE_F_BUF_MORE
-set in the
-.I flags
-member. Available since 6.12.
-.PP
-
-A shared buffer ring looks as follows:
-.PP
-.in +4n
-.EX
-struct io_uring_buf_ring {
- union {
- struct {
- __u64 resv1;
- __u32 resv2;
- __u16 resv3;
- __u16 tail;
- };
- struct io_uring_buf bufs[0];
- };
-};
-.EE
-.in
-.PP
-where
-.I tail
-is the index at which the application can insert new buffers for consumption
-by requests, and
-.I struct io_uring_buf
-is buffer definition:
-.PP
-.in +4n
-.EX
-struct io_uring_buf {
- __u64 addr;
- __u32 len;
- __u16 bid;
- __u16 resv;
-};
-.EE
-.in
-.PP
-where
-.I addr
-is the address for the buffer,
-.I len
-is the length of the buffer in bytes, and
-.I bid
-is the buffer ID that will be returned in the CQE once consumed.
-
-Reserved fields must not be touched. Applications must use
-.BR io_uring_buf_ring_init (3)
-to initialise the buffer ring before use. Applications may use
-.BR io_uring_buf_ring_add (3)
-and
-.BR io_uring_buf_ring_advance (3)
-or
-.BR io_uring_buf_ring_cq_advance (3)
-to provide buffers, which will set these fields and update the tail.
-
-Available since 5.19.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_register_buf_ring (3)
-returns 0. On failure it returns
-.BR -errno .
-.SH NOTES
-Unless manual setup is needed, it's recommended to use
-.BR io_uring_setup_buf_ring (3)
-as it provides a simpler way to setup a provided buffer ring.
-.SH SEE ALSO
-.BR io_uring_buf_ring_init (3),
-.BR io_uring_buf_ring_add (3),
-.BR io_uring_setup_buf_ring (3),
-.BR io_uring_buf_ring_advance (3),
-.BR io_uring_buf_ring_cq_advance (3)
diff --git a/src/liburing/man/io_uring_register_buffers.3 b/src/liburing/man/io_uring_register_buffers.3
deleted file mode 100644
index dfb292da26f8..000000000000
--- a/src/liburing/man/io_uring_register_buffers.3
+++ /dev/null
@@ -1,105 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_register_buffers 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_register_buffers \- register buffers for fixed buffer operations
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_register_buffers(struct io_uring *" ring ","
-.BI " const struct iovec *" iovecs ","
-.BI " unsigned " nr_iovecs ");"
-.PP
-.BI "int io_uring_register_buffers_tags(struct io_uring *" ring ","
-.BI " const struct iovec *" iovecs ","
-.BI " const __u64 *" tags ","
-.BI " unsigned " nr ");"
-.PP
-.BI "int io_uring_register_buffers_sparse(struct io_uring *" ring ","
-.BI " unsigned " nr_iovecs ");"
-.PP
-.BI "int io_uring_register_buffers_update_tag(struct io_uring *" ring ","
-.BI " unsigned " off ","
-.BI " const struct iovec *" iovecs ","
-.BI " const __u64 *" tags ","
-.BI " unsigned " nr ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_register_buffers (3)
-function registers
-.I nr_iovecs
-number of buffers defined by the array
-.I iovecs
-belonging to the
-.IR ring .
-
-The
-.BR io_uring_register_buffers_tags (3)
-function behaves the same as
-.BR io_uring_register_buffers (3)
-function but additionally takes
-.I tags
-parameter. See
-.B IORING_REGISTER_BUFFERS2
-for the resource tagging description.
-
-The
-.BR io_uring_register_buffers_sparse (3)
-function registers
-.I nr_iovecs
-empty buffers belonging to the
-.IR ring .
-These buffers must be updated before use, using eg
-.BR io_uring_register_buffers_update_tag (3).
-
-After the caller has registered the buffers, they can be used with one of the
-fixed buffers functions.
-
-Registered buffers is an optimization that is useful in conjunction with
-.B O_DIRECT
-reads and writes, where it maps the specified range into the kernel once when
-the buffer is registered rather than doing a map and unmap for each IO
-every time IO is performed to that region. Additionally, it also avoids
-manipulating the page reference counts for each IO.
-
-The
-.BR io_uring_register_buffers_update_tag (3)
-function updates registered buffers with new ones, either turning a sparse
-entry into a real one, or replacing an existing entry. The
-.I off
-is offset on which to start the update
-.I nr
-number of buffers defined by the array
-.I iovecs
-belonging to the
-.IR ring .
-The
-.I tags
-points to an array of tags. See
-.B IORING_REGISTER_BUFFERS2
-for the resource tagging description.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_register_buffers (3),
-.BR io_uring_register_buffers_tags (3)
-and
-.BR io_uring_register_buffers_sparse (3)
-return 0.
-.BR io_uring_register_buffers_update_tag (3)
-return number of buffers updated.
-On failure they return
-.BR -errno .
-.SH SEE ALSO
-.BR io_uring_register (2),
-.BR io_uring_get_sqe (3),
-.BR io_uring_unregister_buffers (3),
-.BR io_uring_clone_buffers (3),
-.BR io_uring_register_buf_ring (3),
-.BR io_uring_prep_read_fixed (3),
-.BR io_uring_prep_write_fixed (3)
diff --git a/src/liburing/man/io_uring_register_buffers_sparse.3 b/src/liburing/man/io_uring_register_buffers_sparse.3
deleted file mode 120000
index 1019ce4fa16f..000000000000
--- a/src/liburing/man/io_uring_register_buffers_sparse.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_register_buffers.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_register_buffers_tags.3 b/src/liburing/man/io_uring_register_buffers_tags.3
deleted file mode 120000
index 1019ce4fa16f..000000000000
--- a/src/liburing/man/io_uring_register_buffers_tags.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_register_buffers.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_register_buffers_update_tag.3 b/src/liburing/man/io_uring_register_buffers_update_tag.3
deleted file mode 120000
index 1019ce4fa16f..000000000000
--- a/src/liburing/man/io_uring_register_buffers_update_tag.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_register_buffers.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_register_clock.3 b/src/liburing/man/io_uring_register_clock.3
deleted file mode 100644
index 56ed1ac2bcb5..000000000000
--- a/src/liburing/man/io_uring_register_clock.3
+++ /dev/null
@@ -1,72 +0,0 @@
-.\" Copyright (C) 2024 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_register_clock 3 "Aug 18, 2024" "liburing-2.8" "liburing Manual"
-.SH NAME
-io_uring_register_clock \- set clock source for event waiting
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_register_clock(struct io_uring *" ring ",
-.BI " struct io_uring_clock_register *" arg ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_register_clock (3)
-function registers which clock source should be used by io_uring, when an
-application waits for event completions. The
-.IR ring
-argument should point to the ring in question, and the
-.IR arg
-argument should be a pointer to a
-.B struct io_uring_clock_register .
-
-The
-.IR arg
-argument must be filled in with the appropriate information. It looks as
-follows:
-.PP
-.in +4n
-.EX
-struct io_uring_clock_register {
- __u32 clockid;
- __u32 __resv[3];
-};
-.EE
-.in
-.PP
-The
-.I clockid
-field must contain the clock source, with valid sources being:
-.TP
-.B CLOCK_MONOTONIC
-a nonsettable system-wide clock that represents monotonic time.
-.TP
-.B CLOCK_BOOTTIME
-A nonsettable system-wide clock that is identical to
-.B CLOCK_MONOTONIC ,
-except that is also icnludes any time that the system is suspended.
-.PP
-See
-.BR clock_gettime (3)
-for more details.
-
-The
-.I __resv
-fields must be filled with zeroes.
-
-Available since 6.12.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_register_clock (3)
-returns 0. On failure it returns
-.BR -errno .
-.SH SEE ALSO
-.BR clock_gettime (3),
-.BR io_uring_register (2),
-.BR io_uring_wait_cqe (3),
-.BR io_uring_wait_cqe_timeout (3),
diff --git a/src/liburing/man/io_uring_register_eventfd.3 b/src/liburing/man/io_uring_register_eventfd.3
deleted file mode 100644
index d7b23ee417d9..000000000000
--- a/src/liburing/man/io_uring_register_eventfd.3
+++ /dev/null
@@ -1,50 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_register_eventfd 3 "April 16, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_register_eventfd \- register an eventfd with a ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_register_eventfd(struct io_uring *" ring ","
-.BI " int " fd ");"
-.PP
-.BI "int io_uring_register_eventfd_async(struct io_uring *" ring ","
-.BI " int " fd ");"
-.PP
-.BI "int io_uring_unregister_eventfd(struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-.BR io_uring_register_eventfd (3)
-registers the eventfd file descriptor
-.I fd
-with the ring identified by
-.IR ring .
-
-Whenever completions are posted to the CQ ring, an eventfd notification
-is generated with the registered eventfd descriptor. If
-.BR io_uring_register_eventfd_async (3)
-is used, only events that completed out-of-line will trigger a notification.
-
-It notifications are no longer desired,
-.BR io_uring_unregister_eventfd (3)
-may be called to remove the eventfd registration. No eventfd argument is
-needed, as a ring can only have a single eventfd registered.
-
-.SH NOTES
-While io_uring generally takes care to avoid spurious events, they can occur.
-Similarly, batched completions of CQEs may only trigger a single eventfd
-notification even if multiple CQEs are posted. The application should make no
-assumptions on number of events being available having a direct correlation to
-eventfd notifications posted. An eventfd notification must thus only be treated
-as a hint to check the CQ ring for completions.
-.SH RETURN VALUE
-Returns 0 on success, or
-.BR -errno
-on error.
-.SH SEE ALSO
-.BR eventfd (2)
diff --git a/src/liburing/man/io_uring_register_eventfd_async.3 b/src/liburing/man/io_uring_register_eventfd_async.3
deleted file mode 120000
index 665995711bf2..000000000000
--- a/src/liburing/man/io_uring_register_eventfd_async.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_register_eventfd.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_register_file_alloc_range.3 b/src/liburing/man/io_uring_register_file_alloc_range.3
deleted file mode 100644
index 239ea7d67b93..000000000000
--- a/src/liburing/man/io_uring_register_file_alloc_range.3
+++ /dev/null
@@ -1,52 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_register_file_alloc_range 3 "Oct 21, 2022" "liburing-2.3" "liburing Manual"
-.SH NAME
-io_uring_register_file_alloc_range \- set range for fixed file allocations
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_register_file_alloc_range(struct io_uring *" ring ",
-.BI " unsigned " off ","
-.BI " unsigned " len ");"
-.BI "
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_register_file_alloc_range (3)
-function sets the allowable range for fixed file index allocations within the
-kernel. When requests that can instantiate a new fixed file are used with
-.B IORING_FILE_INDEX_ALLOC ,
-the application is asking the kernel to allocate a new fixed file descriptor
-rather than pass in a specific value for one. By default, the kernel will
-pick any available fixed file descriptor within the range available. Calling
-this function with
-.I off
-set to the starting offset and
-.I len
-set to the number of descriptors, the application can limit the allocated
-descriptors to that particular range. This effectively allows the application
-to set aside a range just for dynamic allocations, with the remainder being
-used for specific values.
-
-The application must have registered a fixed file table upfront, eg through
-.BR io_uring_register_files (3)
-or
-.BR io_uring_register_files_sparse (3) .
-
-Available since 6.0.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_register_file_alloc_range (3)
-returns 0. On failure it returns
-.BR -errno .
-.SH SEE ALSO
-.BR io_uring_register_files (3)
-.BR io_uring_prep_accept_direct (3)
-.BR io_uring_prep_openat_direct (3)
-.BR io_uring_prep_socket_direct (3)
diff --git a/src/liburing/man/io_uring_register_files.3 b/src/liburing/man/io_uring_register_files.3
deleted file mode 100644
index c7f73e922b40..000000000000
--- a/src/liburing/man/io_uring_register_files.3
+++ /dev/null
@@ -1,120 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_register_files 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_register_files \- register file descriptors
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_register_files(struct io_uring *" ring ","
-.BI " const int *" files ","
-.BI " unsigned " nr_files ");"
-.PP
-.BI "int io_uring_register_files_tags(struct io_uring *" ring ","
-.BI " const int *" files ","
-.BI " const __u64 *" tags ","
-.BI " unsigned " nr ");"
-.PP
-.BI "int io_uring_register_files_sparse(struct io_uring *" ring ","
-.BI " unsigned " nr_files ");"
-.PP
-.BI "int io_uring_register_files_update(struct io_uring *" ring ","
-.BI " unsigned " off ","
-.BI " const int *" files ","
-.BI " unsigned " nr_files ");"
-.PP
-.BI "int io_uring_register_files_update_tag(struct io_uring *" ring ","
-.BI " unsigned " off ","
-.BI " const int *" files ","
-.BI " const __u64 *" tags ","
-.BI " unsigned " nr_files ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_register_files (3)
-function registers
-.I nr_files
-number of file descriptors defined by the array
-.I files
-belonging to the
-.I ring
-for subsequent operations.
-
-The
-.BR io_uring_register_files_tags (3)
-function behaves the same as
-.BR io_uring_register_files (3)
-function but additionally takes
-.I tags
-parameter. See
-.B IORING_REGISTER_BUFFERS2
-for the resource tagging description.
-
-The
-.BR io_uring_register_files_sparse (3)
-function registers an empty file table of
-.I nr_files
-number of file descriptors. These files must be updated before use, using eg
-.BR io_uring_register_files_update_tag (3).
-Note that if the size of the sparse table exceeds what
-.B RLIMIT_NOFILE
-allows, then
-.BR io_uring_register_files_sparse (3)
-will attempt to raise the limit using
-.B setrlimit (2)
-and retry the operation. If the registration fails after doing that, then an
-error will be returned.
-The sparse variant is available in kernels 5.19 and later.
-
-Registering a file table is a prerequisite for using any request that uses
-direct descriptors.
-
-Registered files have less overhead per operation than normal files. This
-is due to the kernel grabbing a reference count on a file when an operation
-begins, and dropping it when it's done. When the process file table is
-shared, for example if the process has ever created any threads, then this
-cost goes up even more. Using registered files reduces the overhead of
-file reference management across requests that operate on a file.
-
-The
-.BR io_uring_register_files_update (3)
-function updates existing registered files. The
-.I off
-is offset on which to start the update
-.I nr_files
-number of files defined by the array
-.I files
-belonging to the
-.IR ring .
-
-The
-.BR io_uring_register_files_update_tag (3)
-function behaves the same as
-.BR io_uring_register_files_update (3)
-function but additionally takes
-.I tags
-parameter. See
-.B IORING_REGISTER_BUFFERS2
-for the resource tagging description.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_register_files (3),
-.BR io_uring_register_files_tags (3)
-and
-.BR io_uring_register_files_sparse (3)
-return 0.
-.BR io_uring_register_files_update (3)
-and
-.BR io_uring_register_files_update_tag (3)
-return number of files updated.
-On failure they return
-.BR -errno .
-.SH SEE ALSO
-.BR io_uring_register (2),
-.BR io_uring_get_sqe (3),
-.BR io_uring_unregister_files (3)
diff --git a/src/liburing/man/io_uring_register_files_sparse.3 b/src/liburing/man/io_uring_register_files_sparse.3
deleted file mode 120000
index db38b932776b..000000000000
--- a/src/liburing/man/io_uring_register_files_sparse.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_register_files.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_register_files_tags.3 b/src/liburing/man/io_uring_register_files_tags.3
deleted file mode 120000
index db38b932776b..000000000000
--- a/src/liburing/man/io_uring_register_files_tags.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_register_files.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_register_files_update.3 b/src/liburing/man/io_uring_register_files_update.3
deleted file mode 120000
index db38b932776b..000000000000
--- a/src/liburing/man/io_uring_register_files_update.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_register_files.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_register_files_update_tag.3 b/src/liburing/man/io_uring_register_files_update_tag.3
deleted file mode 120000
index db38b932776b..000000000000
--- a/src/liburing/man/io_uring_register_files_update_tag.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_register_files.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_register_iowq_aff.3 b/src/liburing/man/io_uring_register_iowq_aff.3
deleted file mode 100644
index 686222c13bea..000000000000
--- a/src/liburing/man/io_uring_register_iowq_aff.3
+++ /dev/null
@@ -1,67 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_register_iowq_aff 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_register_iowq_aff \- register async worker CPU affinities
-.SH SYNOPSIS
-.nf
-.B #include <sched.h>
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_register_iowq_aff(struct io_uring *" ring ","
-.BI " size_t " cpusz ","
-.BI " const cpu_set_t *" mask ");
-.PP
-.BI "void io_uring_unregister_iowq_aff(struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_prep_register_iowq_aff (3)
-function registers a set of CPU affinities to be used by the io_uring async
-workers. By default, io_uring async workers are allowed to run on any CPU in
-the system. If this function is called with
-.I ring
-set to the ring in question and
-.I mask
-set to a pointer to a
-.B cpu_set_t
-value and
-.I cpusz
-set to the size of the CPU set, then async workers will only be allowed to run
-on the CPUs specified in the mask. Existing workers may need to hit a schedule
-point before they are migrated.
-
-For unregistration,
-.BR io_uring_unregister_iowq_aff (3)
-may be called to restore CPU affinities to the default.
-
-Applications must define
-.B _GNU_SOURCE
-to obtain the definition of this helper, as
-.I cpu_set_t
-will not be defined without it.
-
-.SH RETURN VALUE
-Returns
-.B 0
-on success, or any of the following values in case of error.
-.TP
-.B -EFAULT
-The kernel was unable to copy the memory pointer to by
-.I mask
-as it was invalid.
-.TP
-.B -ENOMEM
-The kernel was unable to allocate memory for the new CPU mask.
-.TP
-.B -EINVAL
-.I cpusz
-or
-.I mask
-was NULL/0, or any other value specified was invalid.
-.SH SEE ALSO
-.BR io_uring_queue_init (3),
-.BR io_uring_register (2)
diff --git a/src/liburing/man/io_uring_register_iowq_max_workers.3 b/src/liburing/man/io_uring_register_iowq_max_workers.3
deleted file mode 100644
index 2557e2168852..000000000000
--- a/src/liburing/man/io_uring_register_iowq_max_workers.3
+++ /dev/null
@@ -1,71 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_register_iowq_max_workers 3 "March 13, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_register_iowq_max_workers \- modify the maximum allowed async workers
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_register_iowq_max_workers(struct io_uring *" ring ","
-.BI " unsigned int *" values ");"
-.fi
-.SH DESCRIPTION
-.PP
-io_uring async workers are split into two types:
-.TP
-.B Bounded
-These workers have a bounded execution time. Examples of that are filesystem
-reads, which normally complete in a relatively short amount of time. In case
-of disk failures, they are still bounded by a timeout operation that will
-abort them if exceeded.
-.TP
-.B Unbounded
-Work items here may take an indefinite amount of time to complete. Examples
-include doing IO to sockets, pipes, or any other non-regular type of file.
-
-.PP
-By default, the amount of bounded IO workers is limited to how many SQ entries
-the ring was setup with, or 4 times the number of online CPUs in the system,
-whichever is smaller. Unbounded workers are only limited by the process task
-limit, as indicated by the rlimit
-.B RLIMIT_NPROC
-limit.
-
-This can be modified by calling
-.B io_uring_register_iowq_max_workers
-with
-.I ring
-set to the ring in question, and
-.I values
-pointing to an array of two values. The first element should contain the number
-of desired bounded workers, and the second element should contain the number
-of desired unbounded workers. These are both maximum values, io_uring will
-not maintain a high count of idle workers, they are reaped when they are not
-necessary anymore.
-
-If called with both values set to 0, the existing values are returned.
-
-.SH RETURN VALUE
-Returns
-.B 0
-on success, with
-.I values
-containing the previous values for the settings. On error, any of the following
-may be returned.
-.TP
-.B -EFAULT
-The kernel was unable to copy the memory pointer to by
-.I values
-as it was invalid.
-.TP
-.B -EINVAL
-.I values
-was
-.B NULL
-or the new values exceeded the maximum allowed value.
-.SH SEE ALSO
-.BR io_uring_queue_init (3),
-.BR io_uring_register (2)
diff --git a/src/liburing/man/io_uring_register_napi.3 b/src/liburing/man/io_uring_register_napi.3
deleted file mode 100644
index 6ce8cfff39fd..000000000000
--- a/src/liburing/man/io_uring_register_napi.3
+++ /dev/null
@@ -1,40 +0,0 @@
-.\" Copyright (C) 2022 Stefan Roesch <shr@devkernel.io>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_register_napi 3 "November 16, 2022" "liburing-2.4" "liburing Manual"
-.SH NAME
-io_uring_register_napi \- register NAPI busy poll settings
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_register_napi(struct io_uring *" ring ","
-.BI " struct io_uring_napi *" napi)
-.PP
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_register_napi (3)
-function registers the NAPI settings for subsequent operations. The NAPI
-settings are specified in the structure that is passed in the
-.I napi
-parameter. The structure consists of the napi timeout
-.I busy_poll_to
-(napi busy poll timeout in us) and
-.IR prefer_busy_poll .
-
-Registering a NAPI settings sets the mode when calling the function
-napi_busy_loop and corresponds to the SO_PREFER_BUSY_POLL socket
-option.
-
-NAPI busy poll can reduce the network roundtrip time.
-
-
-.SH RETURN VALUE
-On success
-.BR io_uring_register_napi (3)
-return 0. On failure they return
-.BR -errno .
-It also updates the napi structure with the current values.
diff --git a/src/liburing/man/io_uring_register_reg_wait.3 b/src/liburing/man/io_uring_register_reg_wait.3
deleted file mode 100644
index a9ca0bb94cab..000000000000
--- a/src/liburing/man/io_uring_register_reg_wait.3
+++ /dev/null
@@ -1,62 +0,0 @@
-.\" Copyright (C) 2024 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_register_reg_wait 3 "November 2, 2024" "liburing-2.9" "liburing Manual"
-.SH NAME
-io_uring_register_reg_wait \- Registers fixed wait regions
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_register_reg_wait(struct io_uring *" ring ","
-.BI " struct io_uring_reg_wait *"reg ","
-.BI " int "nr ");"
-.PP
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_register_reg_wait (3)
-registers a fixed wait region starting at
-.IR reg
-and of
-.IR nentries
-entries with the ring indicated by
-.IR ring .
-
-This function works like
-.BR io_uring_setup_reg_wait (3) ,
-except it doesn't allocate any memory on behalf of the application. The
-application must pass in previously allocated memory in
-.IR reg ,
-which must be of the right size to hold
-.IR nr
-entries and suitably aligned on a page boundary.
-
-The memory registered should not be freed until the ring for which it is
-registered is closed.
-
-Once a wait region has been setup, it persists for the life time of the ring.
-It's currently not possible to unregister or resize a wait region.
-Additionally, a wait region may currently only use a single page of memory.
-On a 4k page size system, this means an application is limited to
-.B 64
-wait regions. That should be enough, as each wait index may be modified as
-needed. With at least 64 indices available, hopefully applications can just
-use the appropriately setup wait region for each specific type of wait, with
-different indices having different wait settings.
-
-Available since kernel 6.13.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_register_reg_wait (3)
-returns
-.B 0 .
-On failure, it returns a
-.BR -errno
-value.
-.SH SEE ALSO
-.BR io_uring_submit_and_wait_reg (3),
-.BR io_uring_setup_reg_wait (3)
diff --git a/src/liburing/man/io_uring_register_ring_fd.3 b/src/liburing/man/io_uring_register_ring_fd.3
deleted file mode 100644
index 0284fe415744..000000000000
--- a/src/liburing/man/io_uring_register_ring_fd.3
+++ /dev/null
@@ -1,51 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_register_ring_fd 3 "March 11, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_register_ring_fd \- register a ring file descriptor
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_register_ring_fd(struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-.BR io_uring_register_ring_fd (3)
-registers the file descriptor of the ring.
-
-Whenever
-.BR io_uring_enter (2)
-is called to submit request or wait for completions, the kernel must grab a
-reference to the file descriptor. If the application using io_uring is threaded,
-the file table is marked as shared, and the reference grab and put of the file
-descriptor count is more expensive than it is for a non-threaded application.
-
-Similarly to how io_uring allows registration of files, this allow registration
-of the ring file descriptor itself. This reduces the overhead of the
-.BR io_uring_enter (2)
-system call.
-
-If an application using liburing is threaded, then an application should call
-this function to register the ring descriptor when a ring is set up. See NOTES
-for restrictions when a ring is shared.
-
-Available since kernel 5.18.
-
-.SH NOTES
-When the ring descriptor is registered, it is stored internally in the
-.I struct io_uring
-structure. For applications that share a ring between threads, for example
-having one thread do submits and another reap events, then this optimization
-cannot be used as each thread may have a different index for the registered
-ring fd.
-.SH RETURN VALUE
-Returns 1 on success, indicating that one file descriptor was registered,
-or
-.BR -errno
-on error.
-.SH SEE ALSO
-.BR io_uring_unregister_ring_fd (3),
-.BR io_uring_register_files (3)
diff --git a/src/liburing/man/io_uring_register_sync_cancel.3 b/src/liburing/man/io_uring_register_sync_cancel.3
deleted file mode 100644
index 449bc0ff9ef8..000000000000
--- a/src/liburing/man/io_uring_register_sync_cancel.3
+++ /dev/null
@@ -1,73 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_register_sync_cancel 3 "September 21, 2022" "liburing-2.3" "liburing Manual"
-.SH NAME
-io_uring_register_sync_cancel \- issue a synchronous cancelation request
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_register_sync_cancel(struct io_uring *" ring ",
-.BI " struct io_uring_sync_cancel_reg *" reg ");
-.PP
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_register_sync_cancel (3)
-function performs a synchronous cancelation request based on the parameters
-specified in
-.I reg .
-
-The
-.I reg
-argument must be filled in with the appropriate information for the
-cancelation request. It looks as follows:
-.PP
-.in +4n
-.EX
-struct io_uring_sync_cancel_reg {
- __u64 addr;
- __s32 fd;
- __u32 flags;
- struct __kernel_timespec timeout;
- __u8 opcode;
- __u8 pad[7];
- __u64 pad2[3];
-};
-.EE
-.in
-.PP
-
-The arguments largely mirror what the async prep functions support, see
-.BR io_uring_prep_cancel (3)
-for details. Similarly, the return value is the same. The exception is the
-.I timeout
-argument, which can be used to limit the time that the kernel will wait for
-cancelations to be successful. If the
-.I tv_sec
-and
-.I tv_nsec
-values are set to anything but
-.B -1UL ,
-then they indicate a relative timeout upon which cancelations should be
-completed by.
-
-The
-.I pad
-values must be zero filled.
-
-.SH RETURN VALUE
-See
-.BR io_uring_prep_cancel (3)
-for details on the return value. If
-.I timeout
-is set to indicate a timeout, then
-.B -ETIME
-will be returned if exceeded. If an unknown value is set in the request,
-or if the pad values are not cleared to zero, then
-.I -EINVAL
-is returned.
-.SH SEE ALSO
-.BR io_uring_prep_cancel (3)
diff --git a/src/liburing/man/io_uring_register_sync_msg.3 b/src/liburing/man/io_uring_register_sync_msg.3
deleted file mode 100644
index bef56814bedd..000000000000
--- a/src/liburing/man/io_uring_register_sync_msg.3
+++ /dev/null
@@ -1,74 +0,0 @@
-.\" Copyright (C) 2025 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_register_sync_msg 3 "July 10, 2025" "liburing-2.11" "liburing Manual"
-.SH NAME
-io_uring_register_sync_msg \- send a synchronous message to another ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_register_sync_msg(struct io_uring_sqe *" sqe ");"
-.fi
-.SH DESCRIPTION
-.PP
-.BR io_uring_register_sync_msg (3)
-issues a synchronous MSG_RING request. The
-.I sqe
-parameter must have been cleared and initialized with
-.BR io_uring_prep_msg_ring (3) .
-
-Normally message requests are sent from one ring to another ring. But there
-are also cases where a source ring is not available, yet it would be
-convenient to send a message to a destination ring.
-.BR io_uring_register_sync_msg (3)
-exists for that purpose. A source ring is not required to send a message to
-another ring, instead the
-.I sqe
-parameter can be placed on the stack and filled in using the normal message
-helpers, and then
-.BR io_uring_register_sync_msg (3)
-can be called. Since a source ring does not exist, the results of the operation
-is returned directly rather than via a CQE. On the destination/receiving end,
-a CQE is posted, as it would have been with a non-sync request.
-
-Only data request are supported, sending files such as setup by
-.BR io_uring_prep_msg_ring_fd (3)
-is not supported. The given SQE should be initialized by
-.BR io_uring_prep_msg_ring (3)
-or
-.BR io_uring_prep_msg_ring_cqe_flags (3) ,
-or any other helper that sets up a non-fd message request.
-
-The targeted ring may be any ring that the user has access to, even the ring
-itself. This request can be used for simple message passing to another ring,
-allowing 32+64 bits of data to be transferred through the
-.I len
-and
-.I data
-fields. The use case may be anything from simply waking up someone waiting
-on the targeted ring, or it can be used to pass messages between the two
-rings.
-
-.BR io_uring_prep_msg_ring_cqe_flags (3)
-is similar to
-.BR io_uring_prep_msg_ring (3) .
-But has an addition
-.I cqe_flags
-parameter, which is used to set
-.I flags
-field on CQE side. That way, you can set the CQE flags field
-.I cqe->flags
-when sending a message. Be aware that io_uring could potentially set additional
-bits into this field.
-
-Available since kernel 6.13.
-
-.SH RETURN VALUE
-Returns 0 on success, or
-.BR -errno
-on error.
-.SH SEE ALSO
-.BR io_uring_prep_msg_ring_cqe_flags (3) ,
-.BR io_uring_prep_msg_ring (3)
diff --git a/src/liburing/man/io_uring_resize_rings.3 b/src/liburing/man/io_uring_resize_rings.3
deleted file mode 100644
index 4d4a92867da2..000000000000
--- a/src/liburing/man/io_uring_resize_rings.3
+++ /dev/null
@@ -1,116 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_resize_rings 3 "October 29, 2024" "liburing-2.9" "liburing Manual"
-.SH NAME
-io_uring_resize_rings \- resize the SQ and CQ rings
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_resize_rings(struct io_uring *" ring ",
-.BI " struct io_uring_params *" p ");
-.PP
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_resize_rings (3)
-function performs resizes the SQ and/or CQ ring associated with
-.I ring
-by the parameters specified in
-.I p .
-
-The
-.I p
-argument must be filled in with the appropriate information for the resize
-operations, most notably the
-.IR sq_entries
-and
-.IR cq_entries
-fields must be filled out. The
-.IR flags
-field can also be set, see below for potential values that may be used with
-a resize operation.
-
-It's fairly uncommon to need to resize the SQ ring, but not that uncommon
-that the CQ ring would need resizing. For networked workloads, it can be
-hard to appropriately size the CQ ring upfront, as it's not always known what
-load a given ring will see. If overflow conditions are seen for the CQ ring,
-then resizing it larger may be a good idea.
-
-When a ring is resized, any pending SQ or CQ entries are copied along the
-way. It is not legal to resize a CQ ring that is in an overflow condition,
-and attempting to do so will fail.
-
-Currently doesn't support resizing rings setup with
-.B IORING_SETUP_NO_MMAP .
-This is purely a liburing limitation, the kernel does support it.
-
-Also note that ring resizing is currently only supported on rings setup
-with
-.B IORING_SETUP_DEFER_TASKRUN .
-Attempting to resize differently configured rings will result in an
-.BR -EINVAL
-error.
-
-Valid flags in
-.IR flags :
-.TP
-.B IORING_SETUP_CQSIZE
-If this isn't set, then the CQ ring size is set based on the specified
-SQ ring size. The default is twice as many CQ ring entries as there are
-SQ ring entries. If set, then
-.IR cq_entries
-will be used to size the CQ ring.
-.TP
-.B IORING_SETUP_CLAMP
-If set, then SQ and CQ ring entries are clamped to the maximum allowable
-size, if they exceed that. If not set, setting sizes too large will cause
-the operation to fail.
-.PP
-
-Other flags are inherited from the way the ring was setup, that includes flags
-like
-.B IORING_SETUP_NO_SQARRAY ,
-.B IORING_SETUP_SQE128 ,
-.B IORING_SETUP_CQE32 ,
-and
-.B IORING_SETUP_NO_MMAP .
-
-Other fields in
-.IR p
-should be cleared to zero.
-
-Available since kernel 6.13.
-
-Also see
-.BR io_uring_setup (2)
-for a detailed description of the setup flags.
-
-.SH RETURN VALUE
-.PP
-Returns 0 on success, and < 0 on failure. Potential common failure cases:
-.TP
-.B -EEXIST
-Attempting to resize a ring setup with
-.B IORING_SETUP_SINGLE_ISSUER
-and the resizing task is different from the one that created/enabled the ring.
-.TP
-.B -EFAULT
-Copying of
-.I p
-was unsuccessful.
-.TP
-.B -EINVAL
-Invalid flags were specified for the operation
-.TP
-.B -EINVAL
-Attempt to resize a ring not setup with
-.BR IORING_SETUP_DEFER_TASKRUN .
-.TP
-.B -EOVERFLOW
-The values specified for SQ or CQ entries would cause an overflow.
-
-.SH SEE ALSO
-.BR io_uring_setup (2)
diff --git a/src/liburing/man/io_uring_setup.2 b/src/liburing/man/io_uring_setup.2
deleted file mode 100644
index ec9317dee4f7..000000000000
--- a/src/liburing/man/io_uring_setup.2
+++ /dev/null
@@ -1,762 +0,0 @@
-.\" Copyright (C) 2019 Jens Axboe <axboe@kernel.dk>
-.\" Copyright (C) 2019 Jon Corbet <corbet@lwn.net>
-.\" Copyright (C) 2019 Red Hat, Inc.
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_setup 2 2019-01-29 "Linux" "Linux Programmer's Manual"
-.SH NAME
-io_uring_setup \- setup a context for performing asynchronous I/O
-.SH SYNOPSIS
-.nf
-.BR "#include <liburing.h>"
-.PP
-.BI "int io_uring_setup(u32 " entries ", struct io_uring_params *" params );
-.fi
-.PP
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_setup (2)
-system call sets up a submission queue (SQ) and completion queue (CQ) with at
-least
-.I entries
-entries, and returns a file descriptor which can be used to perform
-subsequent operations on the io_uring instance. The submission and
-completion queues are shared between userspace and the kernel, which
-eliminates the need to copy data when initiating and completing I/O.
-
-.I params
-is used by the application to pass options to the kernel, and by the
-kernel to convey information about the ring buffers.
-.PP
-.in +4n
-.EX
-struct io_uring_params {
- __u32 sq_entries;
- __u32 cq_entries;
- __u32 flags;
- __u32 sq_thread_cpu;
- __u32 sq_thread_idle;
- __u32 features;
- __u32 wq_fd;
- __u32 resv[3];
- struct io_sqring_offsets sq_off;
- struct io_cqring_offsets cq_off;
-};
-.EE
-.in
-.PP
-The
-.IR flags ,
-.IR sq_thread_cpu ,
-and
-.I sq_thread_idle
-fields are used to configure the io_uring instance.
-.I flags
-is a bit mask of 0 or more of the following values ORed
-together:
-.TP
-.B IORING_SETUP_IOPOLL
-Perform busy-waiting for an I/O completion, as opposed to getting
-notifications via an asynchronous IRQ (Interrupt Request). The file
-system (if any) and block device must support polling in order for
-this to work. Busy-waiting provides lower latency, but may consume
-more CPU resources than interrupt driven I/O. Currently, this feature
-is usable only on a file descriptor opened using the
-.B O_DIRECT
-flag. When a read or write is submitted to a polled context, the
-application must poll for completions on the CQ ring by calling
-.BR io_uring_enter (2).
-It is illegal to mix and match polled and non-polled I/O on an io_uring
-instance.
-
-This is only applicable for storage devices for now, and the storage device
-must be configured for polling. How to do that depends on the device type
-in question. For NVMe devices, the nvme driver must be loaded with the
-.I poll_queues
-parameter set to the desired number of polling queues. The polling queues
-will be shared appropriately between the CPUs in the system, if the number
-is less than the number of online CPU threads.
-.TP
-.B IORING_SETUP_HYBRID_IOPOLL
-This flag must be used with
-.B IORING_SETUP_IOPOLL
-flag. Hybrid io polling is a feature based on iopoll, it differs from strict
-polling in that it will delay a bit before doing completion side polling, to
-avoid wasting too much CPU resources. Like
-.B IOPOLL
-, it requires that devices support polling.
-.TP
-.B IORING_SETUP_SQPOLL
-When this flag is specified, a kernel thread is created to perform
-submission queue polling. An io_uring instance configured in this way
-enables an application to issue I/O without ever context switching
-into the kernel. By using the submission queue to fill in new
-submission queue entries and watching for completions on the
-completion queue, the application can submit and reap I/Os without
-doing a single system call.
-
-If the kernel thread is idle for more than
-.I sq_thread_idle
-milliseconds, it will set the
-.B IORING_SQ_NEED_WAKEUP
-bit in the
-.I flags
-field of the
-.IR "struct io_sq_ring" .
-When this happens, the application must call
-.BR io_uring_enter (2)
-to wake the kernel thread. If I/O is kept busy, the kernel thread
-will never sleep. An application making use of this feature will need
-to guard the
-.BR io_uring_enter (2)
-call with the following code sequence:
-
-.in +4n
-.EX
-/*
- * Ensure that the wakeup flag is read after the tail pointer
- * has been written. It's important to use memory load acquire
- * semantics for the flags read, as otherwise the application
- * and the kernel might not agree on the consistency of the
- * wakeup flag.
- */
-unsigned flags = atomic_load_relaxed(sq_ring->flags);
-if (flags & IORING_SQ_NEED_WAKEUP)
- io_uring_enter(fd, 0, 0, IORING_ENTER_SQ_WAKEUP);
-.EE
-.in
-
-where
-.I sq_ring
-is a submission queue ring setup using the
-.I struct io_sqring_offsets
-described below.
-.TP
-.BR
-Note that, when using a ring setup with
-.BR IORING_SETUP_SQPOLL ,
-you never directly call the
-.BR io_uring_enter (2)
-system call. That is usually taken care of by liburing's
-.BR io_uring_submit (3)
-function. It automatically determines if you are using
-polling mode or not and deals with when your program needs to call
-.BR io_uring_enter (2)
-without you having to bother about it.
-.TP
-.BR
-Note that while this may sound immediately appealing
-as an automatic "go faster" flag, evaluations should be done on a case-by-case
-basis to check if it makes sense for the application.
-.TP
-.BR
-Before version 5.11 of the Linux kernel, to successfully use this feature, the
-application must register a set of files to be used for IO through
-.BR io_uring_register (2)
-using the
-.B IORING_REGISTER_FILES
-opcode. Failure to do so will result in submitted IO being errored with
-.BR EBADF .
-The presence of this feature can be detected by the
-.B IORING_FEAT_SQPOLL_NONFIXED
-feature flag.
-In version 5.11 and later, it is no longer necessary to register files to use
-this feature. 5.11 also allows using this as non-root, if the user has the
-.B CAP_SYS_NICE
-capability. In 5.13 this requirement was also relaxed, and no special privileges
-are needed for SQPOLL in newer kernels. Certain stable kernels older than 5.13
-may also support unprivileged SQPOLL.
-.TP
-.B IORING_SETUP_SQ_AFF
-If this flag is specified, then the poll thread will be bound to the
-cpu set in the
-.I sq_thread_cpu
-field of the
-.IR "struct io_uring_params" .
-This flag is only meaningful when
-.B IORING_SETUP_SQPOLL
-is specified. When cgroup setting
-.I cpuset.cpus
-changes (typically in container environment), the bounded cpu set may be
-changed as well.
-.TP
-.B IORING_SETUP_CQSIZE
-Create the completion queue with
-.I "struct io_uring_params.cq_entries"
-entries. The value must be greater than
-.IR entries ,
-and may be rounded up to the next power-of-two.
-.TP
-.B IORING_SETUP_CLAMP
-If this flag is specified, and if
-.IR entries
-exceeds
-.BR IORING_MAX_ENTRIES ,
-then
-.I entries
-will be clamped at
-.BR IORING_MAX_ENTRIES .
-If the flag
-.B IORING_SETUP_CQSIZE
-is set, and if the value of
-.I "struct io_uring_params.cq_entries"
-exceeds
-.BR IORING_MAX_CQ_ENTRIES ,
-then it will be clamped at
-.BR IORING_MAX_CQ_ENTRIES .
-.TP
-.B IORING_SETUP_ATTACH_WQ
-This flag should be set in conjunction with
-.I "struct io_uring_params.wq_fd"
-being set to an existing io_uring ring file descriptor. When set, the
-io_uring instance being created will share the asynchronous worker
-thread backend of the specified io_uring ring, rather than create a new
-separate thread pool. Additionally the sq polling thread will be shared,
-if
-.B IORING_SETUP_SQPOLL
-is set.
-.TP
-.B IORING_SETUP_R_DISABLED
-If this flag is specified, the io_uring ring starts in a disabled state.
-In this state, restrictions can be registered, but submissions are not allowed.
-See
-.BR io_uring_register (2)
-for details on how to enable the ring. Available since 5.10.
-.TP
-.B IORING_SETUP_SUBMIT_ALL
-Normally io_uring stops submitting a batch of requests, if one of these requests
-results in an error. This can cause submission of less than what is expected,
-if a request ends in error while being submitted. If the ring is created with
-this flag,
-.BR io_uring_enter (2)
-will continue submitting requests even if it encounters an error submitting
-a request. CQEs are still posted for errored request regardless of whether or
-not this flag is set at ring creation time, the only difference is if the
-submit sequence is halted or continued when an error is observed. Available
-since 5.18.
-.TP
-.B IORING_SETUP_COOP_TASKRUN
-By default, io_uring will interrupt a task running in userspace when a
-completion event comes in. This is to ensure that completions run in a timely
-manner. For a lot of use cases, this is overkill and can cause reduced
-performance from both the inter-processor interrupt used to do this, the
-kernel/user transition, the needless interruption of the tasks userspace
-activities, and reduced batching if completions come in at a rapid rate. Most
-applications don't need the forceful interruption, as the events are processed
-at any kernel/user transition. The exception are setups where the application
-uses multiple threads operating on the same ring, where the application
-waiting on completions isn't the one that submitted them. For most other
-use cases, setting this flag will improve performance. Available since 5.19.
-.TP
-.B IORING_SETUP_TASKRUN_FLAG
-Used in conjunction with
-.BR IORING_SETUP_COOP_TASKRUN ,
-this provides a flag,
-.BR IORING_SQ_TASKRUN ,
-which is set in the SQ ring
-.I flags
-whenever completions are pending that should be processed. liburing will check
-for this flag even when doing
-.BR io_uring_peek_cqe (3)
-and enter the kernel to process them, and applications can do the same. This
-makes
-.B IORING_SETUP_TASKRUN_FLAG
-safe to use even when applications rely on a peek style operation on the CQ
-ring to see if anything might be pending to reap. Available since 5.19.
-.TP
-.B IORING_SETUP_SQE128
-If set, io_uring will use 128-byte SQEs rather than the normal 64-byte sized
-variant. This is a requirement for using certain request types, as of 5.19
-only the
-.B IORING_OP_URING_CMD
-passthrough command for NVMe passthrough needs this. Available since 5.19.
-.TP
-.B IORING_SETUP_CQE32
-If set, io_uring will use 32-byte CQEs rather than the normal 16-byte sized
-variant. This is a requirement for using certain request types, as of 5.19
-only the
-.B IORING_OP_URING_CMD
-passthrough command for NVMe passthrough needs this. Available since 5.19.
-.TP
-.B IORING_SETUP_SINGLE_ISSUER
-A hint to the kernel that only a single task (or thread) will submit requests, which is
-used for internal optimisations. The submission task is either the task that created the
-ring, or if
-.B IORING_SETUP_R_DISABLED
-is specified then it is the task that enables the ring through
-.BR io_uring_register (2) .
-The kernel enforces this rule, failing requests with
-.B -EEXIST
-if the restriction is violated.
-Note that when
-.B IORING_SETUP_SQPOLL
-is set it is considered that the polling task is doing all submissions
-on behalf of the userspace and so it always complies with the rule disregarding
-how many userspace tasks do
-.BR io_uring_enter (2).
-Available since 6.0.
-.TP
-.B IORING_SETUP_DEFER_TASKRUN
-By default, io_uring will process all outstanding work at the end of any system
-call or thread interrupt. This can delay the application from making other progress.
-Setting this flag will hint to io_uring that it should defer work until an
-.BR io_uring_enter (2)
-call with the
-.B IORING_ENTER_GETEVENTS
-flag set. This allows the application to request work to run just before it wants to
-process completions.
-This flag requires the
-.B IORING_SETUP_SINGLE_ISSUER
-flag to be set, and also enforces that the call to
-.BR io_uring_enter (2)
-is called from the same thread that submitted requests.
-Note that if this flag is set then it is the application's responsibility to periodically
-trigger work (for example via any of the CQE waiting functions) or else completions may
-not be delivered.
-Available since 6.1.
-.TP
-.B IORING_SETUP_NO_MMAP
-By default, io_uring allocates kernel memory that callers must subsequently
-.BR mmap (2).
-If this flag is set, io_uring instead uses caller-allocated buffers;
-.I p->cq_off.user_addr
-must point to the memory for the sq/cq rings, and
-.I p->sq_off.user_addr
-must point to the memory for the sqes.
-Each allocation must be contiguous memory.
-Typically, callers should allocate this memory by using
-.BR mmap (2)
-to allocate a huge page.
-If this flag is set, a subsequent attempt to
-.BR mmap (2)
-the io_uring file descriptor will fail.
-Available since 6.5.
-.TP
-.B IORING_SETUP_REGISTERED_FD_ONLY
-If this flag is set, io_uring will register the ring file descriptor, and
-return the registered descriptor index, without ever allocating an unregistered
-file descriptor. The caller will need to use
-.B IORING_REGISTER_USE_REGISTERED_RING
-when calling
-.BR io_uring_register (2).
-This flag only makes sense when used alongside with
-.BR IORING_SETUP_NO_MMAP ,
-which also needs to be set.
-Available since 6.5.
-
-.TP
-.B IORING_SETUP_NO_SQARRAY
-If this flag is set, entries in the submission queue will be submitted in order,
-wrapping around to the first entry after reaching the end of the queue. In other
-words, there will be no more indirection via the array of submission entries,
-and the queue will be indexed directly by the submission queue tail and the
-range of indexed represented by it modulo queue size. Subsequently, the user
-should not map the array of submission queue entries, and the corresponding
-offset in
-.I struct io_sqring_offsets
-will be set to zero. Available since 6.6.
-
-.PP
-If no flags are specified, the io_uring instance is setup for
-interrupt driven I/O. I/O may be submitted using
-.BR io_uring_enter (2)
-and can be reaped by polling the completion queue.
-
-The
-.I resv
-array must be initialized to zero.
-
-.I features
-is filled in by the kernel, which specifies various features supported
-by current kernel version.
-.TP
-.B IORING_FEAT_SINGLE_MMAP
-If this flag is set, the two SQ and CQ rings can be mapped with a single
-.BR mmap (2)
-call. The SQEs must still be allocated separately. This brings the necessary
-.BR mmap (2)
-calls down from three to two. Available since kernel 5.4.
-.TP
-.B IORING_FEAT_NODROP
-If this flag is set, io_uring supports almost never dropping completion events.
-A dropped event can only occur if the kernel runs out of memory, in which case
-you have worse problems than a lost event. Your application and others will
-likely get OOM killed anyway. If a completion event occurs and the CQ ring is
-full, the kernel stores the event internally until such a time that the CQ ring
-has room for more entries. In earlier kernels, if this overflow condition is
-entered, attempting to submit more IO would fail with the
-.B -EBUSY
-error value, if it can't flush the overflown events to the CQ ring. If this
-happens, the application must reap events from the CQ ring and attempt the
-submit again. If the kernel has no free memory to store the event internally
-it will be visible by an increase in the overflow value on the cqring.
-Available since kernel 5.5. Additionally
-.BR io_uring_enter (2)
-will return
-.B -EBADR
-the next time it would otherwise sleep waiting for completions (since kernel 5.19).
-
-.TP
-.B IORING_FEAT_SUBMIT_STABLE
-If this flag is set, applications can be certain that any data for
-async offload has been consumed when the kernel has consumed the SQE. Available
-since kernel 5.5.
-.TP
-.B IORING_FEAT_RW_CUR_POS
-If this flag is set, applications can specify
-.I offset
-==
-.B -1
-with
-.BR IORING_OP_{READV,WRITEV} ,
-.BR IORING_OP_{READ,WRITE}_FIXED ,
-and
-.B IORING_OP_{READ,WRITE}
-to mean current file position, which behaves like
-.BR preadv2 (2)
-and
-.BR pwritev2 (2)
-with
-.I offset
-==
-.BR -1 .
-It'll use (and update) the current file position. This obviously comes
-with the caveat that if the application has multiple reads or writes in flight,
-then the end result will not be as expected. This is similar to threads sharing
-a file descriptor and doing IO using the current file position. Available since
-kernel 5.6.
-.TP
-.B IORING_FEAT_CUR_PERSONALITY
-If this flag is set, then io_uring guarantees that both sync and async
-execution of a request assumes the credentials of the task that called
-.BR io_uring_enter (2)
-to queue the requests. If this flag isn't set, then requests are issued with
-the credentials of the task that originally registered the io_uring. If only
-one task is using a ring, then this flag doesn't matter as the credentials
-will always be the same. Note that this is the default behavior, tasks can
-still register different personalities through
-.BR io_uring_register (2)
-with
-.B IORING_REGISTER_PERSONALITY
-and specify the personality to use in the sqe. Available since kernel 5.6.
-.TP
-.B IORING_FEAT_FAST_POLL
-If this flag is set, then io_uring supports using an internal poll mechanism
-to drive data/space readiness. This means that requests that cannot read or
-write data to a file no longer need to be punted to an async thread for
-handling, instead they will begin operation when the file is ready. This is
-similar to doing poll + read/write in userspace, but eliminates the need to do
-so. If this flag is set, requests waiting on space/data consume a lot less
-resources doing so as they are not blocking a thread. Available since kernel
-5.7.
-.TP
-.B IORING_FEAT_POLL_32BITS
-If this flag is set, the
-.B IORING_OP_POLL_ADD
-command accepts the full 32-bit range of epoll based flags. Most notably
-.B EPOLLEXCLUSIVE
-which allows exclusive (waking single waiters) behavior. Available since kernel
-5.9.
-.TP
-.B IORING_FEAT_SQPOLL_NONFIXED
-If this flag is set, the
-.B IORING_SETUP_SQPOLL
-feature no longer requires the use of fixed files. Any normal file descriptor
-can be used for IO commands without needing registration. Available since
-kernel 5.11.
-.TP
-.B IORING_FEAT_EXT_ARG
-If this flag is set, then the
-.BR io_uring_enter (2)
-system call supports passing in an extended argument instead of just the
-.I "sigset_t"
-of earlier kernels. This.
-extended argument is of type
-.I "struct io_uring_getevents_arg"
-and allows the caller to pass in both a
-.I sigset_t
-and a timeout argument for waiting on events. The struct layout is as follows:
-.TP
-.in +8n
-.EX
-struct io_uring_getevents_arg {
- __u64 sigmask;
- __u32 sigmask_sz;
- __u32 pad;
- __u64 ts;
-};
-.EE
-
-and a pointer to this struct must be passed in if
-.B IORING_ENTER_EXT_ARG
-is set in the flags for the enter system call. Available since kernel 5.11.
-.TP
-.B IORING_FEAT_NATIVE_WORKERS
-If this flag is set, io_uring is using native workers for its async helpers.
-Previous kernels used kernel threads that assumed the identity of the
-original io_uring owning task, but later kernels will actively create what
-looks more like regular process threads instead. Available since kernel
-5.12.
-.TP
-.B IORING_FEAT_RSRC_TAGS
-If this flag is set, then io_uring supports a variety of features related
-to fixed files and buffers. In particular, it indicates that registered
-buffers can be updated in-place, whereas before the full set would have to
-be unregistered first. Available since kernel 5.13.
-.TP
-.B IORING_FEAT_CQE_SKIP
-If this flag is set, then io_uring supports setting
-.B IOSQE_CQE_SKIP_SUCCESS
-in the submitted SQE, indicating that no CQE should be generated for this
-SQE if it executes normally. If an error happens processing the SQE, a
-CQE with the appropriate error value will still be generated. Available since
-kernel 5.17.
-.TP
-.B IORING_FEAT_LINKED_FILE
-If this flag is set, then io_uring supports sane assignment of files for SQEs
-that have dependencies. For example, if a chain of SQEs are submitted with
-.BR IOSQE_IO_LINK ,
-then kernels without this flag will prepare the file for each link upfront.
-If a previous link opens a file with a known index, eg if direct descriptors
-are used with open or accept, then file assignment needs to happen post
-execution of that SQE. If this flag is set, then the kernel will defer
-file assignment until execution of a given request is started. Available since
-kernel 5.17.
-.TP
-.B IORING_FEAT_REG_REG_RING
-If this flag is set, then io_uring supports calling
-.BR io_uring_register (2)
-using a registered ring fd, via
-.BR IORING_REGISTER_USE_REGISTERED_RING .
-Available since kernel 6.3.
-.TP
-.B IORING_FEAT_MIN_TIMEOUT
-If this flag is set, then io_uring supports passing in a minimum batch wait
-timeout. See
-.BR io_uring_submit_and_wait_min_timeout (3)
-for more details.
-
-.TP
-.B IORING_FEAT_RECVSEND_BUNDLE
-If this flag is set, then io_uring supports bundled send and recv operations.
-See
-.BR io_uring_prep_send_bundle (3)
-for more information. Also implies support for provided buffers in send
-operations.
-.PP
-The rest of the fields in the
-.I struct io_uring_params
-are filled in by the kernel, and provide the information necessary to
-memory map the submission queue, completion queue, and the array of
-submission queue entries.
-.I sq_entries
-specifies the number of submission queue entries allocated.
-.I sq_off
-describes the offsets of various ring buffer fields:
-.PP
-.in +4n
-.EX
-struct io_sqring_offsets {
- __u32 head;
- __u32 tail;
- __u32 ring_mask;
- __u32 ring_entries;
- __u32 flags;
- __u32 dropped;
- __u32 array;
- __u32 resv1;
- __u64 user_addr;
-};
-.EE
-.in
-.PP
-Taken together,
-.I sq_entries
-and
-.I sq_off
-provide all of the information necessary for accessing the submission
-queue ring buffer and the submission queue entry array. The submission queue can
-be mapped with a call like:
-.PP
-.in +4n
-.EX
-ptr = mmap(0, sq_off.array + sq_entries * sizeof(__u32),
- PROT_READ|PROT_WRITE, MAP_SHARED|MAP_POPULATE,
- ring_fd, IORING_OFF_SQ_RING);
-.EE
-.in
-.PP
-where
-.I sq_off
-is the
-.I io_sqring_offsets
-structure, and
-.I ring_fd
-is the file descriptor returned from
-.BR io_uring_setup (2).
-The addition of
-.I sq_off.array
-to the length of the region accounts for the fact that the ring is
-located at the end of the data structure. As an example, the ring
-buffer head pointer can be accessed by adding
-.I sq_off.head
-to the address returned from
-.BR mmap (2):
-.PP
-.in +4n
-.EX
-head = ptr + sq_off.head;
-.EE
-.in
-
-The
-.I flags
-field is used by the kernel to communicate state information to the
-application. Currently, it is used to inform the application when a
-call to
-.BR io_uring_enter (2)
-is necessary. See the documentation for the
-.B IORING_SETUP_SQPOLL
-flag above.
-The
-.I dropped
-member is incremented for each invalid submission queue entry
-encountered in the ring buffer.
-
-The head and tail track the ring buffer state. The tail is
-incremented by the application when submitting new I/O, and the head
-is incremented by the kernel when the I/O has been successfully
-submitted. Determining the index of the head or tail into the ring is
-accomplished by applying a mask:
-.PP
-.in +4n
-.EX
-index = tail & ring_mask;
-.EE
-.in
-.PP
-The array of submission queue entries is mapped with:
-.PP
-.in +4n
-.EX
-sqentries = mmap(0, sq_entries * sizeof(struct io_uring_sqe),
- PROT_READ|PROT_WRITE, MAP_SHARED|MAP_POPULATE,
- ring_fd, IORING_OFF_SQES);
-.EE
-.in
-.PP
-The completion queue is described by
-.I cq_entries
-and
-.I cq_off
-shown here:
-.PP
-.in +4n
-.EX
-struct io_cqring_offsets {
- __u32 head;
- __u32 tail;
- __u32 ring_mask;
- __u32 ring_entries;
- __u32 overflow;
- __u32 cqes;
- __u32 flags;
- __u32 resv1;
- __u64 user_addr;
-};
-.EE
-.in
-.PP
-The completion queue is simpler, since the entries are not separated
-from the queue itself, and can be mapped with:
-.PP
-.in +4n
-.EX
-ptr = mmap(0, cq_off.cqes + cq_entries * sizeof(struct io_uring_cqe),
- PROT_READ|PROT_WRITE, MAP_SHARED|MAP_POPULATE, ring_fd,
- IORING_OFF_CQ_RING);
-.EE
-.in
-.PP
-Closing the file descriptor returned by
-.BR io_uring_setup (2)
-will free all resources associated with the io_uring context. Note that this
-may happen asynchronously within the kernel, so it is not guaranteed that
-resources are freed immediately.
-.PP
-.SH RETURN VALUE
-.BR io_uring_setup (2)
-returns a new file descriptor on success. The application may then
-provide the file descriptor in a subsequent
-.BR mmap (2)
-call to map the submission and completion queues, or to the
-.BR io_uring_register (2)
-or
-.BR io_uring_enter (2)
-system calls.
-
-On error, a negative error code is returned. The caller should not rely on
-.I errno
-variable.
-.PP
-.SH ERRORS
-.TP
-.B EFAULT
-.I params
-is outside your accessible address space.
-.TP
-.B EINVAL
-The resv array contains non-zero data, p.flags contains an unsupported
-flag,
-.I entries
-is out of bounds,
-.B IORING_SETUP_SQ_AFF
-was specified, but
-.B IORING_SETUP_SQPOLL
-was not, or
-.B IORING_SETUP_CQSIZE
-was specified, but
-.I io_uring_params.cq_entries
-was invalid.
-.B IORING_SETUP_REGISTERED_FD_ONLY
-was specified, but
-.B IORING_SETUP_NO_MMAP
-was not.
-.TP
-.B EMFILE
-The per-process limit on the number of open file descriptors has been
-reached (see the description of
-.B RLIMIT_NOFILE
-in
-.BR getrlimit (2)).
-.TP
-.B ENFILE
-The system-wide limit on the total number of open files has been
-reached.
-.TP
-.B ENOMEM
-Insufficient kernel resources are available.
-.TP
-.B EPERM
-.B IORING_SETUP_SQPOLL
-was specified, but the effective user ID of the caller did not have sufficient
-privileges.
-.TP
-.B EPERM
-.I /proc/sys/kernel/io_uring_disabled
-has the value 2, or it has the value 1 and the calling process does not hold the
-.B CAP_SYS_ADMIN
-capability or is not a member of
-.IR /proc/sys/kernel/io_uring_group .
-.TP
-.B ENXIO
-.B IORING_SETUP_ATTACH_WQ
-was set, but
-.I params.wq_fd
-did not refer to an io_uring instance or refers to an instance that is in the
-process of shutting down.
-.SH SEE ALSO
-.BR io_uring_register (2),
-.BR io_uring_enter (2)
diff --git a/src/liburing/man/io_uring_setup_buf_ring.3 b/src/liburing/man/io_uring_setup_buf_ring.3
deleted file mode 100644
index c50748ddbd68..000000000000
--- a/src/liburing/man/io_uring_setup_buf_ring.3
+++ /dev/null
@@ -1,94 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_setup_buf_ring 3 "Mar 07, 2023" "liburing-2.4" "liburing Manual"
-.SH NAME
-io_uring_setup_buf_ring \- setup and register buffer ring for provided buffers
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "struct io_uring_buf_ring *io_uring_setup_buf_ring(struct io_uring *" ring ",
-.BI " unsigned int " nentries ",
-.BI " int " bgid ",
-.BI " unsigned int " flags ",
-.BI " int *" err ");"
-.BI "
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_setup_buf_ring (3)
-function registers a shared buffer ring to be used with provided buffers. For
-the request types that support it, provided buffers are given to the ring and
-one is selected by a request if it has
-.B IOSQE_BUFFER_SELECT
-set in the SQE
-.IR flags ,
-when the request is ready to receive data. This allows both clear ownership
-of the buffer lifetime, and a way to have more read/receive type of operations
-in flight than buffers available.
-
-The
-.I ring
-argument must pointer to the ring for which the provided buffer ring is being
-registered,
-.I nentries
-is the number of entries requested in the buffer ring. This argument must be
-a power-of 2 in size, and can be up to 32768 in size.
-.I bgid
-is the chosen buffer group ID,
-.I flags
-are modifier flags for the operation, and
-.I *err
-is is a pointer to an integer for the error value if any part of the ring
-allocation and registration fails.
-
-The
-.I flags
-argument can be set to one of the following values:
-.TP
-.B IOU_PBUF_RING_INC
-The buffers in this ring can be incrementally consumed. With partial
-consumption, each completion of a given buffer ID will continue where the
-previous one left off, or from the start if no completions have been seen yet.
-When more completions should be expected for a given buffer ID, the CQE will
-have
-.B IORING_CQE_F_BUF_MORE
-set in the
-.I flags
-member. Available since 6.12.
-.PP
-
-Under the covers, this function uses
-.BR io_uring_register_buf_ring (3)
-to register the ring, and handles the allocation of the ring rather than
-letting the application open code it.
-
-To unregister and free a buffer group ID setup with this function, the
-application must call
-.BR io_uring_free_buf_ring (3) .
-
-Available since 5.19.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_setup_buf_ring (3)
-returns a pointer to the buffer ring. On failure it returns
-.BR NULL
-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.
-.SH SEE ALSO
-.BR io_uring_register_buf_ring (3),
-.BR io_uring_buf_ring_init (3),
-.BR io_uring_buf_ring_add (3),
-.BR io_uring_buf_ring_advance (3),
-.BR io_uring_buf_ring_cq_advance (3)
diff --git a/src/liburing/man/io_uring_setup_reg_wait.3 b/src/liburing/man/io_uring_setup_reg_wait.3
deleted file mode 100644
index f755ee4e29a2..000000000000
--- a/src/liburing/man/io_uring_setup_reg_wait.3
+++ /dev/null
@@ -1,121 +0,0 @@
-.\" Copyright (C) 2024 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_setup_reg_wait 3 "November 2, 2024" "liburing-2.9" "liburing Manual"
-.SH NAME
-io_uring_setup_reg_wait \- Sets up and registers fixed wait regions
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "struct io_uring_reg_wait *io_uring_setup_reg_wait(struct io_uring *" ring ","
-.BI " unsigned " nentries ","
-.BI " int *"err ");"
-.PP
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_setup_reg_wait (3)
-function allocates and registers a fixed wait region of
-.IR nentries
-entries. Upon successful return, the function returns a non-NULL pointer. On
-error, it returns
-.B NULL
-and fills in
-.IR err
-with the error value.
-
-A registered wait region is a contiguous range of
-.IR struct io_uring_reg_wait ,
-which look as follows:
-.PP
-.EX
-struct io_uring_reg_wait {
- struct __kernel_timespec ts;
- __u32 min_wait_usec;
- __u32 flags;
- __u64 sigmask;
- __u32 sigmask_sz;
- __u32 pad[3];
- __u64 pad2[2];
-};
-.EE
-where
-.IR ts
-is the wait related information for this wait,
-.IR min_wait_usec
-is the minimum wait period (for a two-stage wait), if set to non-zero,
-.IR flags
-tells the kernel about the wait region,
-.IR sigmask
-is a pointer to a signal mask, if used, and
-.IR sigmask_sz
-is the size of the signal mask, if used.
-
-Currently the only valid flag is
-.B IORING_REG_WAIT_TS ,
-which, if set, indicates that the value in
-.IR ts
-is valid and should be used for the wait operation.
-
-A signal mask is used for the wait, if
-.IR sigmask
-is set to a valid, non-zero, pointer value. If used,
-.IR sigmask_sz
-must also be set.
-
-Each of the wait regions are indicated by the offset of the structure. The
-first wait region is index
-.B 0 ,
-the next is index
-.B 1 ,
-and so forth, up to the registered number of regions set by
-.IR nentries.
-
-The wait regions may be modified by an application at any time before calling
-.BR io_uring_submit_and_reg_wait (3) .
-If modified while a wait region for that given offset is currently in use
-by the kernel, the results are undefined - the kernel may see the new value
-in time to use it, or it may not.
-
-The main purpose of registered wait regions and the associated submit-and-wait
-helpers is to reduce the overhead of a wait operation. A normal wait for
-events with a timeout will pass in a
-.IR struct io_uring_getevents_arg
-which will need to be copied for each wait. For high frequency wait operations,
-this adds noticeable overhead for each wait. With registered wait regions,
-no such copying needs to take place for each wait.
-
-Once a wait region has been setup, it persists for the life time of the ring.
-It's currently not possible to unregister or resize a wait region.
-Additionally, a wait region may currently only use a single page of memory.
-On a 4k page size system, this means an application is limited to
-.B 64
-wait regions. That should be enough, as each wait index may be modified as
-needed. With at least 64 indices available, hopefully applications can just
-use the appropriately setup wait region for each specific type of wait, with
-different indices having different wait settings.
-
-While a region cannot get unregistered from the kernel, once a ring has been
-closed, the application may free the associated memory by calling
-.BR io_uring_free_reg_wait (3) .
-An application may also do this before closing a ring, but then wait regions
-may no longer be modified by the application.
-
-Available since kernel 6.13.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_setup_reg_wait (3)
-returns a pointer to the start of the wait regions. On failure, it returns
-.B NULL
-and sets
-.IR err
-to the appropriate
-.BR -errno
-value.
-.SH SEE ALSO
-.BR io_uring_submit_and_wait_reg (3),
-.BR io_uring_free_reg_wait (3)
diff --git a/src/liburing/man/io_uring_sq_ready.3 b/src/liburing/man/io_uring_sq_ready.3
deleted file mode 100644
index ba155b3210d0..000000000000
--- a/src/liburing/man/io_uring_sq_ready.3
+++ /dev/null
@@ -1,31 +0,0 @@
-.\" Copyright (C) 2022 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_sq_ready 3 "January 25, 2022" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_sq_ready \- number of unconsumed or unsubmitted entries in the SQ ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "unsigned io_uring_sq_ready(const struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_sq_ready (3)
-function returns the number of unconsumed (if SQPOLL) or unsubmitted entries
-that exist in the SQ ring belonging to the
-.I ring
-param.
-
-Usage of this function only applies if the ring has been setup with
-.B IORING_SETUP_SQPOLL,
-where request submissions, and hence consumption from the SQ ring, happens
-through a polling thread.
-
-.SH RETURN VALUE
-Returns the number of unconsumed or unsubmitted entries in the SQ ring.
-.SH SEE ALSO
-.BR io_uring_cq_ready (3)
diff --git a/src/liburing/man/io_uring_sq_space_left.3 b/src/liburing/man/io_uring_sq_space_left.3
deleted file mode 100644
index 74872d8b7690..000000000000
--- a/src/liburing/man/io_uring_sq_space_left.3
+++ /dev/null
@@ -1,25 +0,0 @@
-.\" Copyright (C) 2022 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_sq_space_left 3 "January 25, 2022" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_sq_space_left \- free space in the SQ ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "unsigned io_uring_sq_space_left(const struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_sq_space_left (3)
-function returns how much space is left in the SQ ring belonging to the
-.I ring
-param.
-
-.SH RETURN VALUE
-Returns the number of availables entries in the SQ ring.
-.SH SEE ALSO
-.BR io_uring_sq_ready (3)
diff --git a/src/liburing/man/io_uring_sqe_set_buf_group.3 b/src/liburing/man/io_uring_sqe_set_buf_group.3
deleted file mode 100644
index 5299051d07e3..000000000000
--- a/src/liburing/man/io_uring_sqe_set_buf_group.3
+++ /dev/null
@@ -1,32 +0,0 @@
-.\" Copyright (C) 2024 Christian Mazakas <christian.mazakas@gmail.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_sqe_set_buf_group 3 "December 9, 2024" "liburing-2.9" "liburing Manual"
-.SH NAME
-io_uring_sqe_set_buf_group \- set buf group for submission queue event
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_sqe_set_buf_group(struct io_uring_sqe *" sqe ","
-.BI " int " bgid ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_sqe_set_buf_group (3)
-function sets the associated buf_group of the
-.I sqe
-to
-.IR bgid .
-
-After the caller has requested a submission queue entry (SQE) with
-.BR io_uring_get_sqe (3) ,
-they can associate a buf_group with the SQE used for multishot operations.
-
-.SH RETURN VALUE
-None
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_cqe_set_data (3)
diff --git a/src/liburing/man/io_uring_sqe_set_data.3 b/src/liburing/man/io_uring_sqe_set_data.3
deleted file mode 100644
index 0a91f57f4cf7..000000000000
--- a/src/liburing/man/io_uring_sqe_set_data.3
+++ /dev/null
@@ -1,57 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_sqe_set_data 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_sqe_set_data \- set user data for submission queue event
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_sqe_set_data(struct io_uring_sqe *" sqe ","
-.BI " void *" user_data ");"
-.BI "
-.BI "void io_uring_sqe_set_data64(struct io_uring_sqe *" sqe ","
-.BI " __u64 " data ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_sqe_set_data (3)
-function stores a
-.I user_data
-pointer with the submission queue entry
-.IR sqe .
-
-The
-.BR io_uring_sqe_set_data64 (3)
-function stores a 64-bit
-.I data
-value with the submission queue entry
-.IR sqe .
-
-After the caller has requested a submission queue entry (SQE) with
-.BR io_uring_get_sqe (3) ,
-they can associate a data pointer or value with the SQE. Once the completion
-arrives, the function
-.BR io_uring_cqe_get_data (3)
-or
-.BR io_uring_cqe_get_data64 (3)
-can be called to retrieve the data pointer or value associated with the
-submitted request.
-
-Note that if neither of these functions are called, or the
-.I user_data
-field in the
-.IR sqe
-isn't set manually either, then the field may contain a value from a previous
-use of this sqe. If an application relies on always having a valid
-.I user_data
-value present, it must always assign one to each sqe.
-
-.SH RETURN VALUE
-None
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_cqe_get_data (3)
diff --git a/src/liburing/man/io_uring_sqe_set_data64.3 b/src/liburing/man/io_uring_sqe_set_data64.3
deleted file mode 120000
index 8bbd6927f35e..000000000000
--- a/src/liburing/man/io_uring_sqe_set_data64.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_sqe_set_data.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_sqe_set_flags.3 b/src/liburing/man/io_uring_sqe_set_flags.3
deleted file mode 100644
index ab0bb8e7b531..000000000000
--- a/src/liburing/man/io_uring_sqe_set_flags.3
+++ /dev/null
@@ -1,87 +0,0 @@
-.\" Copyright (C) 2022 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_sqe_set_flags 3 "January 25, 2022" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_sqe_set_flags \- set flags for submission queue entry
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "void io_uring_sqe_set_flags(struct io_uring_sqe *" sqe ","
-.BI " unsigned " flags ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_sqe_set_flags (3)
-function allows the caller to change the behavior of the submission queue entry
-by specifying flags. It enables the
-.I flags
-belonging to the
-.I sqe
-submission queue entry param.
-
-.I flags
-is a bit mask of 0 or more of the following values ORed together:
-.TP
-.B IOSQE_FIXED_FILE
-The file descriptor in the SQE refers to the index of a previously registered
-file or direct file descriptor, not a normal file descriptor.
-.TP
-.B IOSQE_ASYNC
-Normal operation for io_uring is to try and issue an sqe as non-blocking first,
-and if that fails, execute it in an async manner. To support more efficient
-overlapped operation of requests that the application knows/assumes will
-always (or most of the time) block, the application can ask for an sqe to be
-issued async from the start. Note that this flag immediately causes the SQE
-to be offloaded to an async helper thread with no initial non-blocking attempt.
-This may be less efficient and should not be used liberally or without
-understanding the performance and efficiency tradeoffs.
-.TP
-.B IOSQE_IO_LINK
-When this flag is specified, the SQE forms a link with the next SQE in the
-submission ring. That next SQE will not be started before the previous request
-completes. This, in effect, forms a chain of SQEs, which can be arbitrarily
-long. The tail of the chain is denoted by the first SQE that does not have this
-flag set. Chains are not supported across submission boundaries. Even if the
-last SQE in a submission has this flag set, it will still terminate the current
-chain. This flag has no effect on previous SQE submissions, nor does it impact
-SQEs that are outside of the chain tail. This means that multiple chains can be
-executing in parallel, or chains and individual SQEs. Only members inside the
-chain are serialized. A chain of SQEs will be broken if any request in that
-chain ends in error.
-.TP
-.B IOSQE_IO_HARDLINK
-Like
-.B IOSQE_IO_LINK ,
-except the links aren't severed if an error or unexpected result occurs.
-.TP
-.B IOSQE_IO_DRAIN
-When this flag is specified, the SQE will not be started before previously
-submitted SQEs have completed, and new SQEs will not be started before this
-one completes.
-.TP
-.B IOSQE_CQE_SKIP_SUCCESS
-Request that no CQE be generated for this request, if it completes successfully.
-This can be useful in cases where the application doesn't need to know when
-a specific request completed, if it completed successfully.
-.TP
-.B IOSQE_BUFFER_SELECT
-If set, and if the request types supports it, select an IO buffer from the
-indicated buffer group. This can be used with requests that read or receive
-data from a file or socket, where buffer selection is deferred until the kernel
-is ready to transfer data, instead of when the IO is originally submitted. The
-application must also set the
-.I buf_group
-field in the SQE, indicating which previously registered buffer group to select
-a buffer from.
-
-.SH RETURN VALUE
-None
-.SH SEE ALSO
-.BR io_uring_submit (3),
-.BR io_uring_register (3)
-.BR io_uring_register_buffers (3)
-.BR io_uring_register_buf_ring (3)
diff --git a/src/liburing/man/io_uring_sqring_wait.3 b/src/liburing/man/io_uring_sqring_wait.3
deleted file mode 100644
index 4d3a5676d3f3..000000000000
--- a/src/liburing/man/io_uring_sqring_wait.3
+++ /dev/null
@@ -1,34 +0,0 @@
-.\" Copyright (C) 2022 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_sqring_wait 3 "January 25, 2022" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_sqring_wait \- wait for free space in the SQ ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_sqring_wait(struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-The function
-.BR io_uring_sqring_wait (3)
-allows the caller to wait for space to free up in the SQ ring belonging to the
-.I ring
-param, which happens when the kernel side thread
-has consumed one or more entries. If the SQ ring is currently non-full,
-no action is taken.
-
-This feature can only be used when the ring has been setup with
-.B IORING_SETUP_SQPOLL
-and hence is using an offloaded approach to request submissions.
-
-.SH RETURN VALUE
-On success it returns the free space. If the kernel does not support the
-feature, -EINVAL is returned.
-.SH SEE ALSO
-.BR io_uring_submit (3),
-.BR io_uring_wait_cqe (3),
-.BR io_uring_wait_cqes (3)
diff --git a/src/liburing/man/io_uring_submit.3 b/src/liburing/man/io_uring_submit.3
deleted file mode 100644
index c7dbbed21dfb..000000000000
--- a/src/liburing/man/io_uring_submit.3
+++ /dev/null
@@ -1,51 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_submit 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_submit \- submit requests to the submission queue
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_submit(struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_submit (3)
-function submits the next events to the submission queue belonging to the
-.IR ring .
-
-After the caller retrieves a submission queue entry (SQE) with
-.BR io_uring_get_sqe (3)
-and prepares the SQE using one of the provided helpers, it can be submitted with
-.BR io_uring_submit (3) .
-
-.SH RETURN VALUE
-On success
-.BR io_uring_submit (3)
-returns the number of submitted submission queue entries, if SQPOLL is not used.
-If SQPOLL is used, the return value may report a higher number of submitted
-entries than actually submitted. If the user requires accurate information
-about how many submission queue entries have been successfully submitted, while
-using SQPOLL, the user must fall back to repeatedly submitting a single submission
-queue entry. On failure it returns
-.BR -errno .
-.SH NOTES
-For any request that passes in data in a struct, that data must remain
-valid until the request has been successfully submitted. It need not remain
-valid until completion. Once a request has been submitted, the in-kernel
-state is stable. Very early kernels (5.4 and earlier) required state to be
-stable until the completion occurred. Applications can test for this
-behavior by inspecting the
-.B IORING_FEAT_SUBMIT_STABLE
-flag passed back from
-.BR io_uring_queue_init_params (3).
-In general, the man pages for the individual prep helpers will have a note
-mentioning this fact as well, if required for the given command.
-.SH SEE ALSO
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit_and_wait (3),
-.BR io_uring_submit_and_wait_timeout (3)
diff --git a/src/liburing/man/io_uring_submit_and_get_events.3 b/src/liburing/man/io_uring_submit_and_get_events.3
deleted file mode 100644
index 9e143d1dff47..000000000000
--- a/src/liburing/man/io_uring_submit_and_get_events.3
+++ /dev/null
@@ -1,31 +0,0 @@
-.\" Copyright (C), 2022 dylany
-.\" You may distribute this file under the terms of the GNU Free
-.\" Documentation License.
-.TH io_uring_submit_and_get_events 3 "September 5, 2022" "liburing-2.3" "liburing Manual"
-.SH NAME
-io_uring_submit_and_get_events \- submit requests to the submission queue and flush completions
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_submit_and_get_events(struct io_uring *" ring ");"
-.fi
-
-.SH DESCRIPTION
-The
-.BR io_uring_submit_and_get_events (3)
-function submits the next events to the submission queue as with
-.BR io_uring_submit (3) .
-After submission it will flush CQEs as with
-.BR io_uring_get_events (3) .
-
-The benefit of this function is that it does both with only one system call.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_submit_and_get_events (3)
-returns the number of submitted submission queue entries. On failure it returns
-.BR -errno .
-.SH SEE ALSO
-.BR io_uring_submit (3),
-.BR io_uring_get_events (3)
diff --git a/src/liburing/man/io_uring_submit_and_wait.3 b/src/liburing/man/io_uring_submit_and_wait.3
deleted file mode 100644
index 2351f335a7aa..000000000000
--- a/src/liburing/man/io_uring_submit_and_wait.3
+++ /dev/null
@@ -1,44 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_submit_and_wait 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_submit_and_wait \- submit requests to the submission queue and wait for completion
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_submit_and_wait(struct io_uring *" ring ","
-.BI " unsigned " wait_nr ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_submit_and_wait (3)
-function submits the next requests from the submission queue belonging to the
-.I ring
-and waits for
-.I wait_nr
-completion events.
-
-After the caller retrieves a submission queue entry (SQE) with
-.BR io_uring_get_sqe (3)
-and prepares the SQE, it can be submitted with
-.BR io_uring_submit_and_wait (3) .
-
-Ideally used with a ring setup with
-.BR IORING_SETUP_SINGLE_ISSUER | IORING_SETUP_DEFER_TASKRUN
-as that will greatly reduce the number of context switches that an application
-will see waiting on multiple requests.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_submit_and_wait (3)
-returns the number of submitted submission queue entries. On failure it returns
-.BR -errno .
-.SH SEE ALSO
-.BR io_uring_queue_init_params (3),
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_submit_and_wait_timeout (3)
diff --git a/src/liburing/man/io_uring_submit_and_wait_min_timeout.3 b/src/liburing/man/io_uring_submit_and_wait_min_timeout.3
deleted file mode 100644
index 6a52806fa70a..000000000000
--- a/src/liburing/man/io_uring_submit_and_wait_min_timeout.3
+++ /dev/null
@@ -1,119 +0,0 @@
-.\" Copyright (C) 2024 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_submit_and_wait_min_timeout 3 "Jan 11, 2024" "liburing-2.8" "liburing Manual"
-.SH NAME
-io_uring_submit_and_wait_min_timeout \- submit requests to the submission queue and
-wait for the completion with both batch and normal timeout
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_submit_and_wait_min_timeout(struct io_uring *" ring ","
-.BI " struct io_uring_cqe **" cqe_ptr ","
-.BI " unsigned " wait_nr ","
-.BI " struct __kernel_timespec *" ts ","
-.BI " unsigned int " min_wait_usec ",
-.BI " sigset_t *" sigmask ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_submit_and_wait_min_timeout (3)
-function submits the next requests from the submission queue belonging to the
-.I ring
-and waits for
-.I wait_nr
-completion events, or until the timeout
-.I ts
-expires. The completion events are stored in the
-.I cqe_ptr
-array. If non-zero,
-.I min_wait_usec
-denotes a timeout for the
-.I wait_nr
-batch.
-
-The
-.I sigmask
-specifies the set of signals to block. If set, it is equivalent to atomically
-executing the following calls:
-.PP
-.in +4n
-.EX
-sigset_t origmask;
-
-pthread_sigmask(SIG_SETMASK, &sigmask, &origmask);
-ret = io_uring_submit_and_wait_min_timeout(ring, cqe, wait_nr, ts, min_wait, NULL);
-pthread_sigmask(SIG_SETMASK, &origmask, NULL);
-.EE
-.in
-.PP
-This works like
-.BR io_uring_submit_and_wait_timeout (3)
-with the twist that it applies a minimum timeout for the requested batch size
-of requests to wait for. While
-.BR io_uring_submit_and_wait_timeout (3)
-waits for as long as
-.IR ts
-specifies, or until
-.IR wait_nr
-of request completions have been received, if
-.IR min_wait_usec
-is set, then this is the timeout for the
-.IR wait_nr
-number of requests. If the requested number of completions have been received
-within
-.IR min_wait_usec
-number of microseconds, then the function returns successfully. If that isn't
-the case, once
-.IR min_wait_usec
-time has passed, control is returned if any completions have been posted. If
-no completions have been posted, the kernel switches to a normal wait of up
-to
-.IR ts
-specified amount of time, subtracting the time already waited. If any
-completions are posted after this happens, control is returned immediately to
-the application.
-
-This differs from the normal timeout waiting in that waiting continues post
-the initial timeout, if and only if no completions have been posted. It's meant
-to be used to optimize batch waiting for requests, where the application
-allots a budget of
-.IR min_wait_usec
-amount of time to receive
-.IR wait_nr
-number of completions, but if none are received, then waiting can continue
-without incurring extra context switches or extra kernel/user transitions.
-
-Can be used with any ring, as long as the kernel supports it. Support is
-indicated by checking the
-.BR IORING_FEAT_MIN_TIMEOUT
-feature flag after the ring has been setup. Ideally used with a ring setup
-with
-.BR IORING_SETUP_SINGLE_ISSUER | IORING_SETUP_DEFER_TASKRUN
-as that will greatly reduce the number of context switches that an application
-will see waiting on multiple requests.
-
-Available since 6.12.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_submit_and_wait_min_timeout (3)
-returns the number of submitted submission queue entries. On failure it returns
-.BR -errno .
-If the kernel doesn't support this functionality,
-.BR -EINVAL
-will be returned. See note on the feature flag.
-The most common failure case is not receiving a completion within the specified
-timeout,
-.B -ETIME
-is returned in this case.
-.SH SEE ALSO
-.BR io_uring_queue_init_params (3),
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_submit_and_wait (3),
-.BR io_uring_submit_and_wait_timeout (3),
-.BR io_uring_wait_cqe (3)
diff --git a/src/liburing/man/io_uring_submit_and_wait_reg.3 b/src/liburing/man/io_uring_submit_and_wait_reg.3
deleted file mode 100644
index 3575727231d6..000000000000
--- a/src/liburing/man/io_uring_submit_and_wait_reg.3
+++ /dev/null
@@ -1,63 +0,0 @@
-.\" Copyright (C) 2024 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_submit_and_wait_reg 3 "November 2, 2024" "liburing-2.9" "liburing Manual"
-.SH NAME
-io_uring_submit_and_wait_reg \- Sets up and registers fixed wait regions
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_submit_and_wait_reg(struct io_uring *" ring ","
-.BI " struct io_uring_cqe **"cqe_ptr ","
-.BI " unsigned "wait_nr ","
-.BI " int "reg_index ");"
-.PP
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_submit_and_wait_reg (3)
-submits previously prepared requests in the ring
-.IR ring
-and waits for
-.IR wait_nr
-completions using the registered wait index of
-.IR reg_index .
-Upon successful return, the completion events are stored in the
-.IR cqe_ptr
-array.
-
-This function works like
-.BR io_uring_submit_and_wait_min_timeout (3)
-in that it supports all the features of that helper, but rather than pass in
-all the information in a struct that needs copying, it references a registered
-wait index for which previously registered wait region holds information
-about how the wait should be performed. That includes information such as
-the overall timeout, the minimum timeout to be used, and so forth. See
-.BR io_uring_setup_reg_wait (3)
-for the details on registered wait regions.
-
-Using registered wait regions has less overhead then other wait methods, as
-no copying of data is needed.
-
-It's valid to use this function purely for waiting on events, even if no
-new requests should be submitted.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_submit_and_wait_reg (3)
-returns the number of new requests submitted. On failure it returns
-.BR -errno .
-If the kernel doesn't support this functionality,
-.BR -EINVAL
-will be returned. If no events are submitted and the wait operation times
-out, then
-.BR -ETIME
-will be returned.
-
-.SH SEE ALSO
-.BR io_uring_setup_reg_wait (3) ,
-.BR io_uring_submit_and_wait_min_timeout (3) ,
-.BR io_uring_submit_and_wait_timeout (3)
diff --git a/src/liburing/man/io_uring_submit_and_wait_timeout.3 b/src/liburing/man/io_uring_submit_and_wait_timeout.3
deleted file mode 100644
index 74611766b385..000000000000
--- a/src/liburing/man/io_uring_submit_and_wait_timeout.3
+++ /dev/null
@@ -1,74 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_submit_and_wait_timeout 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_submit_and_wait_timeout \- submit requests to the submission queue and
-wait for the completion with timeout
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_submit_and_wait_timeout(struct io_uring *" ring ","
-.BI " struct io_uring_cqe **" cqe_ptr ","
-.BI " unsigned " wait_nr ","
-.BI " struct __kernel_timespec *" ts ","
-.BI " sigset_t *" sigmask ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_submit_and_wait_timeout (3)
-function submits the next requests from the submission queue belonging to the
-.I ring
-and waits for
-.I wait_nr
-completion events, or until the timeout
-.I ts
-expires. The completion events are stored in the
-.I cqe_ptr
-array.
-.PP
-The
-.I sigmask
-specifies the set of signals to block. If set, it is equivalent to atomically
-executing the following calls:
-.PP
-.in +4n
-.EX
-sigset_t origmask;
-
-pthread_sigmask(SIG_SETMASK, &sigmask, &origmask);
-ret = io_uring_submit_and_wait_timeout(ring, cqe, wait_nr, ts, NULL);
-pthread_sigmask(SIG_SETMASK, &origmask, NULL);
-.EE
-.in
-.PP
-After the caller retrieves a submission queue entry (SQE) with
-.BR io_uring_get_sqe (3)
-and prepares the SQE, it can be submitted with
-.BR io_uring_submit_and_wait_timeout (3) .
-
-Ideally used with a ring setup with
-.BR IORING_SETUP_SINGLE_ISSUER | IORING_SETUP_DEFER_TASKRUN
-as that will greatly reduce the number of context switches that an application
-will see waiting on multiple requests.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_submit_and_wait_timeout (3)
-returns the number of submitted submission queue entries. On failure it returns
-.BR -errno .
-Note that in earlier versions of the liburing library, the return value was 0
-on success.
-The most common failure case is not receiving a completion within the specified
-timeout,
-.B -ETIME
-is returned in this case.
-.SH SEE ALSO
-.BR io_uring_queue_init_params (3),
-.BR io_uring_get_sqe (3),
-.BR io_uring_submit (3),
-.BR io_uring_submit_and_wait (3),
-.BR io_uring_wait_cqe (3)
diff --git a/src/liburing/man/io_uring_unregister_buf_ring.3 b/src/liburing/man/io_uring_unregister_buf_ring.3
deleted file mode 100644
index ee87e860aafb..000000000000
--- a/src/liburing/man/io_uring_unregister_buf_ring.3
+++ /dev/null
@@ -1,30 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_unregister_buf_ring 3 "May 18, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_unregister_buf_ring \- unregister a previously registered buffer ring
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_unregister_buf_ring(struct io_uring *" ring ",
-.BI " int " bgid ");"
-.BI "
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_unregister_buf_ring (3)
-function unregisters a previously registered shared buffer ring indicated by
-.IR bgid .
-
-.SH RETURN VALUE
-On success
-.BR io_uring_unregister_buf_ring (3)
-returns 0. On failure it returns
-.BR -errno .
-.SH SEE ALSO
-.BR io_uring_register_buf_ring (3),
-.BR io_uring_buf_ring_free (3)
diff --git a/src/liburing/man/io_uring_unregister_buffers.3 b/src/liburing/man/io_uring_unregister_buffers.3
deleted file mode 100644
index f066679bf90d..000000000000
--- a/src/liburing/man/io_uring_unregister_buffers.3
+++ /dev/null
@@ -1,27 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_unregister_buffers 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_unregister_buffers \- unregister buffers for fixed buffer operations
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_unregister_buffers(struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_unregister_buffers (3)
-function unregisters the fixed buffers previously registered to the
-.IR ring .
-
-.SH RETURN VALUE
-On success
-.BR io_uring_unregister_buffers (3)
-returns 0. On failure it returns
-.BR -errno .
-.SH SEE ALSO
-.BR io_uring_register_buffers (3)
diff --git a/src/liburing/man/io_uring_unregister_eventfd.3 b/src/liburing/man/io_uring_unregister_eventfd.3
deleted file mode 120000
index 665995711bf2..000000000000
--- a/src/liburing/man/io_uring_unregister_eventfd.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_register_eventfd.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_unregister_files.3 b/src/liburing/man/io_uring_unregister_files.3
deleted file mode 100644
index c468d0813f24..000000000000
--- a/src/liburing/man/io_uring_unregister_files.3
+++ /dev/null
@@ -1,27 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_unregister_files 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_unregister_files \- unregister file descriptors
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_unregister_files(struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_unregister_files (3)
-function unregisters the file descriptors previously registered to the
-.IR ring .
-
-.SH RETURN VALUE
-On success
-.BR io_uring_unregister_files (3)
-returns 0. On failure it returns
-.BR -errno .
-.SH SEE ALSO
-.BR io_uring_register_files (3)
diff --git a/src/liburing/man/io_uring_unregister_iowq_aff.3 b/src/liburing/man/io_uring_unregister_iowq_aff.3
deleted file mode 120000
index c29bd44ea833..000000000000
--- a/src/liburing/man/io_uring_unregister_iowq_aff.3
+++ /dev/null
@@ -1 +0,0 @@
-io_uring_register_iowq_aff.3
\ No newline at end of file
diff --git a/src/liburing/man/io_uring_unregister_napi.3 b/src/liburing/man/io_uring_unregister_napi.3
deleted file mode 100644
index f7087ef73639..000000000000
--- a/src/liburing/man/io_uring_unregister_napi.3
+++ /dev/null
@@ -1,27 +0,0 @@
-.\" Copyright (C) 2022 Stefan Roesch <shr@devkernel.io>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_unregister_napi 3 "November 16, 2022" "liburing-2.4" "liburing Manual"
-.SH NAME
-io_uring_unregister_napi \- unregister NAPI busy poll settings
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_unregister_napi(struct io_uring *" ring ","
-.BI " struct io_uring_napi *" napi)
-.PP
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_unregister_napi (3)
-function unregisters the NAPI busy poll settings for subsequent operations.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_unregister_napi (3)
-return 0. On failure they return
-.BR -errno .
-It also updates the napi structure with the current values.
diff --git a/src/liburing/man/io_uring_unregister_ring_fd.3 b/src/liburing/man/io_uring_unregister_ring_fd.3
deleted file mode 100644
index 85aca1415159..000000000000
--- a/src/liburing/man/io_uring_unregister_ring_fd.3
+++ /dev/null
@@ -1,32 +0,0 @@
-.\" Copyright (C) 2022 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_unregister_ring_fd 3 "March 11, 2022" "liburing-2.2" "liburing Manual"
-.SH NAME
-io_uring_unregister_ring_fd \- unregister a ring file descriptor
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_unregister_ring_fd(struct io_uring *" ring ");"
-.fi
-.SH DESCRIPTION
-.PP
-.BR io_uring_unregister_ring_fd (3)
-unregisters the file descriptor of the ring.
-
-Unregisters a ring descriptor previously registered with the task. This is
-done automatically when
-.BR io_uring_queue_exit (3)
-is called, but can also be done to free up space for new ring registrations.
-For more information on ring descriptor registration, see
-.BR io_uring_register_ring_fd (3)
-
-.SH RETURN VALUE
-Returns 1 on success, indicating that one file descriptor was unregistered, or
-.BR -errno
-on error.
-.SH SEE ALSO
-.BR io_uring_register_ring_fd (3),
-.BR io_uring_register_files (3)
diff --git a/src/liburing/man/io_uring_wait_cqe.3 b/src/liburing/man/io_uring_wait_cqe.3
deleted file mode 100644
index c2fffedeb8cd..000000000000
--- a/src/liburing/man/io_uring_wait_cqe.3
+++ /dev/null
@@ -1,41 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_wait_cqe 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_wait_cqe \- wait for one io_uring completion event
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_wait_cqe(struct io_uring *" ring ","
-.BI " struct io_uring_cqe **" cqe_ptr ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_wait_cqe (3)
-function waits for an IO completion from the queue belonging to the
-.I ring
-param, waiting for it if necessary. If an event is already available in
-the ring when invoked, no waiting will occur. The
-.I cqe_ptr
-param is filled in on success.
-
-After the caller has submitted a request with
-.BR io_uring_submit (3),
-the application can retrieve the completion with
-.BR io_uring_wait_cqe (3).
-
-.SH RETURN VALUE
-On success
-.BR io_uring_wait_cqe (3)
-returns 0 and the cqe_ptr param is filled in. On failure it returns
-.BR -errno .
-The return value indicates the result of waiting for a CQE, and it has no
-relation to the CQE result itself.
-.SH SEE ALSO
-.BR io_uring_submit (3),
-.BR io_uring_wait_cqe_timeout (3),
-.BR io_uring_wait_cqes (3)
diff --git a/src/liburing/man/io_uring_wait_cqe_nr.3 b/src/liburing/man/io_uring_wait_cqe_nr.3
deleted file mode 100644
index 9e19098f54fd..000000000000
--- a/src/liburing/man/io_uring_wait_cqe_nr.3
+++ /dev/null
@@ -1,49 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_wait_cqe_nr 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_wait_cqe_nr \- wait for one or more io_uring completion events
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_wait_cqe_nr(struct io_uring *" ring ","
-.BI " struct io_uring_cqe **" cqe_ptr ","
-.BI " unsigned " wait_nr ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_wait_cqe_nr (3)
-function returns
-.I wait_nr
-IO completion events from the queue belonging to the
-.I ring
-param, waiting for it if necessary. If the requested number of events are
-already available in the ring when invoked, no waiting will occur. The
-.I cqe_ptr
-param is filled in on success.
-
-After the caller has submitted a request with
-.BR io_uring_submit (3),
-the application can retrieve the completion with
-.BR io_uring_wait_cqe (3).
-
-Ideally used with a ring setup with
-.BR IORING_SETUP_SINGLE_ISSUER | IORING_SETUP_DEFER_TASKRUN
-as that will greatly reduce the number of context switches that an application
-will see waiting on multiple requests.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_wait_cqe_nr (3)
-returns 0 and the cqe_ptr param is filled in. On failure it returns
-.BR -errno .
-The return value indicates the result of waiting for a CQE, and it has no
-relation to the CQE result itself.
-.SH SEE ALSO
-.BR io_uring_queue_init_params (3),
-.BR io_uring_submit (3),
-.BR io_uring_wait_cqes (3)
diff --git a/src/liburing/man/io_uring_wait_cqe_timeout.3 b/src/liburing/man/io_uring_wait_cqe_timeout.3
deleted file mode 100644
index 901772b91679..000000000000
--- a/src/liburing/man/io_uring_wait_cqe_timeout.3
+++ /dev/null
@@ -1,61 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_wait_cqe_timeout 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_wait_cqe_timeout \- wait for one io_uring completion event with timeout
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_wait_cqe_timeout(struct io_uring *" ring ","
-.BI " struct io_uring_cqe **" cqe_ptr ","
-.BI " struct __kernel_timespec *" ts ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_wait_cqe_timeout (3)
-function waits for one IO completion to be available from the queue belonging
-to the
-.I ring
-param, waiting for it if necessary or until the timeout
-.I ts
-expires. If an event is already available in the ring when invoked, no waiting
-will occur.
-
-The
-.I cqe_ptr
-param is filled in on success.
-
-If
-.I ts
-is specified and an older kernel without
-.B IORING_FEAT_EXT_ARG
-is used, the application does not need to call
-.BR io_uring_submit (3)
-before calling
-.BR io_uring_wait_cqes (3).
-For newer kernels with that feature flag set, there is no implied submit
-when waiting for a request.
-
-If
-.I ts
-is
-.B NULL ,
-then this behaves like
-.BR io_uring_wait_cqe (3)
-in that it will wait forever for an event.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_wait_cqe_timeout (3)
-returns 0 and the cqe_ptr param is filled in. On failure it returns
-.BR -errno .
-The return value indicates the result of waiting for a CQE, and it has no
-relation to the CQE result itself.
-.SH SEE ALSO
-.BR io_uring_submit (3),
-.BR io_uring_wait_cqes (3),
-.BR io_uring_wait_cqe (3)
diff --git a/src/liburing/man/io_uring_wait_cqes.3 b/src/liburing/man/io_uring_wait_cqes.3
deleted file mode 100644
index 816cd73abac3..000000000000
--- a/src/liburing/man/io_uring_wait_cqes.3
+++ /dev/null
@@ -1,80 +0,0 @@
-.\" Copyright (C) 2021 Stefan Roesch <shr@fb.com>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_wait_cqes 3 "November 15, 2021" "liburing-2.1" "liburing Manual"
-.SH NAME
-io_uring_wait_cqes \- wait for one or more io_uring completion events
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_wait_cqes(struct io_uring *" ring ","
-.BI " struct io_uring_cqe **" cqe_ptr ","
-.BI " unsigned " wait_nr ","
-.BI " struct __kernel_timespec *" ts ","
-.BI " sigset_t *" sigmask ");
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_wait_cqes (3)
-function returns
-.I wait_nr
-IO completions from the queue belonging to the
-.I ring
-param, waiting for them if necessary or until the timeout
-.I ts
-expires.
-.PP
-The
-.I sigmask
-specifies the set of signals to block. If set, it is equivalent to atomically
-executing the following calls:
-.PP
-.in +4n
-.EX
-sigset_t origmask;
-
-pthread_sigmask(SIG_SETMASK, &sigmask, &origmask);
-ret = io_uring_wait_cqes(ring, cqe, wait_nr, ts, NULL);
-pthread_sigmask(SIG_SETMASK, &origmask, NULL);
-.EE
-.in
-.PP
-The
-.I cqe_ptr
-param is filled in on success with the first CQE. Callers of this function
-should use
-.BR io_uring_for_each_cqe (3)
-to iterate all available CQEs.
-
-If
-.I ts
-is specified and an older kernel without
-.B IORING_FEAT_EXT_ARG
-is used, the application does not need to call
-.BR io_uring_submit (3)
-before calling
-.BR io_uring_wait_cqes (3).
-For newer kernels with that feature flag set, there is no implied submit
-when waiting for a request.
-
-If
-.I ts
-is
-.B NULL ,
-then this behaves like
-.BR io_uring_wait_cqe (3)
-in that it will wait forever for an event.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_wait_cqes (3)
-returns 0 and the cqe_ptr param is filled in. On failure it returns
-.BR -errno .
-.SH SEE ALSO
-.BR io_uring_submit (3),
-.BR io_uring_for_each_cqe (3),
-.BR io_uring_wait_cqe_timeout (3),
-.BR io_uring_wait_cqe (3)
diff --git a/src/liburing/man/io_uring_wait_cqes_min_timeout.3 b/src/liburing/man/io_uring_wait_cqes_min_timeout.3
deleted file mode 100644
index e3d9849d44b6..000000000000
--- a/src/liburing/man/io_uring_wait_cqes_min_timeout.3
+++ /dev/null
@@ -1,76 +0,0 @@
-.\" Copyright (C) 2024 Jens Axboe <axboe@kernel.dk>
-.\"
-.\" SPDX-License-Identifier: LGPL-2.0-or-later
-.\"
-.TH io_uring_wait_cqes_min_timeout 3 "Feb 13, 2024" "liburing-2.8" "liburing Manual"
-.SH NAME
-io_uring_wait_cqes_min_timeout \- wait for completions with both batch and normal timeout
-.SH SYNOPSIS
-.nf
-.B #include <liburing.h>
-.PP
-.BI "int io_uring_wait_cqes_min_timeout(struct io_uring *" ring ","
-.BI " struct io_uring_cqe **" cqe_ptr ","
-.BI " unsigned " wait_nr ","
-.BI " struct __kernel_timespec *" ts ","
-.BI " unsigned int " min_wait_usec ",
-.BI " sigset_t *" sigmask ");"
-.fi
-.SH DESCRIPTION
-.PP
-The
-.BR io_uring_wait_cqes_min_timeout (3)
-waits for completions from the submission queue belonging to the
-.I ring
-and waits for
-.I wait_nr
-completion events, or until the timeout
-.I ts
-expires. The completion events are stored in the
-.I cqe_ptr
-array. If non-zero,
-.I min_wait_usec
-denotes a timeout for the
-.I wait_nr
-batch.
-
-The
-.I sigmask
-specifies the set of signals to block. If set, it is equivalent to atomically
-executing the following calls:
-.PP
-.in +4n
-.EX
-sigset_t origmask;
-
-pthread_sigmask(SIG_SETMASK, &sigmask, &origmask);
-ret = io_uring_wait_cqes_min_timeout(ring, cqe, wait_nr, ts, min_wait, NULL);
-pthread_sigmask(SIG_SETMASK, &origmask, NULL);
-.EE
-.in
-.PP
-This works like
-.BR io_uring_submit_and_wait_min_timeout (3)
-except that it doesn't submit requests. See that man page for a description
-for how the min timeout waiting works.
-
-Available since 6.12.
-
-.SH RETURN VALUE
-On success
-.BR io_uring_wait_cqes_min_timeout (3)
-returns the 0.On failure it returns
-.BR -errno .
-If the kernel doesn't support this functionality,
-.BR -EINVAL
-will be returned. See note on the feature flag.
-The most common failure case is not receiving a completion within the specified
-timeout,
-.B -ETIME
-is returned in this case.
-.SH SEE ALSO
-.BR io_uring_wait_cqe (3),
-.BR io_uring_wait_cqes (3),
-.BR io_uring_wait_cqe_timeout (3),
-.BR io_uring_wait_cqes (3),
-.BR io_uring_submit_and_wait_min_timeout (3)
base-commit: 148b8774e92b345b06e8cc3e127799f066b68480
--
Ahmad Gani
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [PATCH gwproxy v2 0/3] Minor changes and fixes
2025-07-29 2:53 ` [PATCH gwproxy v1 0/3] Minor changes and fixes Ammar Faizi
2025-07-29 3:08 ` [PATCH gwproxy v2] io_uring: Reduce liburing code base Ahmad Gani
@ 2025-07-29 3:47 ` Ahmad Gani
2025-07-29 3:47 ` [PATCH gwproxy v2 1/3] io_uring: Add liburing to the code base Ahmad Gani
` (3 more replies)
1 sibling, 4 replies; 11+ messages in thread
From: Ahmad Gani @ 2025-07-29 3:47 UTC (permalink / raw)
To: ammarfaizi2; +Cc: gwml, reyuki
On Tue, 29 Jul 2025 09:53:41 +0700, Ammar Faizi wrote:
>> io_uring: Add liburing to the code base
>
> This one feels too big. Let's not bring liburing tests and liburing
> manpages.
As discussed in the voice chat, let's use git submodule instead.
This is v2 revision of patches that contain the following changes:
- add liburing to the code base
- add macro guard
- fix undeclared GWP_CONN_FLAG_IS_CANCEL macro
My Linux distro didn't have a static version of the liburing library.
Let's just embed the liburing source code directly into the code base.
VS Code's C/C++ linter was complaining about an undefined struct member.
Adding a macro guard resolved the warning, although I later discovered
that configuring the defines array in c_cpp_properties.json also fixes
the issue, but it's still nice to have macro guard as a safe fallback.
And I noticed that declaration of GWP_CONN_FLAG_IS_CANCEL is missing, and
have now declared it.
## Changelog
v1 -> v2:
- Using git submodule instead of pulling the code base directly.
Signed-off-by: Ahmad Gani <reyuki@gnuweeb.org>
---
Ahmad Gani (3):
io_uring: Add liburing to the code base
io_uring: Add macro guard
io_uring: Rename GWP_CONN_FLAG_IS_SHUTDOWN to GWP_CONN_FLAG_IS_CANCEL
.gitmodules | 4 ++++
Makefile | 10 ++++++++--
src/gwproxy/ev/io_uring.c | 13 +++++++++----
src/gwproxy/gwproxy.h | 2 +-
src/liburing | 1 +
5 files changed, 23 insertions(+), 7 deletions(-)
create mode 100644 .gitmodules
create mode 160000 src/liburing
base-commit: 06fa2ea2ba4acee27d03b7f467012b403df1f48c
--
Ahmad Gani
^ permalink raw reply [flat|nested] 11+ messages in thread
* [PATCH gwproxy v2 1/3] io_uring: Add liburing to the code base
2025-07-29 3:47 ` [PATCH gwproxy v2 0/3] Minor changes and fixes Ahmad Gani
@ 2025-07-29 3:47 ` Ahmad Gani
2025-07-29 15:06 ` Ammar Faizi
2025-07-29 3:47 ` [PATCH gwproxy v2 2/3] io_uring: Add macro guard Ahmad Gani
` (2 subsequent siblings)
3 siblings, 1 reply; 11+ messages in thread
From: Ahmad Gani @ 2025-07-29 3:47 UTC (permalink / raw)
To: ammarfaizi2; +Cc: gwml, reyuki
Make the build process easier.
Some people may not have had liburing installed on their system.
Signed-off-by: Ahmad Gani <reyuki@gnuweeb.org>
---
.gitmodules | 4 ++++
Makefile | 10 ++++++++--
src/liburing | 1 +
3 files changed, 13 insertions(+), 2 deletions(-)
create mode 100644 .gitmodules
create mode 160000 src/liburing
diff --git a/.gitmodules b/.gitmodules
new file mode 100644
index 000000000000..d49ed8e6e06f
--- /dev/null
+++ b/.gitmodules
@@ -0,0 +1,4 @@
+[submodule "src/liburing"]
+ path = src/liburing
+ url = https://github.com/axboe/liburing
+ branch = master
diff --git a/Makefile b/Makefile
index 0fea43c9fce7..e5e0f756936a 100644
--- a/Makefile
+++ b/Makefile
@@ -9,6 +9,7 @@ LIBS = -lpthread
DEPFLAGS = -MMD -MP -MF $@.d
LDFLAGS_SHARED = $(LDFLAGS) -shared -fpic -fPIC
GWPROXY_DIR = ./src/gwproxy
+LIBURING_DIR = ./src/liburing/src
ifeq ($(SANITIZE),1)
CFLAGS += -fsanitize=address -fsanitize=undefined
@@ -30,6 +31,8 @@ ifeq ($(STATIC),1)
LDFLAGS += -static
endif
+LIBURING_TARGET = $(LIBURING_DIR)/liburing.a
+
GWPROXY_TARGET = gwproxy
GWPROXY_CC_SOURCES = \
$(GWPROXY_DIR)/gwproxy.c \
@@ -39,7 +42,7 @@ GWPROXY_CC_SOURCES = \
ifeq ($(CONFIG_IO_URING),1)
CFLAGS += -DCONFIG_IO_URING
- LIBS += /usr/lib/liburing.a
+ LIBS += $(LIBURING_TARGET)
GWPROXY_CC_SOURCES += $(GWPROXY_DIR)/ev/io_uring.c
endif
@@ -66,7 +69,10 @@ ALL_DEPFILES = $(ALL_OBJECTS:.o=.o.d)
ALL_GWPROXY_OBJECTS = $(GWPROXY_OBJECTS) $(LIBGWPSOCKS5_OBJECTS) $(LIBGWDNS_OBJECTS)
-all: $(GWPROXY_TARGET) $(LIBGWPSOCKS5_TARGET) $(LIBGWDNS_TARGET)
+all: $(GWPROXY_TARGET) $(LIBGWPSOCKS5_TARGET) $(LIBGWDNS_TARGET) $(LIBURING_TARGET)
+
+$(LIBURING_TARGET): $(LIBURING_DIR)
+ @$(MAKE) -C $^
$(GWPROXY_TARGET): $(ALL_GWPROXY_OBJECTS)
$(CC) $(LDFLAGS) -o $@ $^ $(LIBS)
diff --git a/src/liburing b/src/liburing
new file mode 160000
index 000000000000..f2b6fb85b79b
--- /dev/null
+++ b/src/liburing
@@ -0,0 +1 @@
+Subproject commit f2b6fb85b79baf17f2c0ea24a357c652caa2d7ba
--
Ahmad Gani
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [PATCH gwproxy v2 2/3] io_uring: Add macro guard
2025-07-29 3:47 ` [PATCH gwproxy v2 0/3] Minor changes and fixes Ahmad Gani
2025-07-29 3:47 ` [PATCH gwproxy v2 1/3] io_uring: Add liburing to the code base Ahmad Gani
@ 2025-07-29 3:47 ` Ahmad Gani
2025-07-29 3:47 ` [PATCH gwproxy v2 3/3] io_uring: Rename GWP_CONN_FLAG_IS_SHUTDOWN to GWP_CONN_FLAG_IS_CANCEL Ahmad Gani
2025-07-29 3:50 ` [PATCH gwproxy v2 0/3] Minor changes and fixes Ammar Faizi
3 siblings, 0 replies; 11+ messages in thread
From: Ahmad Gani @ 2025-07-29 3:47 UTC (permalink / raw)
To: ammarfaizi2; +Cc: gwml, reyuki
To prevent linter error from text editor such as VSCode.
Signed-off-by: Ahmad Gani <reyuki@gnuweeb.org>
---
src/gwproxy/ev/io_uring.c | 5 +++++
1 file changed, 5 insertions(+)
diff --git a/src/gwproxy/ev/io_uring.c b/src/gwproxy/ev/io_uring.c
index 5b8785ade49f..e7696efbf4aa 100644
--- a/src/gwproxy/ev/io_uring.c
+++ b/src/gwproxy/ev/io_uring.c
@@ -2,6 +2,9 @@
/*
* Copyright (C) 2025 Ammar Faizi <ammarfaizi2@gnuweeb.org>
*/
+
+#ifdef CONFIG_IO_URING
+
#ifndef _GNU_SOURCE
#define _GNU_SOURCE
#endif
@@ -764,3 +767,5 @@ void gwp_ctx_signal_all_io_uring(struct gwp_ctx *ctx)
io_uring_submit_eintr(&we->iou->ring, 8);
}
+
+#endif // CONFIG_IO_URING
--
Ahmad Gani
^ permalink raw reply related [flat|nested] 11+ messages in thread
* [PATCH gwproxy v2 3/3] io_uring: Rename GWP_CONN_FLAG_IS_SHUTDOWN to GWP_CONN_FLAG_IS_CANCEL
2025-07-29 3:47 ` [PATCH gwproxy v2 0/3] Minor changes and fixes Ahmad Gani
2025-07-29 3:47 ` [PATCH gwproxy v2 1/3] io_uring: Add liburing to the code base Ahmad Gani
2025-07-29 3:47 ` [PATCH gwproxy v2 2/3] io_uring: Add macro guard Ahmad Gani
@ 2025-07-29 3:47 ` Ahmad Gani
2025-07-29 3:50 ` [PATCH gwproxy v2 0/3] Minor changes and fixes Ammar Faizi
3 siblings, 0 replies; 11+ messages in thread
From: Ahmad Gani @ 2025-07-29 3:47 UTC (permalink / raw)
To: ammarfaizi2; +Cc: gwml, reyuki
A previous commit forgot to replace GWP_CONN_FLAG_IS_SHUTDOWN and leading to
build error on debug mode, it wasn't detected on release mode.
Fixes: 06fa2ea2ba4a ("io_uring: Replace prep_shutdown() with prep_cancel()")
Signed-off-by: Ahmad Gani <reyuki@gnuweeb.org>
---
src/gwproxy/ev/io_uring.c | 8 ++++----
src/gwproxy/gwproxy.h | 2 +-
2 files changed, 5 insertions(+), 5 deletions(-)
diff --git a/src/gwproxy/ev/io_uring.c b/src/gwproxy/ev/io_uring.c
index e7696efbf4aa..ca7178476f9f 100644
--- a/src/gwproxy/ev/io_uring.c
+++ b/src/gwproxy/ev/io_uring.c
@@ -318,7 +318,7 @@ static void shutdown_gcp(struct gwp_wrk *w, struct gwp_conn_pair *gcp)
struct gwp_ctx *ctx = w->ctx;
struct io_uring_sqe *s;
- if (gcp->flags & GWP_CONN_FLAG_IS_SHUTDOWN)
+ if (gcp->flags & GWP_CONN_FLAG_IS_CANCEL)
return;
if (gcp->target.fd >= 0) {
@@ -339,7 +339,7 @@ static void shutdown_gcp(struct gwp_wrk *w, struct gwp_conn_pair *gcp)
get_gcp(gcp);
}
- gcp->flags |= GWP_CONN_FLAG_IS_SHUTDOWN;
+ gcp->flags |= GWP_CONN_FLAG_IS_CANCEL;
}
static int arm_gcp(struct gwp_wrk *w, struct gwp_conn_pair *gcp)
@@ -640,7 +640,7 @@ static int handle_event(struct gwp_wrk *w, struct io_uring_cqe *cqe)
break;
case EV_BIT_TARGET_CANCEL:
pr_dbg(&ctx->lh, "Handling target cancel event: %d", cqe->res);
- assert(gcp->flags & GWP_CONN_FLAG_IS_SHUTDOWN);
+ assert(gcp->flags & GWP_CONN_FLAG_IS_CANCEL);
r = 0;
break;
case EV_BIT_CLIENT_CANCEL:
@@ -661,7 +661,7 @@ static int handle_event(struct gwp_wrk *w, struct io_uring_cqe *cqe)
gcp = udata;
if ((gcp->flags & GWP_CONN_FLAG_IS_DYING) &&
- !(gcp->flags & GWP_CONN_FLAG_IS_SHUTDOWN))
+ !(gcp->flags & GWP_CONN_FLAG_IS_CANCEL))
shutdown_gcp(w, gcp);
put_gcp(w, gcp);
diff --git a/src/gwproxy/gwproxy.h b/src/gwproxy/gwproxy.h
index 86c1a05458ad..4b0fdfb37f73 100644
--- a/src/gwproxy/gwproxy.h
+++ b/src/gwproxy/gwproxy.h
@@ -99,7 +99,7 @@ enum {
*/
GWP_CONN_FLAG_NO_CLOSE_FD = (1ull << 0ull),
GWP_CONN_FLAG_IS_DYING = (1ull << 1ull),
- GWP_CONN_FLAG_IS_SHUTDOWN = (1ull << 2ull),
+ GWP_CONN_FLAG_IS_CANCEL = (1ull << 2ull),
};
struct gwp_conn_pair {
--
Ahmad Gani
^ permalink raw reply related [flat|nested] 11+ messages in thread
* Re: [PATCH gwproxy v2 0/3] Minor changes and fixes
2025-07-29 3:47 ` [PATCH gwproxy v2 0/3] Minor changes and fixes Ahmad Gani
` (2 preceding siblings ...)
2025-07-29 3:47 ` [PATCH gwproxy v2 3/3] io_uring: Rename GWP_CONN_FLAG_IS_SHUTDOWN to GWP_CONN_FLAG_IS_CANCEL Ahmad Gani
@ 2025-07-29 3:50 ` Ammar Faizi
3 siblings, 0 replies; 11+ messages in thread
From: Ammar Faizi @ 2025-07-29 3:50 UTC (permalink / raw)
To: Ahmad Gani; +Cc: Ammar Faizi, gwml
On Tue, 29 Jul 2025 10:47:16 +0700, Ahmad Gani wrote:
> On Tue, 29 Jul 2025 09:53:41 +0700, Ammar Faizi wrote:
> >> io_uring: Add liburing to the code base
> >
> > This one feels too big. Let's not bring liburing tests and liburing
> > manpages.
>
> As discussed in the voice chat, let's use git submodule instead.
>
> [...]
Applied, thanks!
[1/3] io_uring: Add liburing to the code base
commit: 10ee5b83b50f9f454b893e36e8fc5611615c1ffd
[2/3] io_uring: Add macro guard
commit: 8fa0bafbfab9037d2e436e4aba693731114e9fa7
[3/3] io_uring: Rename GWP_CONN_FLAG_IS_SHUTDOWN to GWP_CONN_FLAG_IS_CANCEL
commit: be5eeab266d36129f722fb023a7d3715a5e125cb
Best regards,
--
Ammar Faizi
^ permalink raw reply [flat|nested] 11+ messages in thread
* Re: [PATCH gwproxy v2 1/3] io_uring: Add liburing to the code base
2025-07-29 3:47 ` [PATCH gwproxy v2 1/3] io_uring: Add liburing to the code base Ahmad Gani
@ 2025-07-29 15:06 ` Ammar Faizi
0 siblings, 0 replies; 11+ messages in thread
From: Ammar Faizi @ 2025-07-29 15:06 UTC (permalink / raw)
To: Ahmad Gani; +Cc: gwml
On Tue, Jul 29, 2025 at 10:47:17AM +0700, Ahmad Gani wrote:
> Make the build process easier.
> Some people may not have had liburing installed on their system.
This breaks a clean build where liburing's ./configure script has not
been invoked. I have pushed a fix for this.
https://github.com/GNUWeeb/gwproxy/commit/76045a47aeaf1ef482d2afa0b2e9c54ae4c8847a
--
Ammar Faizi
^ permalink raw reply [flat|nested] 11+ messages in thread
end of thread, other threads:[~2025-07-29 15:06 UTC | newest]
Thread overview: 11+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2025-07-29 2:48 [PATCH gwproxy v1 0/3] Minor changes and fixes Ahmad Gani
2025-07-29 2:48 ` [PATCH gwproxy v1 2/3] io_uring: Add macro guard Ahmad Gani
2025-07-29 2:48 ` [PATCH gwproxy v1 3/3] io_uring: Rename GWP_CONN_FLAG_IS_SHUTDOWN to GWP_CONN_FLAG_IS_CANCEL Ahmad Gani
2025-07-29 2:53 ` [PATCH gwproxy v1 0/3] Minor changes and fixes Ammar Faizi
2025-07-29 3:08 ` [PATCH gwproxy v2] io_uring: Reduce liburing code base Ahmad Gani
2025-07-29 3:47 ` [PATCH gwproxy v2 0/3] Minor changes and fixes Ahmad Gani
2025-07-29 3:47 ` [PATCH gwproxy v2 1/3] io_uring: Add liburing to the code base Ahmad Gani
2025-07-29 15:06 ` Ammar Faizi
2025-07-29 3:47 ` [PATCH gwproxy v2 2/3] io_uring: Add macro guard Ahmad Gani
2025-07-29 3:47 ` [PATCH gwproxy v2 3/3] io_uring: Rename GWP_CONN_FLAG_IS_SHUTDOWN to GWP_CONN_FLAG_IS_CANCEL Ahmad Gani
2025-07-29 3:50 ` [PATCH gwproxy v2 0/3] Minor changes and fixes Ammar Faizi
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox