Andi Kleen writes: > It violates the definition of write() though if the TCP socket is > accessed via write(2), because writes are guaranteed to be atomic. > The later could be fixed by aquiring the inode semaphore in > sock_write, but I'm not sure if it is worth the cycles. Hmmm, do we even know of any implementation that doesn't essentially implement write() via send()/sendmsg()? Later, David S. Miller davem@redhat.com - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org
