Commit:     89808060b7a71376cc2ba8092d43b2010da465b6
Parent:     3cfe3baaf07c9e40a75f9a70662de56df1c246a8
Author:     Ilpo Järvinen <[EMAIL PROTECTED]>
AuthorDate: Tue Feb 27 10:10:55 2007 -0800
Committer:  David S. Miller <[EMAIL PROTECTED]>
CommitDate: Wed Apr 25 22:23:24 2007 -0700

    [TCP] Sysctl documentation: tcp_frto_response
    In addition, fixed minor things in tcp_frto sysctl.
    Signed-off-by: Ilpo Järvinen <[EMAIL PROTECTED]>
    Signed-off-by: David S. Miller <[EMAIL PROTECTED]>
 Documentation/networking/ip-sysctl.txt |   21 +++++++++++++++++++--
 1 files changed, 19 insertions(+), 2 deletions(-)

diff --git a/Documentation/networking/ip-sysctl.txt 
index 719b429..054c515 100644
--- a/Documentation/networking/ip-sysctl.txt
+++ b/Documentation/networking/ip-sysctl.txt
@@ -179,15 +179,32 @@ tcp_fin_timeout - INTEGER
        because they eat maximum 1.5K of memory, but they tend
        to live longer. Cf. tcp_max_orphans.
-tcp_frto - BOOLEAN
+tcp_frto - INTEGER
        Enables F-RTO, an enhanced recovery algorithm for TCP retransmission
        timeouts.  It is particularly beneficial in wireless environments
        where packet loss is typically due to random radio interference
        rather than intermediate router congestion. If set to 1, basic
-       version is enabled. 2 enables SACK enhanced FRTO, which is
+       version is enabled. 2 enables SACK enhanced F-RTO, which is
        EXPERIMENTAL. The basic version can be used also when SACK is
        enabled for a flow through tcp_sack sysctl.
+tcp_frto_response - INTEGER
+       When F-RTO has detected that a TCP retransmission timeout was
+       spurious (i.e, the timeout would have been avoided had TCP set a
+       longer retransmission timeout), TCP has several options what to do
+       next. Possible values are:
+               0 Rate halving based; a smooth and conservative response,
+                 results in halved cwnd and ssthresh after one RTT
+               1 Very conservative response; not recommended because even
+                 though being valid, it interacts poorly with the rest of
+                 Linux TCP, halves cwnd and ssthresh immediately
+               2 Aggressive response; undoes congestion control measures
+                 that are now known to be unnecessary (ignoring the
+                 possibility of a lost retransmission that would require
+                 TCP to be more cautious), cwnd and ssthresh are restored
+                 to the values prior timeout
+       Default: 0 (rate halving based)
 tcp_keepalive_time - INTEGER
        How often TCP sends out keepalive messages when keepalive is enabled.
        Default: 2hours.
To unsubscribe from this list: send the line "unsubscribe git-commits-head" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at

Reply via email to