89858ad143
This makes RTAX_RTO_MIN also available to CCID-3, replacing the compile-time RTO lower bound with a per-route tunable value. The original Kconfig option solved the problem that a very low RTT (in the order of HZ) can trigger too frequent and unnecessary reductions of the sending rate. This tunable does not affect the initial RTO value of 2 seconds specified in RFC 5348, section 4.2 and Appendix B. But like the hardcoded Kconfig value, it allows to adapt to network conditions. The same effect as the original Kconfig option of 100ms is now achieved by > ip route replace to unicast 192.168.0.0/24 rto_min 100j dev eth0 (assuming HZ=1000). Signed-off-by: Gerrit Renker <gerrit@erg.abdn.ac.uk> Signed-off-by: David S. Miller <davem@davemloft.net>
55 lines
1.7 KiB
Text
55 lines
1.7 KiB
Text
menu "DCCP CCIDs Configuration (EXPERIMENTAL)"
|
|
depends on EXPERIMENTAL
|
|
|
|
config IP_DCCP_CCID2_DEBUG
|
|
bool "CCID-2 debugging messages"
|
|
---help---
|
|
Enable CCID-2 specific debugging messages.
|
|
|
|
The debugging output can additionally be toggled by setting the
|
|
ccid2_debug parameter to 0 or 1.
|
|
|
|
If in doubt, say N.
|
|
|
|
config IP_DCCP_CCID3
|
|
bool "CCID-3 (TCP-Friendly) (EXPERIMENTAL)"
|
|
def_bool y if (IP_DCCP = y || IP_DCCP = m)
|
|
---help---
|
|
CCID-3 denotes TCP-Friendly Rate Control (TFRC), an equation-based
|
|
rate-controlled congestion control mechanism. TFRC is designed to
|
|
be reasonably fair when competing for bandwidth with TCP-like flows,
|
|
where a flow is "reasonably fair" if its sending rate is generally
|
|
within a factor of two of the sending rate of a TCP flow under the
|
|
same conditions. However, TFRC has a much lower variation of
|
|
throughput over time compared with TCP, which makes CCID-3 more
|
|
suitable than CCID-2 for applications such streaming media where a
|
|
relatively smooth sending rate is of importance.
|
|
|
|
CCID-3 is further described in RFC 4342,
|
|
http://www.ietf.org/rfc/rfc4342.txt
|
|
|
|
The TFRC congestion control algorithms were initially described in
|
|
RFC 5348.
|
|
|
|
This text was extracted from RFC 4340 (sec. 10.2),
|
|
http://www.ietf.org/rfc/rfc4340.txt
|
|
|
|
If in doubt, say N.
|
|
|
|
config IP_DCCP_CCID3_DEBUG
|
|
bool "CCID-3 debugging messages"
|
|
depends on IP_DCCP_CCID3
|
|
---help---
|
|
Enable CCID-3 specific debugging messages.
|
|
|
|
The debugging output can additionally be toggled by setting the
|
|
ccid3_debug parameter to 0 or 1.
|
|
|
|
If in doubt, say N.
|
|
|
|
config IP_DCCP_TFRC_LIB
|
|
def_bool y if IP_DCCP_CCID3
|
|
|
|
config IP_DCCP_TFRC_DEBUG
|
|
def_bool y if IP_DCCP_CCID3_DEBUG
|
|
endmenu
|