Thread (22 messages) 22 messages, 7 authors, 2011-08-25

Re: [BUG] tcp : how many times a frame can possibly be retransmitted ?

flat view

From: Ilpo Järvinen <hidden>
Date: 2011-08-25 10:07:40

On Thu, 25 Aug 2011, Eric Dumazet wrote:
Le jeudi 25 août 2011 à 11:56 +0300, Ilpo Järvinen a écrit :
quoted
So you think that this is not true: ?

        /* NOTE: clamping at TCP_RTO_MIN is not required, current algo
         * guarantees that rto is higher.
         */

...it would still be smaller than 1sec though, but certainly not going to 
cause flooding either. Default tcp_rto_min should be 200ms so it's 
5pkts+5ICMP sent, received and processed per second. Which doesn't sound 
that bad CPU load?!?
Unless you have 100.000 active sessions maybe ?

Some years ago, I helped people running servers with more than 1.000.000
long living active sessions, and a temporary network disruption was
already very critical at that time, with old kernels (At that time, IP
route cache could blow away and consume too much ram or cpu time, things
are now under control)

I guess they would not try a new kernel :(
quoted
It is unclear to me how tp->rttvar could become smaller than 
tcp_rto_min().
I believe this part is fine Ilpo.

As long as we handle few tcp sessions, its fine to send 5 messages per
session per second.
Yeah, thanks for the clarification. I was just confused by the initial 
wording of yours which seemed to imply that we could, at worst, end up 
doing it with full rate without any timers.

To me it seems that both cases are quite valid, with pretty much 
contradicting goals.


-- 
 i.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help