#1 Receive queue creates one thread per link (connection).

[Nathan D. Mickulicz]

Upon establishing a connection, the receive queue algorithms use a thread to synchronize client receive notifications (so that no two notifications run in parallel). This is bad, since it defeats the purpose of using thread-pooled I/O. We should allow receives to run in parallel if the client requests it, and these receives can use the existing I/O thread pool (or at least all connections can share a common thread pool).