aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/RCU/whatisRCU.txt
diff options
context:
space:
mode:
Diffstat (limited to 'Documentation/RCU/whatisRCU.txt')
-rw-r--r--Documentation/RCU/whatisRCU.txt5
1 files changed, 4 insertions, 1 deletions
diff --git a/Documentation/RCU/whatisRCU.txt b/Documentation/RCU/whatisRCU.txt
index 8ed6c9f6133c..df62466da4e0 100644
--- a/Documentation/RCU/whatisRCU.txt
+++ b/Documentation/RCU/whatisRCU.txt
@@ -890,6 +890,8 @@ SRCU: Critical sections Grace period Barrier
890 srcu_read_lock_held 890 srcu_read_lock_held
891 891
892SRCU: Initialization/cleanup 892SRCU: Initialization/cleanup
893 DEFINE_SRCU
894 DEFINE_STATIC_SRCU
893 init_srcu_struct 895 init_srcu_struct
894 cleanup_srcu_struct 896 cleanup_srcu_struct
895 897
@@ -913,7 +915,8 @@ a. Will readers need to block? If so, you need SRCU.
913b. What about the -rt patchset? If readers would need to block 915b. What about the -rt patchset? If readers would need to block
914 in an non-rt kernel, you need SRCU. If readers would block 916 in an non-rt kernel, you need SRCU. If readers would block
915 in a -rt kernel, but not in a non-rt kernel, SRCU is not 917 in a -rt kernel, but not in a non-rt kernel, SRCU is not
916 necessary. 918 necessary. (The -rt patchset turns spinlocks into sleeplocks,
919 hence this distinction.)
917 920
918c. Do you need to treat NMI handlers, hardirq handlers, 921c. Do you need to treat NMI handlers, hardirq handlers,
919 and code segments with preemption disabled (whether 922 and code segments with preemption disabled (whether