From: Valdis.Kletnieks@vt.edu
To: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>,
Andrew Morton <akpm@linux-foundation.org>
Cc: linux-kernel@vger.kernel.org
Subject: RCU Kconfig help text
Date: Sat, 05 Sep 2009 09:27:10 -0400 [thread overview]
Message-ID: <12924.1252157230@turing-police.cc.vt.edu> (raw)
[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]
init/Kconfig says:
"choice
prompt "RCU Implementation"
default TREE_RCU
config TREE_RCU
bool "Tree-based hierarchical RCU"
help
This option selects the RCU implementation that is
designed for very large SMP system with hundreds or
thousands of CPUs. It also scales down nicely to
smaller systems.
config TREE_PREEMPT_RCU
bool "Preemptable tree-based hierarchical RCU"
depends on PREEMPT
help
This option selects the RCU implementation that is
designed for very large SMP systems with hundreds or
thousands of CPUs, but for which real-time response
is also required.
endchoice"
This leaves somebody who has a laptop wondering which choice is best for
a system with only one or two cores that has CONFIG_PREEMPT defined. One
choice says it scales down nicely, the other explicitly has a 'depends on
PREEMPT' attached to it...
(Yes, I realize in practice, the RCU sections on a laptop are probably usually
so short they don't matter in practice. I finally concluded TREE_PREEMPT was
apparently a rename of CONFIG_PREEMPT_RCU and went with that since that was
working for me before...)
[-- Attachment #2: Type: application/pgp-signature, Size: 226 bytes --]
next reply other threads:[~2009-09-05 17:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-05 13:27 Valdis.Kletnieks [this message]
2009-09-05 20:01 ` RCU Kconfig help text Paul E. McKenney
2009-09-06 6:24 ` Pavel Machek
2009-09-06 6:39 ` Paul E. McKenney
2009-09-06 20:07 ` Pavel Machek
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=12924.1252157230@turing-police.cc.vt.edu \
--to=valdis.kletnieks@vt.edu \
--cc=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=paulmck@linux.vnet.ibm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox