linux-kernel - Re: rcu: Provide compile-time control for no-CBs CPUs

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20130430221915.GM3780@linux.vnet.ibm.com>
Date:	Tue, 30 Apr 2013 15:19:15 -0700
From:	"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>
To:	Dave Jones <davej@...hat.com>,
	Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
	paul.mckenney@...aro.org, mmarek@...e.cz,
	linux-kbuild@...r.kernel.org
Subject: Re: rcu: Provide compile-time control for no-CBs CPUs

On Tue, Apr 30, 2013 at 06:06:47PM -0400, Dave Jones wrote:
> On Tue, Apr 30, 2013 at 02:48:26PM -0700, Paul E. McKenney wrote:
> 
>  > <snip excellent explanation>
>  >
>  > Should I add this to the Kconfig help text?  My guess is "not all of it",
>  > but figured I should ask.
> 
> The commit msg would have been a great place for much of it, especially
> the part explaining your desire to have users kick the tires etc.

Good point, will keep that in mind for next time.

>  >  See below for my current best guess.
> 
> Much better. Be sure to pass on the 'terrible kconfig' award to the
> next lucky recipient when their time comes :)

Interesting.  Who passed it to you, and what was the occasion?  ;-)

							Thanx, Paul

--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/