Re: aio_read/write versus O_NONBLOCK (linux context)
- From: David Schwartz <davids@xxxxxxxxxxxxx>
- Date: Mon, 26 May 2008 01:26:03 -0700 (PDT)
On May 24, 4:45 pm, phil-news-nos...@xxxxxxxx wrote:
It appears that aio_read/write are not implemented as system calls. These
appear to be library implementations that presumably call some other system
call. But since O_NONBLOCK does not work on files, it can't be using that.
Anyone know what it is that aio_read/write could be using to request such
I/O from Linux.
Threads.
DS
.
- Follow-Ups:
- Re: aio_read/write versus O_NONBLOCK (linux context)
- From: phil-news-nospam
- Re: aio_read/write versus O_NONBLOCK (linux context)
- References:
- aio_read/write versus O_NONBLOCK (linux context)
- From: phil-news-nospam
- aio_read/write versus O_NONBLOCK (linux context)
- Prev by Date: aio_read/write versus O_NONBLOCK (linux context)
- Next by Date: Writing a simple driver and cross compiling for ARM
- Previous by thread: aio_read/write versus O_NONBLOCK (linux context)
- Next by thread: Re: aio_read/write versus O_NONBLOCK (linux context)
- Index(es):
