From: Joel Fernandes <joel@joelfernandes.org>
To: Sebastian Andrzej Siewior <bigeasy@linutronix.de>
Cc: Peter Zijlstra <peterz@infradead.org>,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>,
Steven Rostedt <rostedt@goodmis.org>,
Will Deacon <will@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Paul E . McKenney" <paulmck@kernel.org>,
Linus Torvalds <torvalds@linux-foundation.org>,
Lai Jiangshan <jiangshanlai@gmail.com>,
Josh Triplett <josh@joshtriplett.org>,
Mathieu Desnoyers <mathieu.desnoyers@efficios.com>,
rcu@vger.kernel.org
Subject: Re: [PATCH 3/8] srcu: Use local_lock() for per-CPU struct srcu_data access
Date: Wed, 20 May 2020 14:59:57 -0400 [thread overview]
Message-ID: <20200520185957.GB261674@google.com> (raw)
In-Reply-To: <20200520182800.sdp6t6bgbhn4kkqk@linutronix.de>
On Wed, May 20, 2020 at 08:28:00PM +0200, Sebastian Andrzej Siewior wrote:
> On 2020-05-20 13:42:59 [-0400], Joel Fernandes wrote:
> > Hi Sebastian,
> Hi Joel,
>
> > For pointer stability, can we just use get_local_ptr() and put_local_ptr()
> > instead of adding an extra lock? This keeps the pointer stable while keeping
> > the section preemptible on -rt. And we already have a lock in rcu_data, I
> > prefer not to add another lock if possible.
>
> What is this get_local_ptr() doing? I can't find it anywhere…
I replied about it in the other thread.
> > > I remember Paul looked at that patch a few years ago and he said that
> > > that disabling interrupts here is important and matches the other part
> > > instance where the interrupts are disabled. Looking at it now, it seems
> > > that there is just pointer stability but I can't tell if
> > > rcu_segcblist_pend_cbs() needs more than just this.
> >
> > Which 'other part' are you referring to? Your patch removed local_irq_save()
> > from other places as well right?
>
> The patch converted hunks.
>
So then there are no other local_irq_save() to match with. Or may be I did
not understand your concern, could you share any threads from past
discussions about disabling interrupts in this code? You mentioned about a
discussion from few years ago.
> >
> > - Joel
> >
> > ---8<-----------------------
> >
> > diff --git a/kernel/rcu/srcutree.c b/kernel/rcu/srcutree.c
> > index 8ff71e5d0fe8b..5f49919205317 100644
> > --- a/kernel/rcu/srcutree.c
> > +++ b/kernel/rcu/srcutree.c
> > @@ -778,13 +778,17 @@ static bool srcu_might_be_idle(struct srcu_struct *ssp)
> > unsigned long tlast;
> >
> > /* If the local srcu_data structure has callbacks, not idle. */
> > - local_irq_save(flags);
> > - sdp = this_cpu_ptr(ssp->sda);
> > + sdp = get_local_ptr(ssp->sda);
> > + spin_lock_irqsave_rcu_node(sdp, flags);
>
> You acquire the node lock which was not acquired before. Is that okay?
> How is get_local_ptr() different to raw_cpu_ptr()?
get_cpu_ptr() disables preemption which you might not want, right?
Most (all?) other paths are accessing the cblist under lock so I added it
here to be safe. This is anyway called from a slowpath. Do you see a problem?
thanks,
- Joel
next prev parent reply other threads:[~2020-05-20 19:00 UTC|newest]
Thread overview: 48+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-19 20:19 [PATCH 0/8] Introduce local_lock() Sebastian Andrzej Siewior
2020-05-19 20:19 ` [PATCH 1/8] locking: " Sebastian Andrzej Siewior
2020-05-20 12:04 ` Peter Zijlstra
2020-05-22 11:05 ` Sebastian Andrzej Siewior
2020-05-22 13:01 ` Peter Zijlstra
2020-05-19 20:19 ` [PATCH 2/8] radix-tree: Use local_lock for protection Sebastian Andrzej Siewior
2020-05-19 20:45 ` Matthew Wilcox
2020-05-19 20:54 ` Steven Rostedt
2020-05-20 2:05 ` Matthew Wilcox
2020-05-20 10:13 ` Sebastian Andrzej Siewior
2020-05-20 10:21 ` Peter Zijlstra
2020-05-20 12:28 ` Thomas Gleixner
2020-05-19 20:19 ` [PATCH 3/8] srcu: Use local_lock() for per-CPU struct srcu_data access Sebastian Andrzej Siewior
2020-05-20 10:24 ` Peter Zijlstra
2020-05-20 12:06 ` Sebastian Andrzej Siewior
2020-05-20 13:27 ` Peter Zijlstra
2020-05-20 17:42 ` Joel Fernandes
2020-05-20 18:28 ` Sebastian Andrzej Siewior
2020-05-20 18:35 ` Peter Zijlstra
2020-05-20 18:44 ` Joel Fernandes
2020-05-20 18:50 ` Uladzislau Rezki
2020-05-20 18:59 ` Joel Fernandes [this message]
2020-05-20 18:43 ` Paul E. McKenney
2020-05-22 15:12 ` Sebastian Andrzej Siewior
2020-05-22 17:39 ` Paul E. McKenney
2020-05-23 15:08 ` Sebastian Andrzej Siewior
2020-05-23 16:59 ` Paul E. McKenney
2020-05-24 19:03 ` Sebastian Andrzej Siewior
2020-05-25 3:27 ` Paul E. McKenney
2020-05-26 13:41 ` [PATCH] srcu: Avoid local_irq_save() before acquiring spinlock_t Sebastian Andrzej Siewior
2020-05-26 16:16 ` Paul E. McKenney
2020-05-26 16:31 ` Sebastian Andrzej Siewior
2020-05-19 20:19 ` [PATCH 4/8] mm/swap: Use local_lock for protection Sebastian Andrzej Siewior
2020-05-19 23:58 ` Andrew Morton
2020-05-20 2:17 ` Matthew Wilcox
2020-05-20 10:53 ` Peter Zijlstra
2020-05-19 20:19 ` [PATCH 5/8] squashfs: make use of local lock in multi_cpu decompressor Sebastian Andrzej Siewior
2020-05-20 10:56 ` Peter Zijlstra
2020-05-19 20:19 ` [PATCH 6/8] connector/cn_proc: Protect send_msg() with a local lock Sebastian Andrzej Siewior
2020-05-20 11:03 ` Peter Zijlstra
2020-05-19 20:19 ` [PATCH 7/8] zram: Use local lock to protect per-CPU data Sebastian Andrzej Siewior
2020-05-20 11:07 ` Peter Zijlstra
2020-05-19 20:19 ` [PATCH 8/8] mm/zswap: " Sebastian Andrzej Siewior
2020-05-19 21:46 ` Song Bao Hua
2020-05-20 10:26 ` Sebastian Andrzej Siewior
2020-05-20 11:13 ` Song Bao Hua
2020-05-20 11:57 ` Sebastian Andrzej Siewior
2020-05-20 12:01 ` Song Bao Hua
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=20200520185957.GB261674@google.com \
--to=joel@joelfernandes.org \
--cc=bigeasy@linutronix.de \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=will@kernel.org \
/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).