Re: AIO and SHM

We are not actually struggling with AIO, we have or own AIO like
implementation on top of POSIX kernel threads.

AIO does not have the functionality we need. The major drawback is that
there is no open/close AIO calls. The completeion feedback is only a
minor issue.

--
Henrik Nordstrom
Squid hacker
Erik Hofman wrote:
> 
> Hi,
> 
> As I understand most of you are strugling with the AIO implementation.
> Maybe The following (I found on the SGI website) could clear some things
> up for you (as it did for me):
> 
> http://techpubs.sgi.com:80/library/dynaweb_bin/ebt-bin/0650/nph-infosrch.cgi/infosrchtpl/SGI_Developer/T_IRIX_Prog/@InfoSearch__BookTextView/13551;he=0
> 
> >
> > Checking for Completion
> >
> > You have a wide variety of design options other than polling. Your program can:
> >    Use aio_suspend() to wait until one of a list of operations completes.
> >
> >    Set up an empty signal handler function and use sigsuspend() or sigwait() to wait until
> >    a signal arrives (see the sigsuspend(2) and sigwait(3) reference pages).
> >
> >    Use either a signal handler function or a callback function to report completion
> >    - for example, the function can post a semaphore.
> >
> > Most of these methods are demonstrated in the example program under "Asynchronous I/O Example".
> >
>   http://techpubs.sgi.com:80/library/dynaweb_bin/ebt-bin/0650/nph-infosrch.cgi/infosrchtpl/SGI_Developer/T_IRIX_Prog/@ebt-link;he=0?target=%25N%15_13965_START_RESTART_N%
> 
> --
> 
> Regards,
>  Erik Hofman