Skip to contentSkip to conversation

RCU Kconfig help text

DISCUSSION [email protected] 3 participants 5 messages Sep 5, 2009 – Sep 6, 2009

lore
Share & tools
lore
#0 lore raw

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...)

#1 lore raw
Quoted 30 lines · On Sat, Sep 05, 2009 at 09:27:10AM -0400, [email protected] wrote:

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...

Quoted 4 lines

(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...)

Good point -- I will add the "It also scales down nicely to smaller systems" to TREE_PREEMPT_RCU.

For -really- small systems, TINY_RCU will hopefully be there at some point, but it can only handle single-CPU systems.

Thanx, Paul

#2 lore raw
Quoted 36 lines · Paul E. McKenney
Quoted 30 lines · On Sat, Sep 05, 2009 at 09:27:10AM -0400, [email protected] wrote:

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...

Quoted 4 lines

(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...)

Quoted 5 lines

Good point -- I will add the "It also scales down nicely to smaller systems" to TREE_PREEMPT_RCU.

For -really- small systems, TINY_RCU will hopefully be there at some point, but it can only handle single-CPU systems.

If so, call it 'UP_RCU' or 'UNIPROCESSOR_RCU'?
Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
#3 lore raw
Quoted 37 lines · Pavel Machek
Quoted 36 lines · Paul E. McKenney
Quoted 34 lines · On Sat, Sep 05, 2009 at 09:27:10AM -0400, [email protected] wrote:

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...)

Quoted 7 lines
Quoted 5 lines

Good point -- I will add the "It also scales down nicely to smaller systems" to TREE_PREEMPT_RCU.

For -really- small systems, TINY_RCU will hopefully be there at some point, but it can only handle single-CPU systems.

If so, call it 'UP_RCU' or 'UNIPROCESSOR_RCU'?

"UP_RCU". Cute!!! ;-)

My hope is to drive the RCU selection directly from CONFIG_SMP and CONFIG_PREEMPT, so that the choice of RCU would be implicit (aside from things like tracing and fanout).

Seem reasonable, or would you expect anyone to want to hand-select the RCU implementation?

Thanx, Paul

#4 lore raw
Quoted 18 lines
Quoted 10 lines
Quoted 10 lines
Quoted 9 lines

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...)

Quoted 7 lines
Quoted 5 lines

Good point -- I will add the "It also scales down nicely to smaller systems" to TREE_PREEMPT_RCU.

For -really- small systems, TINY_RCU will hopefully be there at some point, but it can only handle single-CPU systems.

If so, call it 'UP_RCU' or 'UNIPROCESSOR_RCU'?

Quoted 8 lines

"UP_RCU". Cute!!! ;-)

My hope is to drive the RCU selection directly from CONFIG_SMP and CONFIG_PREEMPT, so that the choice of RCU would be implicit (aside from things like tracing and fanout).

Seem reasonable, or would you expect anyone to want to hand-select the RCU implementation?

Seems reasonable.

Pavel

Signature · 2 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html