Searched refs:srcu_ctrp (Results 1 – 2 of 2) sorted by relevance
106 struct srcu_ctr __percpu *srcu_ctrp; member180 .srcu_ctrp = &pcpu_name.srcu_ctrs[0], \292 struct srcu_ctr __percpu *scp = READ_ONCE(ssp->srcu_ctrp); in __srcu_read_lock_fast()336 struct srcu_ctr __percpu *scp = READ_ONCE(ssp->srcu_ctrp); in __srcu_read_lock_fast_updown()
225 ssp->srcu_ctrp = &ssp->sda->srcu_ctrs[0]; in init_srcu_struct_fields() 545 * the current ->srcu_ctrp but not yet have incremented its CPU's in srcu_readers_active_idx_check() 548 * ->srcu_ctrp and incrementing ->srcu_ctrs[idx].srcu_locks. And in srcu_readers_active_idx_check() 555 * updater has already flipped ->srcu_ctrp (possibly during in srcu_readers_active_idx_check() 560 * old ->srcu_ctrp value's ->srcu_ctrs[idx].srcu_locks counter, in srcu_readers_active_idx_check() 564 * the old value of ->srcu_ctrp and is just about to use that in srcu_readers_active_idx_check() 570 * ->srcu_ctrp, that task will be guaranteed to get the new index. in srcu_readers_active_idx_check() 573 * from ->srcu_ctrp in __srcu_read_lock() is before the smp_mb(). in srcu_readers_active_idx_check() 574 * Thus, that task might not see the new value of ->srcu_ctrp until in srcu_readers_active_idx_check() 577 * old value of ->srcu_ctrp twic in srcu_readers_active_idx_check() [all...]