Lines Matching full:corresponding

138    are protected by the corresponding root ``rcu_node`` structure's lock.
140 #. The fields in ``rcu_data`` are private to the corresponding CPU,
175    to the corresponding leaf ``rcu_node`` structure to allow
179    access to this information from the corresponding CPU. Finally, this
180    structure records past dyntick-idle state for the corresponding CPU
244 structure on the corresponding level of the tree, for example, as shown
260 corresponding CPU's ``rcu_data`` structure.
350 one bit set. This mask is used to clear the bit corresponding to this
396 period request seen by the corresponding ``rcu_node`` structure. The
433 corresponding bit. Note that the leaf ``rcu_node`` structures should be
502 ``->blkd_tasks`` list for the leaf ``rcu_node`` structure corresponding
704 pointer of the last callback in the corresponding segment of the list,
706 segments are empty. If the corresponding segment is empty but some
734 list is *disabled*. Lists are disabled when the corresponding CPU is
735 offline or when the corresponding CPU's callbacks are offloaded to a
742 The ``->gp_seq[]`` array records grace-period numbers corresponding to
772 after the corresponding callbacks have been invoked. This means that the
783 fields in this structure may be accessed only from the corresponding CPU
786 its relationship to the corresponding leaf ``rcu_node`` structure to
790 access to this information from the corresponding CPU. Finally, this
791 structure records past dyntick-idle state for the corresponding CPU and
809 The ``->cpu`` field contains the number of the corresponding CPU and the
810 ``->mynode`` field references the corresponding ``rcu_node`` structure.
816 corresponding to this ``rcu_data`` structure, and is also used when
818 the corresponding CPU comes online, which means that the debugfs tracing
866 that the RCU core needs a quiescent state from the corresponding CPU.
867 The ``->gpwrap`` field indicates that the corresponding CPU has remained
928 corresponding CPU's dyntick-idle state when forcing quiescent states,
945 state for the corresponding CPU. The fields may be accessed only from
946 the corresponding CPU (and from tracing) unless otherwise stated.
969 every time the corresponding CPU enters the idle loop from process
972 The ``->dynticks`` field counts the corresponding CPU's transitions to
980 corresponding CPU, so much so that it is willing to call for
987 corresponding CPU, with the various other fields indicating just how
997 | counts the number of reasons that the corresponding CPU is non-idle?  |