All of lore.kernel.org
 help / color / mirror / Atom feed
* [PATCH 2/2] [TCP] Sysctl documentation: tcp_frto_response
@ 2007-02-27 15:50 Ilpo Järvinen
  2007-02-27 18:11 ` David Miller
  0 siblings, 1 reply; 2+ messages in thread
From: Ilpo Järvinen @ 2007-02-27 15:50 UTC (permalink / raw)
  To: David Miller; +Cc: netdev

[-- Attachment #1: Type: TEXT/PLAIN, Size: 2129 bytes --]

In addition, fixed minor things in tcp_frto sysctl.

Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>
---
 Documentation/networking/ip-sysctl.txt |   21 +++++++++++++++++++--
 1 files changed, 19 insertions(+), 2 deletions(-)

diff --git a/Documentation/networking/ip-sysctl.txt b/Documentation/networking/ip-sysctl.txt
index d66777b..95e2a9f 100644
--- a/Documentation/networking/ip-sysctl.txt
+++ b/Documentation/networking/ip-sysctl.txt
@@ -174,15 +174,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.
-- 
1.4.2

^ permalink raw reply related	[flat|nested] 2+ messages in thread

* Re: [PATCH 2/2] [TCP] Sysctl documentation: tcp_frto_response
  2007-02-27 15:50 [PATCH 2/2] [TCP] Sysctl documentation: tcp_frto_response Ilpo Järvinen
@ 2007-02-27 18:11 ` David Miller
  0 siblings, 0 replies; 2+ messages in thread
From: David Miller @ 2007-02-27 18:11 UTC (permalink / raw)
  To: ilpo.jarvinen; +Cc: netdev

From: "Ilpo_Järvinen" <ilpo.jarvinen@helsinki.fi>
Date: Tue, 27 Feb 2007 17:50:39 +0200 (EET)

> In addition, fixed minor things in tcp_frto sysctl.
> 
> Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@helsinki.fi>

Applied to tcp-2.6, thank you.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2007-02-27 18:11 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2007-02-27 15:50 [PATCH 2/2] [TCP] Sysctl documentation: tcp_frto_response Ilpo Järvinen
2007-02-27 18:11 ` David Miller

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.