Actually, that overhead is not entirely wasted. For example, on Solaris (unlike Linux), Asynchronous I/O is supported for network sockets. (In fairness, Windo

Actually, that overhead is not entirely wasted. For example, on Solaris (unlike Linux), Asynchronous I/O is supported for network sockets. (In fairness, Windows also supports it.) As another example, Solaris has the event completion framework which is also available when using sockets: https://blogs.oracle.com/barts/entry/entry_2_event_ports https://blogs.oracle.com/barts/entry/entry_2_event_ports So I wonder how much of this is the platform implementation they were testing instead of their new API? It's unclear from their presentation materials whether this is really just covering up for problems in the implementation. I would have liked to have seen more test data comparing this work on multiple platforms.