tipc: use kconfig to limit numeric ranges
We can rely on kconfig to limit these numbers, no need to limit them at compile time/run time. Users who modify these numbers manually should be responsible for themself. :) Signed-off-by: WANG Cong <amwang@redhat.com> Cc: Per Liden <per.liden@ericsson.com> Cc: Jon Maloy <jon.maloy@ericsson.com> Cc: Allan Stephens <allan.stephens@windriver.com> Cc: David S. Miller <davem@davemloft.net> Signed-off-by: David S. Miller <davem@davemloft.net>
This commit is contained in:
committed by
David S. Miller
parent
c1c5523dd1
commit
ee983ac768
@@ -189,11 +189,11 @@ static int __init tipc_init(void)
|
||||
tipc_remote_management = 1;
|
||||
tipc_max_publications = 10000;
|
||||
tipc_max_subscriptions = 2000;
|
||||
tipc_max_ports = delimit(CONFIG_TIPC_PORTS, 127, 65536);
|
||||
tipc_max_zones = delimit(CONFIG_TIPC_ZONES, 1, 255);
|
||||
tipc_max_clusters = delimit(CONFIG_TIPC_CLUSTERS, 1, 1);
|
||||
tipc_max_nodes = delimit(CONFIG_TIPC_NODES, 8, 2047);
|
||||
tipc_max_slaves = delimit(CONFIG_TIPC_SLAVE_NODES, 0, 2047);
|
||||
tipc_max_ports = CONFIG_TIPC_PORTS;
|
||||
tipc_max_zones = CONFIG_TIPC_ZONES;
|
||||
tipc_max_clusters = CONFIG_TIPC_CLUSTERS;
|
||||
tipc_max_nodes = CONFIG_TIPC_NODES;
|
||||
tipc_max_slaves = CONFIG_TIPC_SLAVE_NODES;
|
||||
tipc_net_id = 4711;
|
||||
|
||||
if ((res = tipc_core_start()))
|
||||
|
Reference in New Issue
Block a user