Lines Matching refs:leaf
28 of ``rcu_node`` structures. Each leaf node of the ``rcu_node`` tree has up
43 and other events are recorded by the leaf-level ``rcu_node``
65 | Because there are more types of events that affect the leaf-level |
67 | leaf ``rcu_node`` structures have fanout of 64, the contention on |
73 | thousands of CPUs may demonstrate that the fanout for the non-leaf |
77 | on the non-leaf ``rcu_node`` structures, you may use the |
79 | non-leaf fanout as needed. |
106 up the tree. This means that at the leaf-level ``rcu_node`` structure,
175 to the corresponding leaf ``rcu_node`` structure to allow
252 first leaf ``rcu_node`` structure.
433 corresponding bit. Note that the leaf ``rcu_node`` structures should be
502 ``->blkd_tasks`` list for the leaf ``rcu_node`` structure corresponding
523 critical section, then the state of the last leaf ``rcu_node``
628 each non-leaf level of the ``rcu_node`` tree. If the
633 each leaf ``rcu_node`` structure. Experience has shown that allowing a
634 given leaf ``rcu_node`` structure to handle 64 CPUs, as permitted by the
636 excessive contention for the leaf ``rcu_node`` structures' ``->lock``
637 fields. The number of CPUs per leaf ``rcu_node`` structure is therefore
786 its relationship to the corresponding leaf ``rcu_node`` structure to
900 its leaf ``rcu_node`` structure. Recall that each ``rcu_node``
1123 array, thus traversing only the leaf ``rcu_node`` structures.