> > Is there a reason why SO_TIMESTAMP does not work with TCP sockets > > but only with RAW and UDP ? > > Because it doesn't really make sense?
But it would. It would let me know how long it took the process to get to the data I�m currently reading from the socket. (and notify operator to buy more hardware if it took too long) > > Since the TCP stream may be arbitrarily re-ordered, knowing when a > packet arrived is not particularly useful to an application. If you > really care, you should probably use BPF instead. > Are you suggesting to reimplement TCP sockets in userland? Pete To Unsubscribe: send mail to [EMAIL PROTECTED] with "unsubscribe freebsd-net" in the body of the message
