glibc aio performance

[Tom Gall]

Amos P Waterland wrote:
> Don Capps wrote:
> > 5. Normal read/write have a nice fast I/O completion notification model
> that is implemented in the
> >    operating system. POSIX async I/O was a "group think" design and has a
> very poor I/O completion
> >    model that slows things down. Polling for I/O completion or signals
> was and is a very poor design.
> >    Most vendors have custom async I/O routines that have a fast I/O
> completion
> >    mechanism. (call back notification)
> 
> While I am not completely enamoured with the POSIX design, I do believe
> they did include a facility for callbacks.  I wrote a small program that
> shows how to use POSIX real-time signals to pass a signal handler an
> arbitrary pointer upon completion of an AIO write:

It might be an interesting question to see how many of the "vendor
custom
aio routines" also don't have posix realtime signals.

regards,

Tom
-- 
Tom Gall - [embedded] [PPC64 | PPC32] Code Monkey
Peace, Love &                  "Where's the ka-boom? There was
Linux Technology Center         supposed to be an earth
http://www.ibm.com/linux/ltc/   shattering ka-boom!"
(w) tom_gall@vnet.ibm.com       -- Marvin Martian
(w) 507-253-4558
(h) tgall@rochcivictheatre.org