Davide Libenzi wrote:
>Maybe my understanding of AIO on Linux is limited but how would you do
>async accept/connect ? Will you be using std poll/select for that, and
>then you'll switch to AIO for read/write requests ?
>
If a connection is likely to be idle, one would want to use an async
read poll instead of an async read in order to avoid having to allocate
input buffers to idle connections. (What one really wants is a variant
of async read that allocates an input buffer to an fd at completion
time, not submission time).
Sometimes one wants to use a library which only has a nonblocking
interface, so when the library says WOULDBLOCK you have to do an async
write poll.
Sometimes one wants to use a kernel interface (e.g. sendfile) that does
not yet have an async equivalent. Accept/connect are in this
class--there should be nothing to prevent us from creating async
versions of accept/connect.
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Wed Oct 23 2002 - 22:01:06 EST