2006-01-02 19:04:38 +01:00
|
|
|
#
|
|
|
|
# TIPC configuration
|
|
|
|
#
|
|
|
|
|
2007-05-23 23:49:38 +02:00
|
|
|
menuconfig TIPC
|
2006-01-02 19:04:38 +01:00
|
|
|
tristate "The TIPC Protocol (EXPERIMENTAL)"
|
2007-05-23 23:49:38 +02:00
|
|
|
depends on INET && EXPERIMENTAL
|
2006-01-02 19:04:38 +01:00
|
|
|
---help---
|
2006-01-16 16:32:18 +01:00
|
|
|
The Transparent Inter Process Communication (TIPC) protocol is
|
|
|
|
specially designed for intra cluster communication. This protocol
|
|
|
|
originates from Ericsson where it has been used in carrier grade
|
|
|
|
cluster applications for many years.
|
2010-01-19 23:23:57 +01:00
|
|
|
|
2006-01-16 16:32:18 +01:00
|
|
|
For more information about TIPC, see http://tipc.sourceforge.net.
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
This protocol support is also available as a module ( = code which
|
|
|
|
can be inserted in and removed from the running kernel whenever you
|
|
|
|
want). The module will be called tipc. If you want to compile it
|
2007-03-16 14:28:43 +01:00
|
|
|
as a module, say M here and read <file:Documentation/kbuild/modules.txt>.
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
If in doubt, say N.
|
|
|
|
|
2007-05-23 23:49:38 +02:00
|
|
|
if TIPC
|
|
|
|
|
2006-01-02 19:04:38 +01:00
|
|
|
config TIPC_ADVANCED
|
2010-01-19 23:23:57 +01:00
|
|
|
bool "Advanced TIPC configuration"
|
2006-01-02 19:04:38 +01:00
|
|
|
default n
|
|
|
|
help
|
2010-01-19 23:23:57 +01:00
|
|
|
Saying Y here will open some advanced configuration for TIPC.
|
|
|
|
Most users do not need to bother; if unsure, just say N.
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
config TIPC_PORTS
|
|
|
|
int "Maximum number of ports in a node"
|
2007-05-23 23:49:38 +02:00
|
|
|
depends on TIPC_ADVANCED
|
2010-01-19 23:23:57 +01:00
|
|
|
range 127 65535
|
2006-01-02 19:04:38 +01:00
|
|
|
default "8191"
|
|
|
|
help
|
2010-01-19 23:23:57 +01:00
|
|
|
Specifies how many ports can be supported by a node.
|
|
|
|
Can range from 127 to 65535 ports; default is 8191.
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2010-12-31 19:59:32 +01:00
|
|
|
Setting this to a smaller value saves some memory,
|
2010-01-19 23:23:57 +01:00
|
|
|
setting it to higher allows for more ports.
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
config TIPC_LOG
|
|
|
|
int "Size of log buffer"
|
2007-05-23 23:49:38 +02:00
|
|
|
depends on TIPC_ADVANCED
|
2010-01-19 23:23:57 +01:00
|
|
|
range 0 32768
|
|
|
|
default "0"
|
2006-01-02 19:04:38 +01:00
|
|
|
help
|
2010-01-19 23:23:57 +01:00
|
|
|
Size (in bytes) of TIPC's internal log buffer, which records the
|
|
|
|
occurrence of significant events. Can range from 0 to 32768 bytes;
|
|
|
|
default is 0.
|
2006-01-02 19:04:38 +01:00
|
|
|
|
|
|
|
There is no need to enable the log buffer unless the node will be
|
|
|
|
managed remotely via TIPC.
|
|
|
|
|
|
|
|
config TIPC_DEBUG
|
2010-12-31 19:59:28 +01:00
|
|
|
bool "Enable debugging support"
|
2006-01-02 19:04:38 +01:00
|
|
|
default n
|
|
|
|
help
|
2010-12-31 19:59:28 +01:00
|
|
|
Saying Y here enables TIPC debugging capabilities used by developers.
|
|
|
|
Most users do not need to bother; if unsure, just say N.
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2010-12-31 19:59:28 +01:00
|
|
|
Enabling debugging support causes TIPC to display data about its
|
|
|
|
internal state when certain abnormal conditions occur. It also
|
|
|
|
makes it easy for developers to capture additional information of
|
|
|
|
interest using the dbg() or msg_dbg() macros.
|
2006-01-02 19:04:38 +01:00
|
|
|
|
2007-05-23 23:49:38 +02:00
|
|
|
endif # TIPC
|