From: "David S. Miller" <davem@redhat.com>
To: David Stevens <dlstevens@us.ibm.com>
Cc: weddy@grc.nasa.gov, linux-kernel@vger.kernel.org, netdev@oss.sgi.com
Subject: Re: TCP rto estimation patch
Date: Fri, 23 Apr 2004 14:09:13 -0700 [thread overview]
Message-ID: <20040423140913.5a7491b9.davem@redhat.com> (raw)
In-Reply-To: <OFE28EC49F.335C9D5D-ON88256E7F.0073BC2E-88256E7F.0073F700@us.ibm.com>
On Fri, 23 Apr 2004 14:06:39 -0700
David Stevens <dlstevens@us.ibm.com> wrote:
> I believe "2" and "3" are the scale factors for the fixed-point
> representation
> of the data, not the "alpha" and "beta" I remember from the estimator
> paper.
That's correct.
next prev parent reply other threads:[~2004-04-23 21:09 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
2004-04-23 21:06 ` David Stevens
2004-04-23 21:09 ` David S. Miller [this message]
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=20040423140913.5a7491b9.davem@redhat.com \
--to=davem@redhat.com \
--cc=dlstevens@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=netdev@oss.sgi.com \
--cc=weddy@grc.nasa.gov \
/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).