aboutsummaryrefslogtreecommitdiffstats
path: root/net/dccp/ccids/Kconfig
diff options
context:
space:
mode:
Diffstat (limited to 'net/dccp/ccids/Kconfig')
-rw-r--r--net/dccp/ccids/Kconfig70
1 files changed, 21 insertions, 49 deletions
diff --git a/net/dccp/ccids/Kconfig b/net/dccp/ccids/Kconfig
index 12275943eab8..b30f049cf1d3 100644
--- a/net/dccp/ccids/Kconfig
+++ b/net/dccp/ccids/Kconfig
@@ -1,80 +1,52 @@
1menu "DCCP CCIDs Configuration (EXPERIMENTAL)" 1menu "DCCP CCIDs Configuration (EXPERIMENTAL)"
2 depends on EXPERIMENTAL 2 depends on EXPERIMENTAL
3 3
4config IP_DCCP_CCID2
5 tristate "CCID2 (TCP-Like) (EXPERIMENTAL)"
6 def_tristate IP_DCCP
7 select IP_DCCP_ACKVEC
8 ---help---
9 CCID 2, TCP-like Congestion Control, denotes Additive Increase,
10 Multiplicative Decrease (AIMD) congestion control with behavior
11 modelled directly on TCP, including congestion window, slow start,
12 timeouts, and so forth [RFC 2581]. CCID 2 achieves maximum
13 bandwidth over the long term, consistent with the use of end-to-end
14 congestion control, but halves its congestion window in response to
15 each congestion event. This leads to the abrupt rate changes
16 typical of TCP. Applications should use CCID 2 if they prefer
17 maximum bandwidth utilization to steadiness of rate. This is often
18 the case for applications that are not playing their data directly
19 to the user. For example, a hypothetical application that
20 transferred files over DCCP, using application-level retransmissions
21 for lost packets, would prefer CCID 2 to CCID 3. On-line games may
22 also prefer CCID 2. See RFC 4341 for further details.
23
24 CCID2 is the default CCID used by DCCP.
25
26config IP_DCCP_CCID2_DEBUG 4config IP_DCCP_CCID2_DEBUG
27 bool "CCID2 debugging messages" 5 bool "CCID-2 debugging messages"
28 depends on IP_DCCP_CCID2 6 ---help---
29 ---help--- 7 Enable CCID-2 specific debugging messages.
30 Enable CCID2-specific debugging messages.
31 8
32 When compiling CCID2 as a module, this debugging output can 9 The debugging output can additionally be toggled by setting the
33 additionally be toggled by setting the ccid2_debug module 10 ccid2_debug parameter to 0 or 1.
34 parameter to 0 or 1.
35 11
36 If in doubt, say N. 12 If in doubt, say N.
37 13
38config IP_DCCP_CCID3 14config IP_DCCP_CCID3
39 tristate "CCID3 (TCP-Friendly) (EXPERIMENTAL)" 15 bool "CCID-3 (TCP-Friendly) (EXPERIMENTAL)"
40 def_tristate IP_DCCP 16 def_bool y if (IP_DCCP = y || IP_DCCP = m)
41 select IP_DCCP_TFRC_LIB 17 select IP_DCCP_TFRC_LIB
42 ---help--- 18 ---help---
43 CCID 3 denotes TCP-Friendly Rate Control (TFRC), an equation-based 19 CCID-3 denotes TCP-Friendly Rate Control (TFRC), an equation-based
44 rate-controlled congestion control mechanism. TFRC is designed to 20 rate-controlled congestion control mechanism. TFRC is designed to
45 be reasonably fair when competing for bandwidth with TCP-like flows, 21 be reasonably fair when competing for bandwidth with TCP-like flows,
46 where a flow is "reasonably fair" if its sending rate is generally 22 where a flow is "reasonably fair" if its sending rate is generally
47 within a factor of two of the sending rate of a TCP flow under the 23 within a factor of two of the sending rate of a TCP flow under the
48 same conditions. However, TFRC has a much lower variation of 24 same conditions. However, TFRC has a much lower variation of
49 throughput over time compared with TCP, which makes CCID 3 more 25 throughput over time compared with TCP, which makes CCID-3 more
50 suitable than CCID 2 for applications such streaming media where a 26 suitable than CCID-2 for applications such streaming media where a
51 relatively smooth sending rate is of importance. 27 relatively smooth sending rate is of importance.
52 28
53 CCID 3 is further described in RFC 4342, 29 CCID-3 is further described in RFC 4342,
54 http://www.ietf.org/rfc/rfc4342.txt 30 http://www.ietf.org/rfc/rfc4342.txt
55 31
56 The TFRC congestion control algorithms were initially described in 32 The TFRC congestion control algorithms were initially described in
57 RFC 3448. 33 RFC 5448.
58 34
59 This text was extracted from RFC 4340 (sec. 10.2), 35 This text was extracted from RFC 4340 (sec. 10.2),
60 http://www.ietf.org/rfc/rfc4340.txt 36 http://www.ietf.org/rfc/rfc4340.txt
61
62 To compile this CCID as a module, choose M here: the module will be
63 called dccp_ccid3.
64 37
65 If in doubt, say M. 38 If in doubt, say N.
66 39
67config IP_DCCP_CCID3_DEBUG 40config IP_DCCP_CCID3_DEBUG
68 bool "CCID3 debugging messages" 41 bool "CCID-3 debugging messages"
69 depends on IP_DCCP_CCID3 42 depends on IP_DCCP_CCID3
70 ---help--- 43 ---help---
71 Enable CCID3-specific debugging messages. 44 Enable CCID-3 specific debugging messages.
72 45
73 When compiling CCID3 as a module, this debugging output can 46 The debugging output can additionally be toggled by setting the
74 additionally be toggled by setting the ccid3_debug module 47 ccid3_debug parameter to 0 or 1.
75 parameter to 0 or 1.
76 48
77 If in doubt, say N. 49 If in doubt, say N.
78 50
79config IP_DCCP_CCID3_RTO 51config IP_DCCP_CCID3_RTO
80 int "Use higher bound for nofeedback timer" 52 int "Use higher bound for nofeedback timer"