Lines Matching full:callbacks

121 RCU updaters wait for normal grace periods by registering RCU callbacks,
123 ``synchronize_rcu()`` and friends. RCU callbacks are represented by
156    serves as short-term repository for callbacks orphaned by CPU-hotplug
182 #. ``rcu_head``: This structure represents RCU callbacks, and is the
670 The ``rcu_segcblist`` structure maintains a segmented list of callbacks
691 #. ``RCU_DONE_TAIL``: Callbacks whose grace periods have elapsed. These
692    callbacks are ready to be invoked.
693 #. ``RCU_WAIT_TAIL``: Callbacks that are waiting for the current grace
696 #. ``RCU_NEXT_READY_TAIL``: Callbacks waiting for the next grace period
698 #. ``RCU_NEXT_TAIL``: Callbacks that have not yet been associated with a
702 the list contains no callbacks (which is *not* the same as being empty).
708 its predecessor. Older callbacks are closer to the head of the list, and
709 new callbacks are added at the tail. This relationship between the
710 ``->head`` pointer, the ``->tails[]`` array, and the callbacks is shown
717 ``->head`` pointer itself, indicating that none of the callbacks is
724 there are no callbacks waiting on the next RCU grace period. The
726 pointer, indicating that all the remaining RCU callbacks have not yet
735 offline or when the corresponding CPU's callbacks are offloaded to a
738 CPUs advance their callbacks from the ``RCU_NEXT_TAIL`` to the
745 premature invocation of their callbacks. In particular, this allows CPUs
746 that go idle for extended periods to determine which of their callbacks
749 The ``->len`` counter contains the number of callbacks in ``->head``,
750 and the ``->len_lazy`` contains the number of those callbacks that are
757    not there are callbacks associated with this ``rcu_segcblist``
759    the ready-to-invoke callbacks (that is, those in the ``RCU_DONE_TAIL``
762    are no not-done callbacks remaining in the ``rcu_segcblist``. If
765    callbacks are placed back on the ``RCU_DONE_TAIL`` segment and
767    head field can briefly be ``NULL`` even though the CPU has callbacks
772 after the corresponding callbacks have been invoked. This means that the
774 is devoid of callbacks. Of course, off-CPU sampling of the ``->len``
875 In the absence of CPU-hotplug events, RCU callbacks are invoked by the
877 optimization: callbacks can and do get invoked on CPUs other than the
896 earlier. The CPU advances the callbacks in its ``rcu_data`` structure
909 fields count the number of callbacks invoked, sent to other CPUs when
912 callbacks are offloaded to a kthread.
914 Finally, the ``->blimit`` counter is the maximum number of RCU callbacks