On 11/04/2010 03:23 PM, Josh Blum wrote:
Well, there is extra overhead. A "pirate" thread in the the receive
path spins on the socket and inspects the contents. The packet may be
an asynchronous message packet for flow control or destined for the
user. Or it may be a data packet, in which case it is placed into a
queue to be popped off by the device::recv() call. No extra memcopies,
its just managing pointers.
When you say that this thread "spins", do you mean that it's in an
infinite loop, waiting on blocking,
or non-blocking I/O? That is, does it pause while it waits for data,
or is it in a tight CPU loop?