Re: [PATCH v2 05/12] rcutorture: Add tests for SRCU up/down reader primitives

On Tue, Apr 15, 2025 at 09:14:36PM -0400, Joel Fernandes wrote: > > > On 4/15/2025 5:15 PM, Paul E. McKenney wrote: > > On Tue, Apr 15, 2025 at 10:59:36AM -0700, Paul E. McKenney wrote: > >> On Tue, Apr 15, 2025 at 01:16:15PM -0400, Joel Fernandes wrote: > >>> > >>> > >>> On 3/31/2025 5:03 PM, Pa

Re: [PATCH v2 05/12] rcutorture: Add tests for SRCU up/down reader primitives

On Tue, Apr 15, 2025 at 10:59:36AM -0700, Paul E. McKenney wrote: > On Tue, Apr 15, 2025 at 01:16:15PM -0400, Joel Fernandes wrote: > > > > > > On 3/31/2025 5:03 PM, Paul E. McKenney wrote: > > > This commit adds a new rcutorture.n_up_down kernel boot parameter > > > that specifies the number of

Re: [PATCH v2 05/12] rcutorture: Add tests for SRCU up/down reader primitives

On Tue, Apr 15, 2025 at 01:16:15PM -0400, Joel Fernandes wrote: > > > On 3/31/2025 5:03 PM, Paul E. McKenney wrote: > > This commit adds a new rcutorture.n_up_down kernel boot parameter > > that specifies the number of outstanding SRCU up/down readers, which > > begin in kthread context and end i

Re: [PATCH v2 05/12] rcutorture: Add tests for SRCU up/down reader primitives

On 3/31/2025 5:03 PM, Paul E. McKenney wrote: > This commit adds a new rcutorture.n_up_down kernel boot parameter > that specifies the number of outstanding SRCU up/down readers, which > begin in kthread context and end in an hrtimer handler. There is a new > kthread ("rcu_torture_updown") that

[PATCH v2 05/12] rcutorture: Add tests for SRCU up/down reader primitives

This commit adds a new rcutorture.n_up_down kernel boot parameter that specifies the number of outstanding SRCU up/down readers, which begin in kthread context and end in an hrtimer handler. There is a new kthread ("rcu_torture_updown") that scans an per-reader array looking for elements whose rea