Home
last modified time | relevance | path

Searched refs:expedited_sequence (Results 1 – 4 of 4) sorted by relevance

/Linux-v5.10/kernel/rcu/
Dtree_exp.h20 rcu_seq_start(&rcu_state.expedited_sequence); in rcu_exp_gp_seq_start()
29 return rcu_seq_endval(&rcu_state.expedited_sequence); in rcu_exp_gp_seq_endval()
37 rcu_seq_end(&rcu_state.expedited_sequence); in rcu_exp_gp_seq_end()
51 s = rcu_seq_snap(&rcu_state.expedited_sequence); in rcu_exp_gp_seq_snap()
63 return rcu_seq_done(&rcu_state.expedited_sequence, s); in rcu_exp_gp_seq_done()
544 jiffies - jiffies_start, rcu_state.expedited_sequence, in synchronize_rcu_expedited_wait()
Dtree.h327 unsigned long expedited_sequence; /* Take a ticket. */ member
Dtree.c583 return rcu_state.expedited_sequence; in rcu_exp_batches_completed()
/Linux-v5.10/Documentation/RCU/Design/Expedited-Grace-Periods/
DExpedited-Grace-Periods.rst259 ``->expedited_sequence`` in the ``rcu_state`` structure. This counter
310 ``->expedited_sequence`` field is zero, so adding three and clearing the
352 initiates the grace period, which increments ``->expedited_sequence``.
367 ``->expedited_sequence``, acquires the ``->exp_wake_mutex`` and then
373 ``->expedited_sequence`` to the value three. If new tasks G and H arrive