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