From: "Zqiang" <qiang.zhang@linux.dev>
To: paulmck@kernel.org, "Joel Fernandes" <joelagnelf@nvidia.com>
Cc: frederic@kernel.org, neeraj.upadhyay@kernel.org,
boqun.feng@gmail.com, urezki@gmail.com, rcu@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] srcu/tiny: Remove preempt_disable/enable() in srcu_gp_start_if_needed()
Date: Thu, 11 Sep 2025 00:36:45 +0000 [thread overview]
Message-ID: <70fa9fd07e4fe2b1b498109f3450804e731fd7ce@linux.dev> (raw)
In-Reply-To: <e5e69dc3-ebd3-47ae-b193-bc4b2de36904@paulmck-laptop>
>
> On Wed, Sep 10, 2025 at 10:36:20AM -0400, Joel Fernandes wrote:
>
> >
> > [..]
> > > kernel/rcu/srcutiny.c | 4 +---
> > > 1 file changed, 1 insertion(+), 3 deletions(-)
> > >
> > > diff --git a/kernel/rcu/srcutiny.c b/kernel/rcu/srcutiny.c
> > > index b52ec45698e8..b2da188133fc 100644
> > > --- a/kernel/rcu/srcutiny.c
> > > +++ b/kernel/rcu/srcutiny.c
> > > @@ -181,10 +181,9 @@ static void srcu_gp_start_if_needed(struct srcu_struct *ssp)
> > > {
> > > unsigned long cookie;
> > >
> > > - preempt_disable(); // Needed for PREEMPT_LAZY
> > > + lockdep_assert_preemption_disabled();
> >
> > nit: Do we still want to keep the comment that the expectation of preemption
> > being disabled is for the LAZY case?
> >
> Good point, and I do believe that we do. Zqiang, any reason not to
> add this comment back in?
in rcu-tree, this commit:
(935147775c977 "EXP srcu: Enable Tiny SRCU On all CONFIG_SMP=n kernels")
make preempt disable needed for CONFIG_PREEMPT=y or CONFIG_PREEMPT_LAZY=y
when the CONFIG_SMP=n. do we need to replace "Needed for PREEMPT_LAZY"
comments with "Needed for PREEMPT or PREEMPT_LAZY"?
Thanks
Zqiang
>
> Thanx, Paul
>
> >
> > thanks,
> >
> > - Joel
> >
> >
> > > cookie = get_state_synchronize_srcu(ssp);
> > > if (ULONG_CMP_GE(READ_ONCE(ssp->srcu_idx_max), cookie)) {
> > > - preempt_enable();
> > > return;
> > > }
> > > WRITE_ONCE(ssp->srcu_idx_max, cookie);
> > > @@ -194,7 +193,6 @@ static void srcu_gp_start_if_needed(struct srcu_struct *ssp)
> > > else if (list_empty(&ssp->srcu_work.entry))
> > > list_add(&ssp->srcu_work.entry, &srcu_boot_list);
> > > }
> > > - preempt_enable();
> > > }
> > >
> > > /*
> > > --
> > > 2.48.1
> > >
> >
>
next prev parent reply other threads:[~2025-09-11 0:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 13:39 [PATCH v2] srcu/tiny: Remove preempt_disable/enable() in srcu_gp_start_if_needed() Zqiang
2025-09-10 13:55 ` Paul E. McKenney
2025-09-10 14:36 ` Joel Fernandes
2025-09-10 15:52 ` Paul E. McKenney
2025-09-11 0:36 ` Zqiang [this message]
2025-09-11 11:37 ` Paul E. McKenney
2025-09-11 11:46 ` Zqiang
2025-09-11 12:06 ` Paul E. McKenney
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=70fa9fd07e4fe2b1b498109f3450804e731fd7ce@linux.dev \
--to=qiang.zhang@linux.dev \
--cc=boqun.feng@gmail.com \
--cc=frederic@kernel.org \
--cc=joelagnelf@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=neeraj.upadhyay@kernel.org \
--cc=paulmck@kernel.org \
--cc=rcu@vger.kernel.org \
--cc=urezki@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).