Documentation: RCU: fix brackets
Subsystems (2)
PATCH 1/1 Documentation: RCU: fix brackets
Remove needless brackets and add missing bracket.
Signed-off-by Manuel Ebner <[email protected]>
--- .../Design/Expedited-Grace-Periods/Expedited-Grace-Periods.rst | 2 +- Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp.svg | 2 +- Documentation/RCU/Design/Memory-Ordering/TreeRCU-qs.svg | 2 +- Documentation/RCU/Design/Requirements/Requirements.rst | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-)
Documentation/RCU/Design/Expedited-Grace-Periods/Expedited-Grace-Periods.rst +1 -1
@@ -410,7 +410,7 @@ workqueues (see Documentation/core-api/workqueue.rst). The requesting task still does counter snapshotting and funnel-lock processing, but the task reaching the top of the funnel lock does a -``schedule_work()`` (from ``_synchronize_rcu_expedited()`` so that a +``schedule_work()`` (from ``_synchronize_rcu_expedited()``) so that a workqueue kthread does the actual grace-period processing. Because workqueue kthreads do not accept POSIX signals, grace-period-wait processing need not allow for POSIX signals. In addition, this approach
Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp.svg +1 -1
@@ -3933,7 +3933,7 @@ font-style="normal" y="-3914.085" x="3745.7725" - xml:space="preserve">rcu__report_qs_rdp())</text> + xml:space="preserve">rcu__report_qs_rdp()</text> </g> <g id="g4504-3"
Documentation/RCU/Design/Memory-Ordering/TreeRCU-qs.svg +1 -1
@@ -815,7 +815,7 @@ font-style="normal" y="-3914.085" x="3745.7725" - xml:space="preserve">rcu__report_qs_rdp())</text> + xml:space="preserve">rcu__report_qs_rdp()</text> </g> <g id="g4504-3"
Documentation/RCU/Design/Requirements/Requirements.rst +1 -1
@@ -2785,7 +2785,7 @@ both srcu_read_lock() and srcu_read_unlock(). This need is handled by a Tasks Trace RCU API implemented as thin wrappers around SRCU-fast, which avoids the read-side memory barriers, at least for architectures that apply noinstr to kernel entry/exit code (or that build with -``CONFIG_TASKS_TRACE_RCU_NO_MB=y``. +``CONFIG_TASKS_TRACE_RCU_NO_MB=y``). Now that the implementation is based on SRCU-fast, a call to synchronize_rcu_tasks_trace() implies at least one call to
Signature · 1 line
2.54.0
Paul E. McKenney
maintainerQuoted 3 lines · Manuel Ebner
Remove needless brackets and add missing bracket.
Signed-off-by Manuel Ebner <[email protected]>
Good catches, queued, thank you!
Thanx, Paul
Quoted 62 lines
--- .../Design/Expedited-Grace-Periods/Expedited-Grace-Periods.rst | 2 +- Documentation/RCU/Design/Memory-Ordering/TreeRCU-gp.svg | 2 +- Documentation/RCU/Design/Memory-Ordering/TreeRCU-qs.svg | 2 +- Documentation/RCU/Design/Requirements/Requirements.rst | 2 +- 4 files changed, 4 insertions(+), 4 deletions(-)Documentation/RCU/Design/Expedited-Grace-Periods/Expedited-Grace-Periods.rst +1
-1@@ -410,7 +410,7 @@ workqueues (see Documentation/core-api/workqueue.rst). The requesting task still does counter snapshotting and funnel-lock processing, but the task reaching the top of the funnel lock does a -``schedule_work()`` (from ``_synchronize_rcu_expedited()`` so that a +``schedule_work()`` (from ``_synchronize_rcu_expedited()``) so that a workqueue kthread does the actual grace-period processing. Because workqueue kthreads do not accept POSIX signals, grace-period-wait processing need not allow for POSIX signals. In addition, this approachDocumentation/RCU/Design/Memory-Ordering/TreeRCU-gp.svg +1
-1@@ -3933,7 +3933,7 @@ font-style="normal" y="-3914.085" x="3745.7725" - xml:space="preserve">rcu__report_qs_rdp())</text> + xml:space="preserve">rcu__report_qs_rdp()</text> </g> <g id="g4504-3"Documentation/RCU/Design/Memory-Ordering/TreeRCU-qs.svg +1
-1@@ -815,7 +815,7 @@ font-style="normal" y="-3914.085" x="3745.7725" - xml:space="preserve">rcu__report_qs_rdp())</text> + xml:space="preserve">rcu__report_qs_rdp()</text> </g> <g id="g4504-3"Documentation/RCU/Design/Requirements/Requirements.rst +1
-1@@ -2785,7 +2785,7 @@ both srcu_read_lock() and srcu_read_unlock(). This need is handled by a Tasks Trace RCU API implemented as thin wrappers around SRCU-fast, which avoids the read-side memory barriers, at least for architectures that apply noinstr to kernel entry/exit code (or that build with -``CONFIG_TASKS_TRACE_RCU_NO_MB=y``. +``CONFIG_TASKS_TRACE_RCU_NO_MB=y``). Now that the implementation is based on SRCU-fast, a call to synchronize_rcu_tasks_trace() implies at least one call toSignature · 1 line
2.54.0