From: Rick Jones <rick.jones2@hp.com>
To: "David S. Miller" <davem@davemloft.net>
Cc: jheffner@psc.edu, zach.brown@oracle.com, netdev@vger.kernel.org
Subject: Re: tune back idle cwnd closing?
Date: Thu, 27 Apr 2006 14:12:32 -0700 [thread overview]
Message-ID: <445133C0.9080808@hp.com> (raw)
In-Reply-To: <20060427.131921.79333703.davem@davemloft.net>
having looked now at both 2861 and the 99 paper it references I see lots
of "may's" "mights" and "belief" but nothing "real world."
the CWV vs non CWV was done against a TCP that did indeed reset cwnd
after an RTT of idle, so it wasn't showing reset at idle versus no reset
at idle. just CWV's less draconian (?) reset than the non CWV stack.
the experimental validation in the 99 paper was still a simulation using
dummynet and a number of buffers rather smaller than what modem banks
were offering at the time, and it was for a modem, rather than any other
sort of link. and when they did use a real modem, the buffering in the
modem bank seems to have made the whole thing moot.
there was nothing about effect on intranets, or high-speed long hauls or
any of that.
what that means wrt having a sysctl to enable/disable functionality
still listed as experimental i'm not sure
rick jones
prev parent reply other threads:[~2006-04-27 21:12 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-21 19:58 tune back idle cwnd closing? Zach Brown
2006-04-25 14:27 ` John Heffner
2006-04-26 21:45 ` David S. Miller
2006-04-26 22:16 ` Rick Jones
2006-04-26 22:27 ` Stephen Hemminger
2006-04-26 22:44 ` Rick Jones
2006-04-26 22:33 ` David S. Miller
2006-04-26 23:25 ` Zach Brown
2006-04-27 17:47 ` John Heffner
2006-04-27 20:19 ` David S. Miller
2006-04-27 21:12 ` Rick Jones [this message]
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=445133C0.9080808@hp.com \
--to=rick.jones2@hp.com \
--cc=davem@davemloft.net \
--cc=jheffner@psc.edu \
--cc=netdev@vger.kernel.org \
--cc=zach.brown@oracle.com \
/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).