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

2025-04-08 Thread Paul E. McKenney
On Tue, Apr 08, 2025 at 06:05:19PM -0400, Joel Fernandes wrote: > > > On 4/8/2025 4:58 PM, Paul E. McKenney wrote: > > On Tue, Apr 08, 2025 at 08:18:05PM -, Joel Fernandes wrote: > >> Hello, Paul, > >> > >> On Tue, 8 Apr 2025 20:16:08 GMT, "Paul E. McKenney" wrote: > >>> This commit adds a ne

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

2025-04-08 Thread Joel Fernandes
Hello, Paul, On Tue, 8 Apr 2025 20:16:08 GMT, "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 ("r

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

2025-04-08 Thread Joel Fernandes
On 4/8/2025 4:58 PM, Paul E. McKenney wrote: > On Tue, Apr 08, 2025 at 08:18:05PM -, Joel Fernandes wrote: >> Hello, Paul, >> >> On Tue, 8 Apr 2025 20:16:08 GMT, "Paul E. McKenney" wrote: >>> This commit adds a new rcutorture.n_up_down kernel boot parameter >>> that specifies the number of o

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

2025-04-08 Thread Paul E. McKenney
On Tue, Apr 08, 2025 at 08:18:05PM -, Joel Fernandes wrote: > Hello, Paul, > > On Tue, 8 Apr 2025 20:16:08 GMT, "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