Messages in this thread | | | Subject | Re: TCP timestamp option | From | Andi Kleen <> | Date | 21 May 1998 18:09:26 +0200 |
| |
Meelis Roos <mroos@tartu.cyber.ee> writes:
> Why do 2 "nop" tcp options usually precede the timestamp option in tcp > packets generated bly linux tcp stack when the timestamps are enabled? > Is the ip header padding done in options block this way, or is it > something other?
To align the timestamp option to a 32bit boundary. Many CPUs get a significant slowdown while accessing non aligned data.
It is padded in the TCP option space, which is different from the IP options.
> > Also, what's the use of the timestamp option?
More accurate Round Trip Time mesasurement. An accurate RTT estimate is cruicial for TCP's performance to prevent unneeded packet retransmissions.
It also prevents TCP against old packets when very large windows are used.
-Andi
- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu
| |