Kconfig 2.1 KB

12345678910111213141516171819202122232425262728293031323334353637383940414243444546474849505152535455565758596061626364656667686970
  1. #
  2. # TIPC configuration
  3. #
  4. menuconfig TIPC
  5. tristate "The TIPC Protocol (EXPERIMENTAL)"
  6. depends on INET && EXPERIMENTAL
  7. ---help---
  8. The Transparent Inter Process Communication (TIPC) protocol is
  9. specially designed for intra cluster communication. This protocol
  10. originates from Ericsson where it has been used in carrier grade
  11. cluster applications for many years.
  12. For more information about TIPC, see http://tipc.sourceforge.net.
  13. This protocol support is also available as a module ( = code which
  14. can be inserted in and removed from the running kernel whenever you
  15. want). The module will be called tipc. If you want to compile it
  16. as a module, say M here and read <file:Documentation/kbuild/modules.txt>.
  17. If in doubt, say N.
  18. if TIPC
  19. config TIPC_ADVANCED
  20. bool "Advanced TIPC configuration"
  21. default n
  22. help
  23. Saying Y here will open some advanced configuration for TIPC.
  24. Most users do not need to bother; if unsure, just say N.
  25. config TIPC_PORTS
  26. int "Maximum number of ports in a node"
  27. depends on TIPC_ADVANCED
  28. range 127 65535
  29. default "8191"
  30. help
  31. Specifies how many ports can be supported by a node.
  32. Can range from 127 to 65535 ports; default is 8191.
  33. Setting this to a smaller value saves some memory,
  34. setting it to higher allows for more ports.
  35. config TIPC_LOG
  36. int "Size of log buffer"
  37. depends on TIPC_ADVANCED
  38. range 0 32768
  39. default "0"
  40. help
  41. Size (in bytes) of TIPC's internal log buffer, which records the
  42. occurrence of significant events. Can range from 0 to 32768 bytes;
  43. default is 0.
  44. There is no need to enable the log buffer unless the node will be
  45. managed remotely via TIPC.
  46. config TIPC_DEBUG
  47. bool "Enable debugging support"
  48. default n
  49. help
  50. Saying Y here enables TIPC debugging capabilities used by developers.
  51. Most users do not need to bother; if unsure, just say N.
  52. Enabling debugging support causes TIPC to display data about its
  53. internal state when certain abnormal conditions occur. It also
  54. makes it easy for developers to capture additional information of
  55. interest using the dbg() or msg_dbg() macros.
  56. endif # TIPC