Comment 5 for bug 883374

How exactly should we go into a 'wait state'? The sleep(2) system call is supposed to do that. Switching to some other work until the delay is up is a much better solution, as long as we can guarantee we will continue to transmit before the delay is up. Going into a busyloop in userspace is, IMO, the worst idea; it can pin a CPU completely and it will definitely cause problems for the scheduler (which is already being overloaded with our 16+ threads).