diff options
Diffstat (limited to 'net/dccp/ccids/Kconfig')
-rw-r--r-- | net/dccp/ccids/Kconfig | 43 |
1 files changed, 39 insertions, 4 deletions
diff --git a/net/dccp/ccids/Kconfig b/net/dccp/ccids/Kconfig index 7684d83946a4..ca00191628f7 100644 --- a/net/dccp/ccids/Kconfig +++ b/net/dccp/ccids/Kconfig | |||
@@ -1,9 +1,39 @@ | |||
1 | menu "DCCP CCIDs Configuration (EXPERIMENTAL)" | 1 | menu "DCCP CCIDs Configuration (EXPERIMENTAL)" |
2 | depends on IP_DCCP && EXPERIMENTAL | 2 | depends on IP_DCCP && EXPERIMENTAL |
3 | 3 | ||
4 | config IP_DCCP_CCID2 | ||
5 | tristate "CCID2 (TCP-Like) (EXPERIMENTAL)" | ||
6 | depends on IP_DCCP | ||
7 | def_tristate IP_DCCP | ||
8 | select IP_DCCP_ACKVEC | ||
9 | ---help--- | ||
10 | CCID 2, TCP-like Congestion Control, denotes Additive Increase, | ||
11 | Multiplicative Decrease (AIMD) congestion control with behavior | ||
12 | modelled directly on TCP, including congestion window, slow start, | ||
13 | timeouts, and so forth [RFC 2581]. CCID 2 achieves maximum | ||
14 | bandwidth over the long term, consistent with the use of end-to-end | ||
15 | congestion control, but halves its congestion window in response to | ||
16 | each congestion event. This leads to the abrupt rate changes | ||
17 | typical of TCP. Applications should use CCID 2 if they prefer | ||
18 | maximum bandwidth utilization to steadiness of rate. This is often | ||
19 | the case for applications that are not playing their data directly | ||
20 | to the user. For example, a hypothetical application that | ||
21 | transferred files over DCCP, using application-level retransmissions | ||
22 | for lost packets, would prefer CCID 2 to CCID 3. On-line games may | ||
23 | also prefer CCID 2. | ||
24 | |||
25 | CCID 2 is further described in: | ||
26 | http://www.icir.org/kohler/dccp/draft-ietf-dccp-ccid2-10.txt | ||
27 | |||
28 | This text was extracted from: | ||
29 | http://www.icir.org/kohler/dccp/draft-ietf-dccp-spec-13.txt | ||
30 | |||
31 | If in doubt, say M. | ||
32 | |||
4 | config IP_DCCP_CCID3 | 33 | config IP_DCCP_CCID3 |
5 | tristate "CCID3 (TFRC) (EXPERIMENTAL)" | 34 | tristate "CCID3 (TCP-Friendly) (EXPERIMENTAL)" |
6 | depends on IP_DCCP | 35 | depends on IP_DCCP |
36 | def_tristate IP_DCCP | ||
7 | ---help--- | 37 | ---help--- |
8 | CCID 3 denotes TCP-Friendly Rate Control (TFRC), an equation-based | 38 | CCID 3 denotes TCP-Friendly Rate Control (TFRC), an equation-based |
9 | rate-controlled congestion control mechanism. TFRC is designed to | 39 | rate-controlled congestion control mechanism. TFRC is designed to |
@@ -15,10 +45,15 @@ config IP_DCCP_CCID3 | |||
15 | suitable than CCID 2 for applications such streaming media where a | 45 | suitable than CCID 2 for applications such streaming media where a |
16 | relatively smooth sending rate is of importance. | 46 | relatively smooth sending rate is of importance. |
17 | 47 | ||
18 | CCID 3 is further described in [CCID 3 PROFILE]. The TFRC | 48 | CCID 3 is further described in: |
19 | congestion control algorithms were initially described in RFC 3448. | 49 | |
50 | http://www.icir.org/kohler/dccp/draft-ietf-dccp-ccid3-11.txt. | ||
51 | |||
52 | The TFRC congestion control algorithms were initially described in | ||
53 | RFC 3448. | ||
20 | 54 | ||
21 | This text was extracted from draft-ietf-dccp-spec-11.txt. | 55 | This text was extracted from: |
56 | http://www.icir.org/kohler/dccp/draft-ietf-dccp-spec-13.txt | ||
22 | 57 | ||
23 | If in doubt, say M. | 58 | If in doubt, say M. |
24 | 59 | ||