Linux：io_uring

参考

https://kernel.dk/io_uring.pdf
https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/9.3_release_notes/technology-previews#technology-previews-file-systems-and-storage
https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/9.4_release_notes/kernel_parameters_changes

简介

在下面这个链接里有简单的介绍
https://docs.redhat.com/en/documentation/red_hat_enterprise_linux/9/html/9.3_release_notes/technology-previews#technology-previews-file-systems-and-storage

详细的说明：https://kernel.dk/io_uring.pdf

io_uring_group

1 - A process must either be privileged (CAP_SYS_ADMIN) or be in the io_uring_group group to create an io_uring instance.
-1 (default) - Only processes with the CAP_SYS_ADMIN capability can create io_uring instances.

io_uring_disabled

这个参数默认设置是2，就是禁止用户使用io_uring的功能，是为了安全。这个默认disable的做法应该是一般性的策略，只有用户真正知道自己在干什么的时候，再打开也不晚。
值域：
0 - All processes can create io_uring instances as normal.
1 - io_uring creation is disabled for unprivileged processes not in the io_uring_group group. io_uring_setup() fails with -EPERM. Existing io_uring instances can still be used. See the documentation for io_uring_group for more information.
2 (default) - io_uring creation is disabled for all processes. io_uring_setup() always fails with -EPERM. Existing io_uring instances can still be used.