[lkml]   [2002]   [Sep]   [5]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: aio-core why not using SuS? [Re: [rfc] aio-core for 2.5.29 (Re: async-io API registration for 2.5.29)]
On Mon, Sep 02, 2002 at 08:40:43PM +0200, Andrea Arcangeli wrote:
> Could somebody explain the semantics of the io_queue_wait call in the
> libaio? If you pass nr == 0 to getevents, getevents will do nothing. I
> don't see the point of it so I'm unsure what's the right implementation.

It was supposed to wait for events to be ready. In reality what ended up
happening is that people don't actually like to use io_queue_run/wait and
the function callbacks as Linus originally suggested in the event model,
and instead they prefer to use io_getevents directly. libaio just hasn't
been updated to reflect that yet.

> then about the 2.5 API we have such min_nr that allows the "at least
> min_nr", instead of the previous default of "at least 1", so that it
> allows implementing the aio_nwait of aix.

It was also required to break source compilation for the timeout update.

> BTW, the libaio I'm adapting to test on my tree will not have the
> libredhat thing anymore, and it will use the mainline 2.5 API since the
> API is registered now and in the very worst case a non backwards
> compatible API change would happen in late 2.5, replacing is
> not more complex than replacing anyways ;).

That was already the intent for libaio-0.4.0.

"You will be reincarnated as a toad; and you will be much happier."
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:28    [W:0.089 / U:0.648 seconds]
©2003-2020 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site