Currently the io_setup.2 man page describes what the kernel really does, i.e. that the resulting context may be able to hold more than the nr_events operations because the memory allocated in kernel is rounded to be multiple of page size. It is be better not to expose this implementation detail and simply state that the resulting context is suitable for nr_events operations. Signed-off-by: Cyril Hrubis <chrubis@xxxxxxx> Acked-by: Jeff Moyer <jmoyer@xxxxxxxxxx> --- man2/io_setup.2 | 4 ++-- 1 files changed, 2 insertions(+), 2 deletions(-) diff --git a/man2/io_setup.2 b/man2/io_setup.2 index 81b9a8b..ffa3972 100644 --- a/man2/io_setup.2 +++ b/man2/io_setup.2 @@ -21,8 +21,8 @@ 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 of concurrently processing -at least \fInr_events\fP. +creates an asynchronous I/O context suitable for concurrently processing +\fInr_events\fP operations. The .I ctx_idp argument must not point to an AIO context that already exists, and must -- 1.7.8.6 -- Cyril Hrubis chrubis@xxxxxxx -- 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
