Provided by: manpages-dev_3.01-1_all
io_setup - create an asynchronous I/O context
int io_setup(unsigned nr_events, aio_context_t *ctxp);
Link with -laio.
io_setup() creates an asynchronous I/O context capable of receiving at
least nr_events. ctxp must not point to an AIO context that already
exists, and must be initialized to 0 prior to the call. On successful
creation of the AIO context, *ctxp is filled in with the resulting
On success, io_setup() returns 0. For the failure return, see NOTES.
io_setup() returns 0 on success; on failure, it returns one of the
errors listed under ERRORS.
EAGAIN The specified nr_events exceeds the user’s limit of available
EFAULT An invalid pointer is passed for ctxp.
EINVAL ctxp is not initialized, or the specified nr_events exceeds
internal limits. nr_events should be greater than 0.
ENOMEM Insufficient kernel resources are available.
ENOSYS io_setup() is not implemented on this architecture.
The asynchronous I/O system calls first appeared in Linux 2.5, August
io_setup() is Linux-specific and should not be used in programs that
are intended to be portable.
Glibc does not provide a wrapper function for this system call.
The wrapper provided in libaio for io_setup() does not follow the usual
C library conventions for indicating error: on error it returns a
negated error number (the negative of one of the values listed in
ERRORS). If the system call is invoked via syscall(2), then the return
value follows the usual conventions for indicating an error: -1, with
errno set to a (positive) value that indicates the error.
io_cancel(2), io_destroy(2), io_getevents(2), io_submit(2)
This page is part of release 3.01 of the Linux man-pages project. A
description of the project, and information about reporting bugs, can
be found at http://www.kernel.org/doc/man-pages/.