10.3.2 RCU Usage
Keywords: perfbook_html

##
10.3.2 RCU Usage

Table: RCU Usage
Mechanism RCU Replaces | Section
Reader-writer locking | Section
Restricted reference-counting mechanism | Section
Bulk reference-counting mechanism | Section
Poor man's garbage collector | Section
Existence Guarantees | Section
Type-Safe Memory | Section
Wait for things to finish | Section

This section answers the question "what is RCU?" from the viewpoint of the uses to which RCU can be put. Because RCU is most frequently used to replace some existing mechanism, we look at it primarily in terms of its relationship to such mechanisms, as listed in Table . Following the sections listed in this table, Section provides a summary.

Subsections

- 10.3.2.1 RCU is a Reader-Writer Lock Replacement
  - 10.3.2.1.1 Performance
  - 10.3.2.1.2 Deadlock Immunity
  - 10.3.2.1.3 Realtime Latency
  - 10.3.2.1.4 RCU Readers and Updaters Run Concurrently
  - 10.3.2.1.5 Low-Priority RCU Readers Can Block High-Priority Reclaimers
  - 10.3.2.1.6 RCU Grace Periods Extend for Many Milliseconds
  - 10.3.2.1.7 Comparison of Reader-Writer Locking and RCU Code
- 10.3.2.2 RCU is a Restricted Reference-Counting Mechanism
- 10.3.2.3 RCU is a Bulk Reference-Counting Mechanism
- 10.3.2.4 RCU is a Poor Man's Garbage Collector
- 10.3.2.5 RCU is a Way of Providing Existence Guarantees
- 10.3.2.6 RCU is a Way of Providing Type-Safe Memory
- 10.3.2.7 RCU is a Way of Waiting for Things to Finish
- 10.3.2.8 RCU Usage Summary