Read-Copy-Update study and documentation
o What is RCU? Overview, block diagram.
o RCU read-side critical sections.
o RCU quiescent states (momentary and extended).
o RCU grace periods.
o RCU idleness (no grace period in progress)
Why preemptible RCU? History, including isolcpus monastery approach.
Why keep RCU-sched if there is preemptible RCU?
Why RCU-bh?
Why SRCU?
Why workqueue RCU?
Note: these articles not only contain trick questions, they
contain more than a few trick answers. My goal in writing
this was to find bugs in RCU, and you are less likely to
be able to do this if you aren't thinking on your feet. And
there is nothing quite like a few trick questions and answers
to help you think on your feet!
Blueprint information
- Status:
- Complete
- Approver:
- David Rusling
- Priority:
- Medium
- Drafter:
- Paul McKenney
- Direction:
- Needs approval
- Assignee:
- Paul McKenney
- Definition:
- Obsolete
- Series goal:
- Accepted for trunk
- Implementation:
- Informational
- Milestone target:
- backlog
- Started by
- Completed by
- Ilias Biris
Related branches
Related bugs
Sprints
Whiteboard
[paulmck] Safe Data Access section: TODO
[paulmck] Updaters section: DONE
[paulmck] Expedited Grace Period section: DONE
[paulmck] Readers section: DONE
[paulmck] Quiescent State Detection section: DONE
[paulmck] Grace Period Detection section: DONE
[paulmck] Callback Handling section: DONE
[paulmck] Scheduler Interface section: TODO
[paulmck] Priority Boosting section: TODO
[paulmck] Force Quiescent State section: TODO
[paulmck] CPU Hotplug section: INPROGRESS
[paulmck] Automated Review section: TODO
[paulmck] Dyntick Idle section: DONE
[paulmck] Stall Detection section: TODO
[paulmck] Overview section: TODO
[paulmck] RCU API section (update from http://
[paulmck] RCU Tracing section: TODO
[paulmck] RCU Kconfig and Sysfs section: TODO
[paulmck] rcutorture section: TODO
[paulmck] TINY_RCU section: TODO
[paulmck] TINY_PREEMPT_RCU section: TODO