Lines Matching +full:kernel +full:- +full:side
1 # SPDX-License-Identifier: GPL-2.0-only
3 # RCU-related configuration options
11 # Dynticks-idle tracking
26 thousands of CPUs, but for which real-time response
37 designed for UP systems from which real-time response
42 bool "Make expert-level adjustments to RCU configuration"
46 expert-level adjustments to RCU configuration. By default,
47 no such adjustments can be made, which has the often-beneficial
48 side-effect of preventing "make oldconfig" from asking you all
52 Say Y if you need to make expert-level adjustments to RCU.
60 This option selects the single-CPU non-preemptible version of SRCU.
66 This option selects the full-fledged version of SRCU.
88 task-based RCU implementations. Not for manual selection.
96 This option force-enables a task-based RCU implementation
98 idle, and user-mode execution as quiescent states. Not for
116 This option force-enables a task-based RCU implementation
118 user-mode execution as quiescent states. It forces IPIs and
133 This option enables a task-based RCU implementation that uses
134 explicit rcu_read_lock_trace() read-side markers, and allows
145 bool "Override RCU Tasks Trace inclusion of read-side memory barriers"
149 This option prevents the use of read-side memory barriers in
160 Those wishing to disable read-side memory barriers for an entire
179 int "Tree-based hierarchical RCU fanout value"
191 systems, but if you are stress-testing the RCU implementation
192 itself, small RCU_FANOUT values allow you to test large-system
199 int "Tree-based hierarchical RCU leaf-level fanout value"
207 This option controls the leaf-level fanout of hierarchical
210 scheduling-clock interrupts for energy-efficiency reasons will
211 want the default because the smaller leaf-level fanout keeps
215 number of cache misses incurred during RCU's grace-period
216 initialization. These systems tend to run CPU-bound, and thus
219 leaf-level fanouts work well. That said, setting leaf-level
221 lock contention on the leaf-level rcu_node structures unless
222 you boot with the skew_tick kernel parameter.
228 kernel boot parameter to avoid contention on the rcu_node
243 Say Y here if you are working with real-time apps or heavy loads
247 int "Milliseconds to delay boosting after RCU grace-period start"
253 a given grace period before priority-boosting preempted RCU
260 bool "Perform RCU expedited work in a real-time kthread"
274 bool "Offload RCU callback processing from boot-selected CPUs"
280 real-time workloads. It can also be used to offload RCU
281 callback invocation to energy-efficient CPUs in battery-powered
284 workloads will incur significant increases in context-switch
291 and where the "x" is "p" for RCU-preempt (PREEMPTION kernels)
292 and "s" for RCU-sched (!PREEMPTION kernels). This option
302 rcutree.rcu_nocb_gp_stride kernel boot parameter. This can
323 bool "Offload RCU callback from real-time kthread"
332 it is your responsibility to ensure that latency-sensitive
336 Say N here if you are building a !PREEMPT_RT kernel and are unsure.
352 Use the rcutree.enable_rcu_lazy=0 kernel-boot parameter to
360 Build the kernel with CONFIG_RCU_LAZY=y, but cause the kernel
361 to boot with these energy-efficiency delays disabled. Use the
362 rcutree.enable_rcu_lazy=0 kernel-boot parameter to override
363 the this option at boot time, thus re-enabling these delays.
366 bool "RCU callback-batch backup time check"
373 thus defeating the 32-callback batching used to amortize the
374 cost of the fine-grained but expensive local_clock() function.
377 jiffy, and overrides the 32-callback batching if this limit
380 Say Y here if you need tighter callback-limit enforcement.