io_setup(2)

1IO_SETUP(2)                Linux Programmer's Manual               IO_SETUP(2)
2
3
4

NAME

6       io_setup - create an asynchronous I/O context
7

SYNOPSIS

9       #include <linux/aio_abi.h>          /* Defines needed types */
10
11       int io_setup(unsigned nr_events, aio_context_t *ctx_idp);
12
13       Note: There is no glibc wrapper for this system call; see NOTES.
14

DESCRIPTION

16       The io_setup() system call creates an asynchronous I/O context suitable
17       for concurrently processing nr_events operations.  The ctx_idp argument
18       must  not point to an AIO context that already exists, and must be ini‐
19       tialized to 0 prior to the call.  On successful  creation  of  the  AIO
20       context, *ctx_idp is filled in with the resulting handle.
21

RETURN VALUE

23       On success, io_setup() returns 0.  For the failure return, see NOTES.
24

ERRORS

26       EAGAIN The  specified  nr_events  exceeds the user's limit of available
27              events, as defined in /proc/sys/fs/aio-max-nr.
28
29       EFAULT An invalid pointer is passed for ctx_idp.
30
31       EINVAL ctx_idp is not initialized, or the specified  nr_events  exceeds
32              internal limits.  nr_events should be greater than 0.
33
34       ENOMEM Insufficient kernel resources are available.
35
36       ENOSYS io_setup() is not implemented on this architecture.
37

VERSIONS

39       The asynchronous I/O system calls first appeared in Linux 2.5.
40

CONFORMING TO

42       io_setup()  is  Linux-specific  and should not be used in programs that
43       are intended to be portable.
44

NOTES

46       Glibc does not provide a wrapper function for this  system  call.   You
47       could  invoke  it  using syscall(2).  But instead, you probably want to
48       use the io_setup() wrapper function provided by libaio.
49
50       Note that the libaio wrapper function uses a  different  type  (io_con‐
51       text_t *)  for the ctx_idp argument.  Note also that the libaio wrapper
52       does not follow the usual C library conventions for indicating  errors:
53       on  error it returns a negated error number (the negative of one of the
54       values  listed  in  ERRORS).   If  the  system  call  is  invoked   via
55       syscall(2),  then  the  return  value follows the usual conventions for
56       indicating an error: -1, with errno set  to  a  (positive)  value  that
57       indicates the error.
58

COLOPHON

63       This  page  is  part of release 3.53 of the Linux man-pages project.  A
64       description of the project, and information about reporting  bugs,  can
65       be found at http://www.kernel.org/doc/man-pages/.
66
67
68
69Linux                             2013-06-21                       IO_SETUP(2)