*nix Documentation Project
·  Home
 +   man pages
·  Linux HOWTOs
·  FreeBSD Tips
·  *niX Forums

  man pages->IRIX man pages -> aio_suspend (3)              



NAME    [Toc]    [Back]

     aio_suspend, aio_suspend64	- wait for an asynchronous I/O request

C SYNOPSIS    [Toc]    [Back]

     #include <aio.h>

     int aio_suspend(const aiocb_t * const aiocbp[], int cnt, const timespec_t *timeout);

     int aio_suspend64(const aiocb64_t * const aiocbp[], int cnt, const	timespec_t *timeout);

DESCRIPTION    [Toc]    [Back]

     The aio_suspend() function	shall suspend the calling thread until at
     least one of the asynchronous I/O operations referenced by	the aiocbp
     argument has completed, until a signal interrupts the function, or	if
     timeout is	not NULL, until	the time interval specified by timeout has
     passed. If	any of the aiocb structures in the list	correspond to the
     completed asynchronous I/O	operations(i.e., the error status for the
     operation is not equal to EINPROGRESS, at the time	of the call), the
     function shall return without suspending the calling thread. The aiocbp
     argument points to	an array of pointers to	asynchronous I/O control
     blocks. The cnt argument indicates	the number of elements in the array.
     Each aiocb	structure pointed to shall have	been used in initiating	an
     asynchronous I/O request via aio_read(), aio_write(), or lio_listio().
     This array	may contain NULL pointers which	shall be ignored. If this
     array contains pointers that refer	to aiocb structures which have not
     been used in submitting asynchronous I/O, the effect is undefined.

     The aio_suspend64() function is identical to aio_suspend()	except that it
     takes an  array of	aiocb64_t * (see <aio.h>).  This structure allows for
     the specification of a file offset	greater	than 2 Gigabytes.  The user
     must define _ABI_SOURCE and include -labi to access the aio64 routines.

     If	the time interval indicated in the timespec structure pointed to by
     timeout passes before any of the I/O operations referenced	by aiocbp are
     completed,	then aio_suspend() shall return	with an	error.

SEE ALSO    [Toc]    [Back]

     aio_read(3), aio_write(3),	lio_listio(3), aio_sgi_init(3)

DIAGNOSTICS    [Toc]    [Back]

     If	the aio_suspend() function returns after one or	more asynchronous I/O
     operations	has completed, zero is returned.

     The application may determine which asynchronous I/O completed by
     scanning the associated error and return status, using aio_error(3) and
     aio_return(3), respectively.

     If	any of the following conditions	occur, the aio_suspend() function
     shall return -1 and set errno to the corresponding	value.

									Page 1


     [EAGAIN]	    No asynchronous I/O	indicated in the list referenced by
		    aiocbp completed in	the time interval indicated by

     [EINTR]	    A signal interrupted the aio_suspend() function. Note
		    that, since	each asynchronous I/O operation	may possibly
		    provoke a signal when it completes,	this error return may
		    be caused by the completion	of one (or more) of the	very
		    I/O	operation being	awaited.

     [EAGAIN]	    The	system was short of resources and unable to wait for

									PPPPaaaaggggeeee 2222
[ Back ]
 Similar pages
Name OS Title
aio_waitcomplete FreeBSD wait for the next completion of an aio request
aio_cancel IRIX cancel an asynchronous I/O request
aio_suspend HP-UX wait for an asynchronous I/O operation to complete
glfinishasyncsgix IRIX wait for completion of an asynchronous command
aio_reap HP-UX wait for multiple asynchronous I/O requests
vwaitforio OpenBSD wait for all outstanding asynchronous writes
aio_read Tru64 Queues a single asynchronous read request
aio_write Tru64 Queues a single asynchronous write request (P1003.1b)
mq_notify Tru64 Attaches a request for asynchronous signal notification to a message queue (P1003.1b)
aio FreeBSD asynchronous I/O
Copyright © 2004-2005 DeniX Solutions SRL
newsletter delivery service