Skip to content

Documentation updates for 4.6

Paul E. McKenney lkml 1 version In review

Get series with b4
b4 am [email protected]

Versions newest first

  1. v1 Latest14 patches 8 repliesIn review

Patches in v1 No applies recorded yet

#Subject and filesSizeRepliesApplied
1/14documentation: Add real-time requirements from CPU-bound workloadsDocumentation/RCU/Design/Requirements/Requirements.html Documentation/RCU/Design/Requirements/Requirements.htmlx+17 -10 replies
2/14documentation: Fix control dependency and identical storesDocumentation/memory-barriers.txt+7 -38 replies
3/14documentation: Fix memory-barriers.txt section referencesDocumentation/memory-barriers.txt+2 -20 replies
4/14documentation: Add synchronize_rcu_mult() to the requirementsDocumentation/RCU/Design/Requirements/Requirements.html Documentation/RCU/Design/Requirements/Requirements.htmlx+174 -00 replies
5/14documentation: Remove obsolete reference to RCU-protected indexesDocumentation/memory-barriers.txt+0 -150 replies
6/14documentation: Subsequent writes ordered by rcu_dereference()Documentation/memory-barriers.txt+24 -00 replies
7/14documentation: Distinguish between local and global transitivityDocumentation/memory-barriers.txt+76 -20 replies
8/14documentation: Add alternative release-acquire outcomeDocumentation/memory-barriers.txt+4 -00 replies
9/14documentation: Add documentation for RCU's major data structuresDocumentation/RCU/Design/Data-Structures/BigTreeClassicRCU.svg Documentation/RCU/Design/Data-Structures/BigTreeClassicRCUBH.svg Documentation/RCU/Design/Data-Structures/BigTreeClassicRCUBHdyntick.svg +10 more+9602 -00 replies
10/14documentation: Explain why rcu_read_lock() needs no barrier()Documentation/RCU/Design/Requirements/Requirements.html Documentation/RCU/Design/Requirements/Requirements.htmlx+115 -430 replies
11/14documentation: Transitivity is not cumulativityDocumentation/memory-barriers.txt+1 -10 replies
12/14documentation: Document illegality of call_rcu() from offline CPUsDocumentation/RCU/Design/Requirements/Requirements.html Documentation/RCU/Design/Requirements/Requirements.htmlx+4 -20 replies
13/14documentation: Explain how RCU's combining tree fights contentionDocumentation/RCU/Design/Data-Structures/Data-Structures.html Documentation/RCU/Design/Data-Structures/Data-Structures.htmlx+46 -00 replies
14/14documentation: Clarify compiler store-fusion exampleDocumentation/memory-barriers.txt+2 -20 replies

Reviews trailers per patch

1 of 14 patches has a Reviewed-by or Acked-by.

PatchDavid Howells
1/14
2/14
3/14
4/14
5/14
6/14
7/14
8/14
9/14
10/14
11/14
12/14
13/14
14/14A-b

Trailers given in replies are filled; those carried in the patches from earlier versions are outlined with dashes.

Read the v1 thread

Cover letter [PATCH tip/core/rcu 0/14] Documentation updates for 4.6

Hello!

This series contains documentation updates as follows:

1. Update the requirements design-level documentation to record RCU's
responsibility to avoid injecting OS jitter onto nohz_full CPUs.

2. Fix control-dependency summary of memory-barriers.txt to
note that barrier() does not always prevent code reordering when both legs of an "if" statement begin with identical code.

3. Fix memory-barriers.txt section references.

4. Update the requirements design-level documentation to add
synchronize_rcu_mult().

5. Remove obsolete references to RCU-protected array indexes from
memory-barriers.txt.

6. Update memory-barriers.txt to explicitly state that
rcu_dereference() orders writes to as well as reads from the RCU-protected data item.

7. Update memory-barriers.txt to distinguish between local and
global transitivity.

8. Update memory-barriers.txt to add alternative outcome from
release-acquire chain.

9. Add design-level documentation for RCU's major data structures.

10. Update the requirements design-level documentation to explain
why rcu_read_lock() needs no barrier() for PREEMPT=n.

11. Remove misleading statement that transitivity is cumulativity
from memory-barriers.txt.

12. Update the requirements design-level documentation to explicitly
state that it is illegal to invoke call_rcu() from an offline CPU.

13. Add text to the design-level documentation for RCU's major data
structures stating how the combining tree keeps lock contention under control.

14. Clarify compiler store-fusion example in memory-barriers.txt.

Thanx, Paul

------------------------------------------------------------------------

 RCU/Design/Data-Structures/BigTreeClassicRCU.svg            |  474 ++++
 RCU/Design/Data-Structures/BigTreeClassicRCUBH.svg          |  499 ++++
 RCU/Design/Data-Structures/BigTreeClassicRCUBHdyntick.svg   |  695 +++++
 RCU/Design/Data-Structures/BigTreePreemptRCUBHdyntick.svg   |  741 ++++++
 RCU/Design/Data-Structures/BigTreePreemptRCUBHdyntickCB.svg |  858 +++++++
 RCU/Design/Data-Structures/Data-Structures.html             | 1395 ++++++++++++
 RCU/Design/Data-Structures/Data-Structures.htmlx            | 1295 +++++++++++
 RCU/Design/Data-Structures/HugeTreeClassicRCU.svg           |  939 ++++++++
 RCU/Design/Data-Structures/TreeLevel.svg                    |  828 +++++++
 RCU/Design/Data-Structures/TreeMapping.svg                  |  305 ++
 RCU/Design/Data-Structures/TreeMappingLevel.svg             |  380 +++
 RCU/Design/Data-Structures/blkd_task.svg                    |  843 +++++++
 RCU/Design/Data-Structures/nxtlist.svg                      |  396 +++
 RCU/Design/Requirements/Requirements.html                   |  235 +-
 RCU/Design/Requirements/Requirements.htmlx                  |  121 +
 memory-barriers.txt                                         |  141 -
 16 files changed, 10074 insertions(+), 71 deletions(-)