Design/Data-Structures/Data-Structures.rst

20 to execute extremely quickly, while also processing the RCU grace periods
46 grace periods are completed at the tree's root ``rcu_node``
121 RCU updaters wait for normal grace periods by registering RCU callbacks,
155    ``rcu_node`` and ``rcu_data`` structures, tracks grace periods,
159    states when grace periods extend too long,
198 periods, contains the lock used to synchronize with CPU-hotplug events,
199 and maintains state used to force quiescent states when grace periods
241 periods.
274 RCU grace periods are numbered, and the ``->gp_seq`` field contains the
285 in order to detect the beginnings and ends of grace periods in a
446 expedited grace periods, respectively.
510 periods and in ``->exp_tasks`` for expedited grace periods. These last
528 Task T1 is blocking both grace periods, task T2 is blocking only the
691 #. ``RCU_DONE_TAIL``: Callbacks whose grace periods have elapsed. These
740 ``RCU_DONE_TAIL`` list segments as grace periods advance.
746 that go idle for extended periods to determine which of their callbacks
1014 algorithms use asynchronous grace periods. In contrast, when using
1015 algorithms that block waiting for RCU grace periods, RCU users need not