On Tue, Apr 22, 2025 at 06:56:17PM -0400, Joel Fernandes wrote:
>
>
> On 4/22/2025 6:55 PM, Joel Fernandes wrote:
> >
> >
> > On 4/22/2025 1:56 PM, Paul E. McKenney wrote:
> >> On Tue, Apr 22, 2025 at 07:38:30PM +0200, Uladzislau Rezki (Sony) wrote:
> >>> The SRCU read-side critical sections de
On 4/22/2025 6:55 PM, Joel Fernandes wrote:
>
>
> On 4/22/2025 1:56 PM, Paul E. McKenney wrote:
>> On Tue, Apr 22, 2025 at 07:38:30PM +0200, Uladzislau Rezki (Sony) wrote:
>>> The SRCU read-side critical sections describes the difference between
>>> srcu_down_read()/srcu_up_read() and srcu_rea
On 4/22/2025 1:56 PM, Paul E. McKenney wrote:
> On Tue, Apr 22, 2025 at 07:38:30PM +0200, Uladzislau Rezki (Sony) wrote:
>> The SRCU read-side critical sections describes the difference between
>> srcu_down_read()/srcu_up_read() and srcu_read_lock()/srcu_read_unlock()
>> in a way that a last pai
On Tue, Apr 22, 2025 at 07:38:30PM +0200, Uladzislau Rezki (Sony) wrote:
> The SRCU read-side critical sections describes the difference between
> srcu_down_read()/srcu_up_read() and srcu_read_lock()/srcu_read_unlock()
> in a way that a last pair must occur on the same CPU.
>
> This is not true, t
The SRCU read-side critical sections describes the difference between
srcu_down_read()/srcu_up_read() and srcu_read_lock()/srcu_read_unlock()
in a way that a last pair must occur on the same CPU.
This is not true, the srcu_read_unlock() can happen on any CPU, but it
must be performed by the same t
5 matches
Mail list logo
