[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20130530.154925.298481337221579707.davem@davemloft.net>
Date: Thu, 30 May 2013 15:49:25 -0700 (PDT)
From: David Miller <davem@...emloft.net>
To: paul.gortmaker@...driver.com
Cc: netdev@...r.kernel.org, jon.maloy@...csson.com,
ying.xue@...driver.com, erik.hugne@...csson.com
Subject: Re: [PATCH net-next 02/12] tipc: Add "max_ports" configuration
parameter
From: Paul Gortmaker <paul.gortmaker@...driver.com>
Date: Thu, 30 May 2013 15:36:07 -0400
> From: Erik Hugne <erik.hugne@...csson.com>
>
> Introduce the "max_ports" module parameter, which allows the maximum
> number of ports supported by TIPC to be changed from the default value
> at boot, or at module load time. Because of the way the port reference
> table is structured and initiated, this value must be known at module
> start time, and can not be changed later.
>
> Until now this value has been set via a macro, and hence things
> have to be recompiled if the value is to be changed. The Kconfig
> knob and the dead code intended to change this parameter at runtime
> are dropped.
>
> Considering TIPC node addresses are unique on the entire node, the
> 64k port limit has proven to be a little too strict. We increase the
> allowed max to 128k. This is safe since the protocol headers allow
> for up to 2^32 -1 ports.
>
> Usage for module: "insmod tipc.ko max_ports=<value>" ; at boot, append
> "tipc.max_ports=<value>" to the kernel command line.
>
> Signed-off-by: Erik Hugne <erik.hugne@...csson.com>
> Reviewed-by: Jon Maloy <jon.maloy@...csson.com>
> Signed-off-by: Paul Gortmaker <paul.gortmaker@...driver.com>
View compile time constants and module parameters as artificial
limits, they are terrible and unnecessary.
There is no reason you cannot restructure this table so that you
can dynamically size it at run time.
Please reimplement it in that way.
Thanks.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Powered by blists - more mailing lists