netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Wesley Eddy <weddy@grc.nasa.gov>
To: Horst von Brand <vonbrand@inf.utfsm.cl>
Cc: netdev@oss.sgi.com, linux-kernel@vger.kernel.org
Subject: Re: TCP rto estimation patch
Date: Fri, 23 Apr 2004 16:44:34 -0400	[thread overview]
Message-ID: <20040423204434.GA7492@grc.nasa.gov> (raw)
In-Reply-To: <200404231735.i3NHZRp3012111@eeyore.valparaiso.cl>

[-- Attachment #1: Type: text/plain, Size: 944 bytes --]

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 #2: Type: application/pgp-signature, Size: 189 bytes --]

  reply	other threads:[~2004-04-23 20:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-23 14:24 TCP rto estimation patch Wesley Eddy
2004-04-23 17:35 ` Horst von Brand
2004-04-23 20:44   ` Wesley Eddy [this message]
2004-04-23 21:06 ` David Stevens
2004-04-23 21:09   ` David S. Miller
2004-04-23 23:19   ` Wesley Eddy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20040423204434.GA7492@grc.nasa.gov \
    --to=weddy@grc.nasa.gov \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@oss.sgi.com \
    --cc=vonbrand@inf.utfsm.cl \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).