> > fact glibc 2.2 has full aio using threads) - you have a whole frame to get > > around to the next one plus any internal buffering > > Sure, and you can get around lack of select() support with threads too. But > it's not very convenient or efficient. What makes you think aio is differently efficient in kernel or user space ? In fact the original aio reference implementors took it out of kernel to user because they found it made no difference
