94fc9c4719
There used to be a time when TIPC had lots of Kconfig knobs the end user could alter, but they have all been made automatic or obsolete, with the exception of CONFIG_TIPC_PORTS. This previously existing set of options was all hidden under the TIPC_ADVANCED setting, which does not exist in any code, but only in Kconfig scope. Having this now, just to hide the one remaining "advanced" option no longer makes sense. Remove it. Also get rid of the ifdeffery in the TIPC code that allowed for TIPC_PORTS to be possibly undefined. Signed-off-by: Paul Gortmaker <paul.gortmaker@windriver.com>
34 lines
1.1 KiB
Plaintext
34 lines
1.1 KiB
Plaintext
#
|
|
# TIPC configuration
|
|
#
|
|
|
|
menuconfig TIPC
|
|
tristate "The TIPC Protocol (EXPERIMENTAL)"
|
|
depends on INET && EXPERIMENTAL
|
|
---help---
|
|
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.
|
|
|
|
For more information about TIPC, see http://tipc.sourceforge.net.
|
|
|
|
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
|
|
as a module, say M here and read <file:Documentation/kbuild/modules.txt>.
|
|
|
|
If in doubt, say N.
|
|
|
|
config TIPC_PORTS
|
|
int "Maximum number of ports in a node"
|
|
depends on TIPC
|
|
range 127 65535
|
|
default "8191"
|
|
help
|
|
Specifies how many ports can be supported by a node.
|
|
Can range from 127 to 65535 ports; default is 8191.
|
|
|
|
Setting this to a smaller value saves some memory,
|
|
setting it to higher allows for more ports.
|