> Andi Kleen wrote:
> > Once you get through again TCP will reset the timeouts itself as it
> > receives new ACKs.
>
> Not if TCP does not retry for the duration of your "connected" window,
> say 5 minutes...
It does. The retransmit timeout is clamped at 120s, when there is anything
to send, and no timeout when there is nothing to send (except for keepalives,
but these are only turned on by some applications)
> Also, I'm not convinced TCP resets the timeouts when they are so large
> so much as takes them back down slowly. This is useless if your
> connection disappeared for a few minutes and then TCP takes longer than
> you have left to recover.
It does. The rtt estimate TCP keeps is independent from the retransmit
timeout (tp->rto vs tp->srtt). The rtt estimate only changes based on
new incoming acks, and only for ACKs where TCP knows that the packets
causing them have not been retransmitted.
-Andi
-- This is like TV. I don't like TV.- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.rutgers.edu Please read the FAQ at http://www.tux.org/lkml/