netdev
[Top] [All Lists]

Re: TCP rto estimation patch

To: Horst von Brand <vonbrand@xxxxxxxxxxxx>
Subject: Re: TCP rto estimation patch
From: Wesley Eddy <weddy@xxxxxxxxxxxx>
Date: Fri, 23 Apr 2004 16:44:34 -0400
Cc: netdev@xxxxxxxxxxx, linux-kernel@xxxxxxxxxxxxxxx
In-reply-to: <200404231735.i3NHZRp3012111@eeyore.valparaiso.cl>
References: <20040423142445.GC501@grc.nasa.gov> <200404231735.i3NHZRp3012111@eeyore.valparaiso.cl>
Reply-to: weddy@xxxxxxxxxxxx
Sender: netdev-bounce@xxxxxxxxxxx
User-agent: Mutt/1.5.5.1i
On Fri, Apr 23, 2004 at 01:35:27PM -0400, Horst von Brand wrote:
> 
> Why RTT_ALPHA and RTTVAR_BETA, and not just RTT_BETA? Or even RTO_xxx?
>

Per the spec, alpha is used to compute rtt and beta likewise for rttvar.
 
> Is there any reason to change them, ever? What happens if you change them?
> Restrictions on values? All this should go with such a patch IMHO (at least
> pointers to relevant discussion).

The information isn't relevant since the patch didn't change them, and if
you were interested in changing the values then simple google search
would return a plethora of research on RTT estimation.

> Must go over it with a fine comb to make sure no unrelated 2 or 3 got
> replaced... out of my league, sorry.

There are stray constants all over the place, which is something that
even freshman computer science students are taught to avoid.  This patch
represents a minor improvement to that situation.

-Wes

Attachment: pgp4F3D4RrTcj.pgp
Description: PGP signature

<Prev in Thread] Current Thread [Next in Thread>