Commit 4edc2f34 authored by Stephen Hemminger's avatar Stephen Hemminger Committed by David S. Miller

ip: sysctl documentation cleanup

Reduced version of the spelling cleanup patch.

Take out the confusing language in tcp_frto, and organize the
undocumented values.
Signed-off-by: default avatarStephen Hemminger <shemminger@vyatta.com>
Acked-by: default avatarRandy Dunlap <rdunlap@xenotime.net>
Signed-off-by: default avatarDavid S. Miller <davem@davemloft.net>
parent 53025f5e
...@@ -148,9 +148,9 @@ tcp_available_congestion_control - STRING ...@@ -148,9 +148,9 @@ tcp_available_congestion_control - STRING
but not loaded. but not loaded.
tcp_base_mss - INTEGER tcp_base_mss - INTEGER
The initial value of search_low to be used by Packetization Layer The initial value of search_low to be used by the packetization layer
Path MTU Discovery (MTU probing). If MTU probing is enabled, Path MTU discovery (MTU probing). If MTU probing is enabled,
this is the inital MSS used by the connection. this is the initial MSS used by the connection.
tcp_congestion_control - STRING tcp_congestion_control - STRING
Set the congestion control algorithm to be used for new Set the congestion control algorithm to be used for new
...@@ -186,9 +186,8 @@ tcp_frto - INTEGER ...@@ -186,9 +186,8 @@ tcp_frto - INTEGER
where packet loss is typically due to random radio interference where packet loss is typically due to random radio interference
rather than intermediate router congestion. F-RTO is sender-side rather than intermediate router congestion. F-RTO is sender-side
only modification. Therefore it does not require any support from only modification. Therefore it does not require any support from
the peer, but in a typical case, however, where wireless link is the peer.
the local access link and most of the data flows downlink, the
faraway servers should have F-RTO enabled to take advantage of it.
If set to 1, basic version is enabled. 2 enables SACK enhanced If set to 1, basic version is enabled. 2 enables SACK enhanced
F-RTO if flow uses SACK. The basic version can be used also when F-RTO if flow uses SACK. The basic version can be used also when
SACK is in use though scenario(s) with it exists where F-RTO SACK is in use though scenario(s) with it exists where F-RTO
...@@ -276,7 +275,7 @@ tcp_mem - vector of 3 INTEGERs: min, pressure, max ...@@ -276,7 +275,7 @@ tcp_mem - vector of 3 INTEGERs: min, pressure, max
memory. memory.
tcp_moderate_rcvbuf - BOOLEAN tcp_moderate_rcvbuf - BOOLEAN
If set, TCP performs receive buffer autotuning, attempting to If set, TCP performs receive buffer auto-tuning, attempting to
automatically size the buffer (no greater than tcp_rmem[2]) to automatically size the buffer (no greater than tcp_rmem[2]) to
match the size required by the path for full throughput. Enabled by match the size required by the path for full throughput. Enabled by
default. default.
...@@ -360,7 +359,7 @@ tcp_slow_start_after_idle - BOOLEAN ...@@ -360,7 +359,7 @@ tcp_slow_start_after_idle - BOOLEAN
Default: 1 Default: 1
tcp_stdurg - BOOLEAN tcp_stdurg - BOOLEAN
Use the Host requirements interpretation of the TCP urg pointer field. Use the Host requirements interpretation of the TCP urgent pointer field.
Most hosts use the older BSD interpretation, so if you turn this on Most hosts use the older BSD interpretation, so if you turn this on
Linux might not communicate correctly with them. Linux might not communicate correctly with them.
Default: FALSE Default: FALSE
...@@ -373,12 +372,12 @@ tcp_synack_retries - INTEGER ...@@ -373,12 +372,12 @@ tcp_synack_retries - INTEGER
tcp_syncookies - BOOLEAN tcp_syncookies - BOOLEAN
Only valid when the kernel was compiled with CONFIG_SYNCOOKIES Only valid when the kernel was compiled with CONFIG_SYNCOOKIES
Send out syncookies when the syn backlog queue of a socket Send out syncookies when the syn backlog queue of a socket
overflows. This is to prevent against the common 'syn flood attack' overflows. This is to prevent against the common 'SYN flood attack'
Default: FALSE Default: FALSE
Note, that syncookies is fallback facility. Note, that syncookies is fallback facility.
It MUST NOT be used to help highly loaded servers to stand It MUST NOT be used to help highly loaded servers to stand
against legal connection rate. If you see synflood warnings against legal connection rate. If you see SYN flood warnings
in your logs, but investigation shows that they occur in your logs, but investigation shows that they occur
because of overload with legal connections, you should tune because of overload with legal connections, you should tune
another parameters until this warning disappear. another parameters until this warning disappear.
...@@ -388,7 +387,7 @@ tcp_syncookies - BOOLEAN ...@@ -388,7 +387,7 @@ tcp_syncookies - BOOLEAN
to use TCP extensions, can result in serious degradation to use TCP extensions, can result in serious degradation
of some services (f.e. SMTP relaying), visible not by you, of some services (f.e. SMTP relaying), visible not by you,
but your clients and relays, contacting you. While you see but your clients and relays, contacting you. While you see
synflood warnings in logs not being really flooded, your server SYN flood warnings in logs not being really flooded, your server
is seriously misconfigured. is seriously misconfigured.
tcp_syn_retries - INTEGER tcp_syn_retries - INTEGER
...@@ -1236,22 +1235,21 @@ sctp_wmem - vector of 3 INTEGERs: min, default, max ...@@ -1236,22 +1235,21 @@ sctp_wmem - vector of 3 INTEGERs: min, default, max
UNDOCUMENTED: UNDOCUMENTED:
dev_weight FIXME /proc/sys/net/core/*
discovery_slots FIXME dev_weight FIXME
discovery_timeout FIXME
fast_poll_increase FIXME /proc/sys/net/unix/*
ip6_queue_maxlen FIXME max_dgram_qlen FIXME
lap_keepalive_time FIXME
lo_cong FIXME /proc/sys/net/irda/*
max_baud_rate FIXME fast_poll_increase FIXME
max_dgram_qlen FIXME warn_noreply_time FIXME
max_noreply_time FIXME discovery_slots FIXME
max_tx_data_size FIXME slot_timeout FIXME
max_tx_window FIXME max_baud_rate FIXME
min_tx_turn_time FIXME discovery_timeout FIXME
mod_cong FIXME lap_keepalive_time FIXME
no_cong FIXME max_noreply_time FIXME
no_cong_thresh FIXME max_tx_data_size FIXME
slot_timeout FIXME max_tx_window FIXME
warn_noreply_time FIXME min_tx_turn_time FIXME
Markdown is supported
0%
or
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment