2019-05-19 06:07:45 -06:00
|
|
|
# SPDX-License-Identifier: GPL-2.0-only
|
2012-10-02 12:19:43 -06:00
|
|
|
menu "DCCP CCIDs Configuration"
|
2005-08-09 21:14:34 -06:00
|
|
|
|
2006-09-19 14:12:44 -06:00
|
|
|
config IP_DCCP_CCID2_DEBUG
|
2009-01-04 22:42:53 -07:00
|
|
|
bool "CCID-2 debugging messages"
|
2020-06-13 10:50:22 -06:00
|
|
|
help
|
2009-01-04 22:42:53 -07:00
|
|
|
Enable CCID-2 specific debugging messages.
|
2006-11-20 13:26:03 -07:00
|
|
|
|
2009-01-04 22:42:53 -07:00
|
|
|
The debugging output can additionally be toggled by setting the
|
|
|
|
ccid2_debug parameter to 0 or 1.
|
2006-09-19 14:12:44 -06:00
|
|
|
|
2009-01-04 22:42:53 -07:00
|
|
|
If in doubt, say N.
|
2006-09-19 14:12:44 -06:00
|
|
|
|
2005-08-09 21:14:34 -06:00
|
|
|
config IP_DCCP_CCID3
|
2012-10-02 12:19:43 -06:00
|
|
|
bool "CCID-3 (TCP-Friendly)"
|
2009-01-04 22:42:53 -07:00
|
|
|
def_bool y if (IP_DCCP = y || IP_DCCP = m)
|
2020-06-13 10:50:22 -06:00
|
|
|
help
|
2009-01-04 22:42:53 -07:00
|
|
|
CCID-3 denotes TCP-Friendly Rate Control (TFRC), an equation-based
|
2005-08-09 21:14:34 -06:00
|
|
|
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
|
2009-01-04 22:42:53 -07:00
|
|
|
throughput over time compared with TCP, which makes CCID-3 more
|
|
|
|
suitable than CCID-2 for applications such streaming media where a
|
2005-08-09 21:14:34 -06:00
|
|
|
relatively smooth sending rate is of importance.
|
|
|
|
|
2009-01-04 22:42:53 -07:00
|
|
|
CCID-3 is further described in RFC 4342,
|
2020-07-13 01:51:08 -06:00
|
|
|
https://www.ietf.org/rfc/rfc4342.txt
|
2006-03-20 18:41:47 -07:00
|
|
|
|
|
|
|
The TFRC congestion control algorithms were initially described in
|
2009-01-11 01:17:22 -07:00
|
|
|
RFC 5348.
|
2005-08-09 21:14:34 -06:00
|
|
|
|
2006-10-24 17:17:51 -06:00
|
|
|
This text was extracted from RFC 4340 (sec. 10.2),
|
2020-07-13 01:51:08 -06:00
|
|
|
https://www.ietf.org/rfc/rfc4340.txt
|
2006-11-20 13:26:03 -07:00
|
|
|
|
2009-01-04 22:42:53 -07:00
|
|
|
If in doubt, say N.
|
2005-08-09 21:14:34 -06:00
|
|
|
|
2006-11-20 13:28:09 -07:00
|
|
|
config IP_DCCP_CCID3_DEBUG
|
2009-01-04 22:42:53 -07:00
|
|
|
bool "CCID-3 debugging messages"
|
|
|
|
depends on IP_DCCP_CCID3
|
2020-06-13 10:50:22 -06:00
|
|
|
help
|
2009-01-04 22:42:53 -07:00
|
|
|
Enable CCID-3 specific debugging messages.
|
2006-11-20 13:28:09 -07:00
|
|
|
|
2009-01-04 22:42:53 -07:00
|
|
|
The debugging output can additionally be toggled by setting the
|
|
|
|
ccid3_debug parameter to 0 or 1.
|
2006-11-20 13:28:09 -07:00
|
|
|
|
2009-01-04 22:42:53 -07:00
|
|
|
If in doubt, say N.
|
2006-12-03 09:50:23 -07:00
|
|
|
|
2007-12-06 07:26:38 -07:00
|
|
|
config IP_DCCP_TFRC_LIB
|
2009-01-04 22:45:33 -07:00
|
|
|
def_bool y if IP_DCCP_CCID3
|
2007-12-06 07:26:38 -07:00
|
|
|
|
|
|
|
config IP_DCCP_TFRC_DEBUG
|
2009-01-04 22:45:33 -07:00
|
|
|
def_bool y if IP_DCCP_CCID3_DEBUG
|
2005-08-09 21:14:34 -06:00
|
|
|
endmenu
|