[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20220420163600.18b9cd15@gandalf.local.home>
Date: Wed, 20 Apr 2022 16:36:00 -0400
From: Steven Rostedt <rostedt@...dmis.org>
To: Joel Fernandes <joel@...lfernandes.org>
Cc: "Paul E. McKenney" <paulmck@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
Josh Triplett <josh@...htriplett.org>,
Lai Jiangshan <jiangshanlai@...il.com>,
Mathieu Desnoyers <mathieu.desnoyers@...icios.com>,
rcu <rcu@...r.kernel.org>,
Frederic Weisbecker <frederic@...nel.org>
Subject: Re: [PATCH RFC] rcu/nocb: Provide default all-CPUs mask for
RCU_NOCB_CPU=y
On Thu, 14 Apr 2022 17:38:08 -0400
Joel Fernandes <joel@...lfernandes.org> wrote:
> Then it should be called: CONFIG_RCU_NOCB_CPU_DEFAULT_ALL , or
> something. Otherwise I can tell you that I will be the first one to be
> confused by menuconfig unless I also read the code :-D
Naw, I think calling it CONFIG_RCU_NOCB_CPU_ALL is fine, it's what you
write in the help message of the Kconfig file that really matters.
I would always say that what is on the command line should override the
configs (when feasible). To add something to the command line takes effort,
and is always visible (cat /proc/cmdline), whereas configs are hidden and
not as visible to those using the kernel. Not having the command line work
would be annoying, and even if it came up with a message of "The config
says *all* so I'm ignoring what you want to do" would be exceptionally more
annoying as now the user has to recompile the kernel (and only if they
could).
-- Steve
Powered by blists - more mailing lists