From: Rick Jones <rick.jones2@hp.com>
To: Baruch Even <baruch@ev-en.org>
Cc: "Ilpo Järvinen" <ilpo.jarvinen@helsinki.fi>,
"David Miller" <davem@davemloft.net>,
Netdev <netdev@vger.kernel.org>
Subject: Re: [PATCH] [TCP] Sysctl: document tcp_max_ssthresh (Limited Slow-Start)
Date: Fri, 18 May 2007 12:39:17 -0700 [thread overview]
Message-ID: <464E00E5.5050801@hp.com> (raw)
In-Reply-To: <464DE584.7030008@ev-en.org>
Baruch Even wrote:
> Ilpo Järvinen wrote:
>
>>Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
>>---
>> Documentation/networking/ip-sysctl.txt | 13 +++++++++++++
>> 1 files changed, 13 insertions(+), 0 deletions(-)
>>
>>diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt
>>index ce16e6a..44ba8d4 100644
>>--- a/Documentation/networking/ip-sysctl.txt
>>+++ b/Documentation/networking/ip-sysctl.txt
>>@@ -239,6 +239,19 @@ tcp_max_orphans - INTEGER
>> more aggressively. Let me to remind again: each orphan eats
>> up to ~64K of unswappable memory.
>>
>>+tcp_max_ssthresh - INTEGER
>>+ Limited Slow-Start for TCP with Large Congestion Windows defined in
>>+ RFC3742. Limited slow-start is a mechanism to limit grow of the
>
>
> s/grow/growth/
>
>
>>+ congestion window on the region where congestion window is larger than
>>+ tcp_max_ssthresh. A TCP connection with a large congestion window could
>>+ have its congestion window increased by thousand (or even more)
>>+ segments per RTT by the traditional slow-start procedure which might be
>>+ counter-productive to TCP performance when packet losses start to
>>+ occur. With limited slow-start TCP increments congestion window at
>>+ most tcp_max_ssthresh/2 segments per RTT when the congestion window is
>
>
> I'm not a native English speaker but "at most" sounds a bit awkward to
> me, maybe change it to "by no more than". But I'm sure someone can find
> a better phrasing.
It could be "by at most" or "by no more than" but indeed it should not just be
"at most."
Also, it should be "With limited slow-start TCP increments the congestion
window..." Combining with other nits yeilds:
Limited Slow-Start for TCP with Large Congestion Windows is defined in RFC3742.
Limited slow-start is a mechanism to limit growth of the congestion window
when the congestion window is larger than tcp_max_ssthresh. A TCP connection
with a large congestion window could have its congestion window increased by
thousands of segments (or more) per RTT via the traditional slow-start
procedures. This might degrade TCP performance when packet losses start to
occur. With limited slow-start, TCP increments the congestion window by at most
tcp_max_ssthresh/2 segments per RTT when the congestion window is is above
tcp_max_ssthresh.
rick jones
as an asside, "tcp_max_ssthresh" sounds like the maximum value ssthresh can
take-on. is that correct, or is this more of a "once ssthresh is above this,
behave in this new way?" If that is the case, while the horse has probably left
the barn, perhaps another name would be better?
>
> Baruch
> -
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2007-05-18 19:40 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 16:27 [PATCH] [TCP] Sysctl: document tcp_max_ssthresh (Limited Slow-Start) Ilpo Järvinen
2007-05-18 17:42 ` Baruch Even
2007-05-18 19:39 ` Rick Jones [this message]
2007-05-18 20:49 ` John Heffner
2007-05-19 7:24 ` Ilpo Järvinen
2007-05-19 7:32 ` Ilpo Järvinen
2007-05-19 7:01 ` Ilpo Järvinen
2007-05-19 7:26 ` Ilpo Järvinen
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=464E00E5.5050801@hp.com \
--to=rick.jones2@hp.com \
--cc=baruch@ev-en.org \
--cc=davem@davemloft.net \
--cc=ilpo.jarvinen@helsinki.fi \
--cc=netdev@vger.kernel.org \
/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).