Home
last modified time | relevance | path

Searched refs:__note_gp_changes (Results 1 – 2 of 2) sorted by relevance

/Linux-v5.10/Documentation/RCU/Design/Memory-Ordering/
DTree-RCU-Memory-Ordering.rst352 ``__note_gp_changes()`` to notice that a new grace period has started,
374 | ``__note_gp_changes()``. On the other hand, this CPU potentially gets |
375 | early notification because it invokes ``__note_gp_changes()`` during |
399 (or alternatively, directly invoking ``__note_gp_changes()``), at which
404 the invocation of ``__note_gp_changes()`` to have started before the
575 ``__note_gp_changes()``. As shown in the diagram below, this invocation
/Linux-v5.10/kernel/rcu/
Dtree.c1602 static bool __note_gp_changes(struct rcu_node *rnp, struct rcu_data *rdp) in __note_gp_changes() function
1664 needwake = __note_gp_changes(rnp, rdp); in note_gp_changes()
1828 (void)__note_gp_changes(rnp, rdp); in rcu_gp_init()
2019 needgp = __note_gp_changes(rnp, rdp) || needgp; in rcu_gp_cleanup()