From: Werner Almesberger <wa@almesberger.net>
To: kuznet@ms2.inr.ac.ru
Cc: netdev@oss.sgi.com, chengjin@cs.caltech.edu
Subject: Re: snd_cwnd drawn and quartered
Date: Thu, 2 Jan 2003 03:08:58 -0300 [thread overview]
Message-ID: <20030102030858.E1363@almesberger.net> (raw)
In-Reply-To: <200301020138.EAA32608@sex.inr.ac.ru>; from kuznet@ms2.inr.ac.ru on Thu, Jan 02, 2003 at 04:38:46AM +0300
kuznet@ms2.inr.ac.ru wrote:
> It does the thing which it is supposed to do: prevents reducing cwnd below
> 1/4 of original one.
Okay, this it does. I guess the only case where this would make a
difference is if your network duplicates packets.
> This was proposed in one of rete-halving related drafts
> with title sort of "...boundary checks...", I forgot exact title, can find
> it if you are curious.
I searched around but didn't spot anything. A pointer would be
welcome, thanks !
> Maybe this is even correct, but I do not see why it can be essential.
> cwnd falls too low not due to decrementing due to rate-halving,
> but due to draining out in_flight when we are not able to keep pipe full.
Yes, but rate-halving is what causes in-flight to drop in the first
place (assuming we have enough fresh data to send, of course), no ?
> Please, show.
I've put graphs of a simulation run (with and without the change) at
http://www.almesberger.net/misc/half.eps
http://www.almesberger.net/misc/quarter.eps
Y-axis is in segments, x-axis is in some arbitrary time unit, RTT is
one initial cwnd (100 packets), path is asymmetric with zero-delay
and loss-less backward channel. (While unusual, this shouldn't
actually affect what TCP does in recovery.) Losses happen right
before the packet hits the receiver.
I've also asked Cheng if he can send you a copy of his simulator.
Thanks,
- Werner
--
_________________________________________________________________________
/ Werner Almesberger, Buenos Aires, Argentina wa@almesberger.net /
/_http://www.almesberger.net/____________________________________________/
next prev parent reply other threads:[~2003-01-02 6:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-25 1:50 snd_cwnd drawn and quartered Werner Almesberger
2003-01-02 1:38 ` kuznet
2003-01-02 6:08 ` Werner Almesberger [this message]
2003-01-02 8:31 ` Werner Almesberger
2003-01-02 21:26 ` Werner Almesberger
2003-01-14 0:12 ` kuznet
2003-01-14 1:20 ` Cheng Jin
2003-01-14 1:46 ` kuznet
2003-01-14 1:58 ` Cheng Jin
2003-01-14 2:12 ` kuznet
2003-01-14 2:19 ` Cheng Jin
2003-01-14 5:07 ` kuznet
2003-01-14 4:01 ` Werner Almesberger
[not found] ` <200301140502.IAA10733@sex.inr.ac.ru>
2003-01-14 5:25 ` Werner Almesberger
2003-01-14 6:14 ` kuznet
2003-01-14 6:36 ` Werner Almesberger
2003-01-15 17:50 ` kuznet
2003-01-15 18:25 ` Werner Almesberger
2003-01-15 18:43 ` kuznet
2003-01-15 19:37 ` Werner Almesberger
2003-01-19 6:55 ` example showing how cwnd gets to one Cheng Jin
2003-01-14 0:54 ` snd_cwnd drawn and quartered kuznet
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=20030102030858.E1363@almesberger.net \
--to=wa@almesberger.net \
--cc=chengjin@cs.caltech.edu \
--cc=kuznet@ms2.inr.ac.ru \
--cc=netdev@oss.sgi.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).