Skip to contentSkip to conversation

rcu_read_unlock() in the nestable rcu based on free-running counter

DISCUSSION Namhyung Kim 2 participants 3 messages Feb 10, 2015 – Feb 12, 2015

lore
Share & tools
lore
#0 lore raw

Hi,

It says "Interestingly enough, the implementation of rcu_read_unlock() is identical to that shown in Section 'RCU based on free-running counter'". However it seems not.. ;-)

Thanks,
Namhyung

#1 lore raw
Quoted 5 lines · Namhyung Kim

Hi,

It says "Interestingly enough, the implementation of rcu_read_unlock() is identical to that shown in Section 'RCU based on free-running counter'". However it seems not.. ;-)

Indeed! How about the following? (And good catch, by the way!)

Thanx, Paul

------------------------------------------------------------------------

Interestingly enough, despite their rcu_read_lock() differences, the implementation of rcu_read_unlock() is broadly similar to that shown in Section 9.3.5.7.

#2 lore raw

Hi Paul,

Quoted 9 lines · Paul E. McKenney
Quoted 5 lines · Namhyung Kim

Hi,

It says "Interestingly enough, the implementation of rcu_read_unlock() is identical to that shown in Section 'RCU based on free-running counter'". However it seems not.. ;-)

Indeed! How about the following? (And good catch, by the way!)

Quoted 7 lines

Thanx, Paul

------------------------------------------------------------------------

Interestingly enough, despite their rcu_read_lock() differences, the implementation of rcu_read_unlock() is broadly similar to that shown in Section 9.3.5.7.

Looks good to me!

Thanks,
Namhyung