Re: Kernel bug handling TCP_RTO_MAX?

[Matti Aarnio <matti.aarnio@zmailer.org>]

On Thu, Dec 12, 2002 at 08:15:42PM +0100, Andreani Stefano wrote:
> Problem: I need to change the max value of the TCP retransmission timeout. 
...
> #define TCP_RTO_MAX	((unsigned)(6*HZ)) //It was: ((unsigned)(120*HZ))
> 
> Then I recompiled the kernel, rebooted the machine and tested the 
> solution. The result I obtained was the same I had before this 
> modification. 

  Oh, you want to cap the retransmit time to 6 seconds so that
  TCP works (at least somehow) in a terribly lossy network ?

  Having that _low_ value at it isn't advisable in the general
  internet, but these modern mobile networks with paketized data
  are pain with dramatically varying latencies.  TCP works
  badly in such environments.  X.25 works better - to a degree..


  Changeing the value, and doing "make clean; make bzImage"
  should give you a kernel with it in.


..
> Could it be a bug on the RTO calculation algorithm, or there is 
> something I mistook?

  Possibly omitting "make clean" -- short-cutting it can be done
  by:  "rm net/ipv4/*.o"   I think..

> This is the first time I get into the linux kernel, so please be 
> patient!
> 
> Thanks,
> Stefano.
> -------------------------------
>         Stefano Andreani
>     Freelance ICT Consultant
>       H3G IOT Team - Italy
>       tel. +39 347 8215965
>    stefano.andreani.ap@h3g.it

/Matti Aarnio