Re: [PATCH rcu 03/12] srcu: Renaming in preparation for additional reader flavor

2024-10-14 Thread Neeraj Upadhyay
On 10/14/2024 10:22 PM, Paul E. McKenney wrote: > On Mon, Oct 14, 2024 at 02:40:35PM +0530, Neeraj Upadhyay wrote: >> On 10/9/2024 11:37 PM, Paul E. McKenney wrote: >>> Currently, there are only two flavors of readers, normal and NMI-safe. >>> A number of fields, functions, and types reflect thi

Re: [PATCH rcu 03/12] srcu: Renaming in preparation for additional reader flavor

2024-10-14 Thread Paul E. McKenney
On Mon, Oct 14, 2024 at 02:40:35PM +0530, Neeraj Upadhyay wrote: > On 10/9/2024 11:37 PM, Paul E. McKenney wrote: > > Currently, there are only two flavors of readers, normal and NMI-safe. > > A number of fields, functions, and types reflect this restriction. > > This renaming-only commit prepares

Re: [PATCH rcu 03/12] srcu: Renaming in preparation for additional reader flavor

2024-10-14 Thread Neeraj Upadhyay
On 10/9/2024 11:37 PM, Paul E. McKenney wrote: > Currently, there are only two flavors of readers, normal and NMI-safe. > A number of fields, functions, and types reflect this restriction. > This renaming-only commit prepares for the addition of light-weight > (as in memory-barrier-free) readers.

[PATCH rcu 03/12] srcu: Renaming in preparation for additional reader flavor

2024-10-09 Thread Paul E. McKenney
Currently, there are only two flavors of readers, normal and NMI-safe. A number of fields, functions, and types reflect this restriction. This renaming-only commit prepares for the addition of light-weight (as in memory-barrier-free) readers. OK, OK, there is also a drive-by white-space fixeup! S