Design/Data-Structures/Data-Structures.rst

137 #. Each ``rcu_state`` structures has a lock and a mutex, and some fields
140 #. The fields in ``rcu_data`` are private to the corresponding CPU,
202 A few of the ``rcu_state`` structure's fields are discussed, singly and
203 in groups, in the following sections. The more specialized fields are
262 All of these fields are constant once initialization is complete, and
282 There are ``->gp_seq`` fields in the ``rcu_node`` and ``rcu_data``
283 structures as well. The fields in the ``rcu_state`` structure represent
303 The ``->name`` and ``->abbr`` fields distinguish between preemptible RCU
305 These fields are used for diagnostic and tracing purposes.
323 The ``rcu_node`` structure's fields are discussed, singly and in groups,
347 on 64-bit systems. The ``->level`` and ``->grpnum`` fields are used only
352 later. Finally, the ``->grplo`` and ``->grphi`` fields contain the
356 All of these fields are constant, and thus do not require any
368 This field is used to protect the remaining fields in this structure,
369 unless otherwise stated. That said, all of the fields in this structure
386 The ``rcu_node`` structures' ``->gp_seq`` fields are the counterparts of
395 The ``->gp_seq_needed`` fields record the furthest-in-the-future grace
418 These fields manage the propagation of quiescent states up the combining
421 This portion of the ``rcu_node`` structure has fields as follows:
511 two fields are ``NULL`` if either there is no grace period in flight or
637 fields. The number of CPUs per leaf ``rcu_node`` structure is therefore
783 fields in this structure may be accessed only from the corresponding CPU
794 The ``rcu_data`` structure's fields are discussed, singly and in groups,
812 tree. These two fields are constant and therefore do not require
909 fields count the number of callbacks invoked, sent to other CPUs when
944 These fields in the rcu_data structure maintain the per-CPU dyntick-idle
945 state for the corresponding CPU. The fields may be accessed only from
987 corresponding CPU, with the various other fields indicating just how
1006 Additional fields are present for some special-purpose builds, and are
1018 The ``rcu_head`` structure has fields as follows:
1033 Both of these fields are used internally by RCU. From the viewpoint of
1055 The ``CONFIG_PREEMPT_RCU`` implementation uses some additional fields in
1143 is tracked by dynticks-related fields in the ``rcu_data`` structure. If