1 # SPDX-License-Identifier: GPL-2.0-only 1 # SPDX-License-Identifier: GPL-2.0-only
2 menu "DCCP CCIDs Configuration" 2 menu "DCCP CCIDs Configuration"
3 3
4 config IP_DCCP_CCID2_DEBUG 4 config IP_DCCP_CCID2_DEBUG
5 bool "CCID-2 debugging messages" 5 bool "CCID-2 debugging messages"
6 help 6 help
7 Enable CCID-2 specific debugging mes 7 Enable CCID-2 specific debugging messages.
8 8
9 The debugging output can additionall 9 The debugging output can additionally be toggled by setting the
10 ccid2_debug parameter to 0 or 1. 10 ccid2_debug parameter to 0 or 1.
11 11
12 If in doubt, say N. 12 If in doubt, say N.
13 13
14 config IP_DCCP_CCID3 14 config IP_DCCP_CCID3
15 bool "CCID-3 (TCP-Friendly)" 15 bool "CCID-3 (TCP-Friendly)"
16 default IP_DCCP = y || IP_DCCP = m !! 16 def_bool y if (IP_DCCP = y || IP_DCCP = m)
17 help 17 help
18 CCID-3 denotes TCP-Friendly Rate Con 18 CCID-3 denotes TCP-Friendly Rate Control (TFRC), an equation-based
19 rate-controlled congestion control m 19 rate-controlled congestion control mechanism. TFRC is designed to
20 be reasonably fair when competing fo 20 be reasonably fair when competing for bandwidth with TCP-like flows,
21 where a flow is "reasonably fair" if 21 where a flow is "reasonably fair" if its sending rate is generally
22 within a factor of two of the sendin 22 within a factor of two of the sending rate of a TCP flow under the
23 same conditions. However, TFRC has 23 same conditions. However, TFRC has a much lower variation of
24 throughput over time compared with T 24 throughput over time compared with TCP, which makes CCID-3 more
25 suitable than CCID-2 for application 25 suitable than CCID-2 for applications such streaming media where a
26 relatively smooth sending rate is of 26 relatively smooth sending rate is of importance.
27 27
28 CCID-3 is further described in RFC 4 28 CCID-3 is further described in RFC 4342,
29 https://www.ietf.org/rfc/rfc4342.txt !! 29 http://www.ietf.org/rfc/rfc4342.txt
30 30
31 The TFRC congestion control algorith 31 The TFRC congestion control algorithms were initially described in
32 RFC 5348. 32 RFC 5348.
33 33
34 This text was extracted from RFC 434 34 This text was extracted from RFC 4340 (sec. 10.2),
35 https://www.ietf.org/rfc/rfc4340.txt !! 35 http://www.ietf.org/rfc/rfc4340.txt
36 36
37 If in doubt, say N. 37 If in doubt, say N.
38 38
39 config IP_DCCP_CCID3_DEBUG 39 config IP_DCCP_CCID3_DEBUG
40 bool "CCID-3 debugging messages" 40 bool "CCID-3 debugging messages"
41 depends on IP_DCCP_CCID3 41 depends on IP_DCCP_CCID3
42 help 42 help
43 Enable CCID-3 specific debugging mes 43 Enable CCID-3 specific debugging messages.
44 44
45 The debugging output can additionall 45 The debugging output can additionally be toggled by setting the
46 ccid3_debug parameter to 0 or 1. 46 ccid3_debug parameter to 0 or 1.
47 47
48 If in doubt, say N. 48 If in doubt, say N.
49 49
50 config IP_DCCP_TFRC_LIB 50 config IP_DCCP_TFRC_LIB
51 def_bool y if IP_DCCP_CCID3 51 def_bool y if IP_DCCP_CCID3
52 52
53 config IP_DCCP_TFRC_DEBUG 53 config IP_DCCP_TFRC_DEBUG
54 def_bool y if IP_DCCP_CCID3_DEBUG 54 def_bool y if IP_DCCP_CCID3_DEBUG
55 endmenu 55 endmenu
Linux® is a registered trademark of Linus Torvalds in the United States and other countries.
TOMOYO® is a registered trademark of NTT DATA CORPORATION.