nr_events is technically the number of completion events that can be stored in the completion ring. The wording of the man page: "capable of receiving at least nr_events" seems dubious to me, only because I worry that folks might interpret that to mean nr_events total, instead of nr_events concurrently. Further, I've added information on where to find the per-user limit on nr_events, /proc/sys/fs/aio-max-nr. Let me know if you think that is not relevent. Signed-off-by: Jeff Moyer <jmoyer@xxxxxxxxxx> --- man2/io_setup.2 | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff --git a/man2/io_setup.2 b/man2/io_setup.2 index 2a541bf..8527b80 100644 --- a/man2/io_setup.2 +++ b/man2/io_setup.2 @@ -21,7 +21,7 @@ There is no glibc wrapper for this system call; see NOTES. The .BR io_setup () system call -creates an asynchronous I/O context capable of receiving +creates an asynchronous I/O context capable of concurrently processing at least \fInr_events\fP. The .I ctx_idp @@ -37,7 +37,8 @@ For the failure return, see NOTES. .SH ERRORS .TP .B EAGAIN -The specified \fInr_events\fP exceeds the user's limit of available events. +The specified \fInr_events\fP exceeds the user's limit of available events, +as defined in /proc/sys/fs/aio-max-nr. .TP .B EFAULT An invalid pointer is passed for \fIctx_idp\fP. -- 1.7.1 -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
