> - it assumes we are going to make these complex state machines (which I > don't believe for a second that a real program will do)

They've not had the chance before and there are certain chains of themwhich make huge amounts of sense because you don't want to keep takingcompletion hits. Not so much looping ones but stuff like

cork write sendfile uncork close

are very natural sequences.

There seem to be a lot of typical sequences it doesn't represent however(consider the trivial copy case where you use the result one syscall intothe next)

> - it assumes that we're going to make many async system calls that go > together (which breaks the whole notion of having different libraries > using this for their own internal reasons - they may not even *know* > about other libraries that _also_ do async IO for *their* reasons)

They can each register their own async objects. They need to do thisanyway so that the libraries can use asynchronous I/O and hide it fromapplications.

> this "AIO atom" in the first place, WHICH WE KNOW IS INCORRECT, since > current users use "aio_read()" that simply doesn't have that and > doesn't build up any such data structures.

Do current users do this because that is all they have, because it ishard, or because the current option is all that makes sense ?

The ability to avoid asynchronous completion waits andcomplete/wake/despatch cycles is a good thing of itself. I don't know ifit justifies the rest but it has potential for excellent performance.