On Fri, 18 May 2007, Baruch Even wrote:
> 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.
Neither am I, but since nothing else seems to have came up, here is one
with your proposal... In addition to your changes, I fixed the
capitalization of the first sentence (which was a result of copy-paste
from RFC's title).
[PATCH] [TCP] Sysctl: Document tcp_max_ssthresh (Limited Slow-Start)
Signed-off-by: Ilpo Järvinen <[EMAIL PROTECTED]>
---
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..b4d0a66 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 growth of the
+ 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 by no
+ more than tcp_max_ssthresh/2 segments per RTT when the congestion
+ window is above tcp_max_ssthresh.
+ Default: 0 (off)
+
tcp_max_syn_backlog - INTEGER
Maximal number of remembered connection requests, which are
still did not receive an acknowledgment from connecting client.
--
1.5.0.6
