Christopher Smith wrote:
> The relevant area of concern is aio_buf.
> Shouldn't aio_buf be marked volatile? It certainly is in the case where
> one is providing an async read. Obviously I have similar concerns for
> aiocb64.
I do not know if it is linked but I could not make work
AIO in a stable way. I patched diablo dreaderd (frontal
news server) to allow him to access directly to a spool.
This spool is stored on a netapp, filled by a diablo
spooler. Dreaderd ask to Diablo where an article was
stored and try to load it directly. The version with
normal read is working fine. When using aio_read, it is
working fine for a few minutes under an high load until
the kernel starts to send signal for AIO read completion
while aio_error returns EINPROGRESS. Any idea ?
François
|