Kconfig 3.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970717273747576777879808182838485868788899091
  1. menu "DCCP CCIDs Configuration (EXPERIMENTAL)"
  2. depends on EXPERIMENTAL
  3. config IP_DCCP_CCID2_DEBUG
  4. bool "CCID-2 debugging messages"
  5. ---help---
  6. Enable CCID-2 specific debugging messages.
  7. The debugging output can additionally be toggled by setting the
  8. ccid2_debug parameter to 0 or 1.
  9. If in doubt, say N.
  10. config IP_DCCP_CCID3
  11. bool "CCID-3 (TCP-Friendly) (EXPERIMENTAL)"
  12. def_bool y if (IP_DCCP = y || IP_DCCP = m)
  13. select IP_DCCP_TFRC_LIB
  14. ---help---
  15. CCID-3 denotes TCP-Friendly Rate Control (TFRC), an equation-based
  16. rate-controlled congestion control mechanism. TFRC is designed to
  17. be reasonably fair when competing for bandwidth with TCP-like flows,
  18. where a flow is "reasonably fair" if its sending rate is generally
  19. within a factor of two of the sending rate of a TCP flow under the
  20. same conditions. However, TFRC has a much lower variation of
  21. throughput over time compared with TCP, which makes CCID-3 more
  22. suitable than CCID-2 for applications such streaming media where a
  23. relatively smooth sending rate is of importance.
  24. CCID-3 is further described in RFC 4342,
  25. http://www.ietf.org/rfc/rfc4342.txt
  26. The TFRC congestion control algorithms were initially described in
  27. RFC 5448.
  28. This text was extracted from RFC 4340 (sec. 10.2),
  29. http://www.ietf.org/rfc/rfc4340.txt
  30. If in doubt, say N.
  31. config IP_DCCP_CCID3_DEBUG
  32. bool "CCID-3 debugging messages"
  33. depends on IP_DCCP_CCID3
  34. ---help---
  35. Enable CCID-3 specific debugging messages.
  36. The debugging output can additionally be toggled by setting the
  37. ccid3_debug parameter to 0 or 1.
  38. If in doubt, say N.
  39. config IP_DCCP_CCID3_RTO
  40. int "Use higher bound for nofeedback timer"
  41. default 100
  42. depends on IP_DCCP_CCID3 && EXPERIMENTAL
  43. ---help---
  44. Use higher lower bound for nofeedback timer expiration.
  45. The TFRC nofeedback timer normally expires after the maximum of 4
  46. RTTs and twice the current send interval (RFC 3448, 4.3). On LANs
  47. with a small RTT this can mean a high processing load and reduced
  48. performance, since then the nofeedback timer is triggered very
  49. frequently.
  50. This option enables to set a higher lower bound for the nofeedback
  51. value. Values in units of milliseconds can be set here.
  52. A value of 0 disables this feature by enforcing the value specified
  53. in RFC 3448. The following values have been suggested as bounds for
  54. experimental use:
  55. * 16-20ms to match the typical multimedia inter-frame interval
  56. * 100ms as a reasonable compromise [default]
  57. * 1000ms corresponds to the lower TCP RTO bound (RFC 2988, 2.4)
  58. The default of 100ms is a compromise between a large value for
  59. efficient DCCP implementations, and a small value to avoid disrupting
  60. the network in times of congestion.
  61. The purpose of the nofeedback timer is to slow DCCP down when there
  62. is serious network congestion: experimenting with larger values should
  63. therefore not be performed on WANs.
  64. config IP_DCCP_TFRC_LIB
  65. tristate
  66. default n
  67. config IP_DCCP_TFRC_DEBUG
  68. bool
  69. depends on IP_DCCP_TFRC_LIB
  70. default y if IP_DCCP_CCID3_DEBUG
  71. endmenu