Re: [Kiobuf-io-devel] RFC: Kernel mechanism: Compound event wait
Jens Axboe (firstname.lastname@example.org)
Tue, 6 Feb 2001 23:09:29 +0100
On Tue, Feb 06 2001, Marcelo Tosatti wrote:
> > > > We don't even need that, non-blocking is implicitly applied with READA.
> > > >
> > > READA just returns - I doubt that the aio functions should poll until
> > > there are free entries in the request queue.
> > The aio functions should NOT use READA/WRITEA. They should just use the
> > normal operations, waiting for requests. The things that makes them
> > asycnhronous is not waiting for the requests to _complete_. Which you can
> > already do, trivially enough.
> Reading write(2):
> EAGAIN Non-blocking I/O has been selected using O_NONBLOCK and there was
> no room in the pipe or socket connected to fd to write the data
> I see no reason why "aio function have to block waiting for requests".
That was my reasoning too with READA etc, but Linus seems to want that we
can block while submitting the I/O (as throttling, Linus?) just not
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to email@example.com
Please read the FAQ at http://www.tux.org/lkml/