1 .\" Copyright (C) 2003 Free Software Foundation, Inc.
3 .\" %%%LICENSE_START(GPL_NOVERSION_ONELINE)
4 .\" This file is distributed according to the GNU General Public License.
7 .TH IO_SETUP 2 2021-03-22 "Linux" "Linux Programmer's Manual"
9 io_setup \- create an asynchronous I/O context
12 .BR "#include <linux/aio_abi.h>" " /* Defines needed types */"
14 .BI "long io_setup(unsigned int " nr_events ", aio_context_t *" ctx_idp );
18 There is no glibc wrapper for this system call; see NOTES.
21 this page describes the raw Linux system call interface.
22 The wrapper function provided by
24 uses a different type for the
32 creates an asynchronous I/O context suitable for concurrently processing
33 \fInr_events\fP operations.
36 argument must not point to an AIO context that already exists, and must
37 be initialized to 0 prior to the call.
38 On successful creation of the AIO context, \fI*ctx_idp\fP is filled in
39 with the resulting handle.
44 For the failure return, see NOTES.
48 The specified \fInr_events\fP exceeds the limit of available events,
50 .IR /proc/sys/fs/aio\-max\-nr
55 An invalid pointer is passed for \fIctx_idp\fP.
58 \fIctx_idp\fP is not initialized, or the specified \fInr_events\fP
59 exceeds internal limits.
60 \fInr_events\fP should be greater than 0.
63 Insufficient kernel resources are available.
67 is not implemented on this architecture.
69 The asynchronous I/O system calls first appeared in Linux 2.5.
72 is Linux-specific and should not be used in programs
73 that are intended to be portable.
75 Glibc does not provide a wrapper for this system call.
76 You could invoke it using
78 But instead, you probably want to use the
80 wrapper function provided by
81 .\" http://git.fedorahosted.org/git/?p=libaio.git
86 wrapper function uses a different type
87 .RI ( "io_context_t\ *" )
88 .\" But glibc is confused, since <libaio.h> uses 'io_context_t' to declare
95 wrapper does not follow the usual C library conventions for indicating errors:
96 on error it returns a negated error number
97 (the negative of one of the values listed in ERRORS).
98 If the system call is invoked via
100 then the return value follows the usual conventions for
101 indicating an error: \-1, with
103 set to a (positive) value that indicates the error.
107 .BR io_getevents (2),