From: Joel Fernandes <joel@joelfernandes.org>
To: Peter Zijlstra <peterz@infradead.org>
Cc: "Paul E. McKenney" <paulmck@kernel.org>,
rcu@vger.kernel.org, linux-kernel@vger.kernel.org,
kernel-team@fb.com, mingo@kernel.org, jiangshanlai@gmail.com,
akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
josh@joshtriplett.org, tglx@linutronix.de, rostedt@goodmis.org,
dhowells@redhat.com, edumazet@google.com, fweisbec@gmail.com,
oleg@redhat.com
Subject: Re: [PATCH tip/core/rcu 2/4] docs: Update RCU's hotplug requirements with a bit about design
Date: Tue, 10 Nov 2020 15:33:28 -0500 [thread overview]
Message-ID: <20201110203328.GA694269@google.com> (raw)
In-Reply-To: <20201109171433.GL2611@hirez.programming.kicks-ass.net>
On Mon, Nov 09, 2020 at 06:14:33PM +0100, Peter Zijlstra wrote:
> On Mon, Nov 09, 2020 at 08:24:52AM -0800, Paul E. McKenney wrote:
> > On Mon, Nov 09, 2020 at 01:23:17PM +0100, Peter Zijlstra wrote:
> > > On Thu, Nov 05, 2020 at 03:05:08PM -0800, paulmck@kernel.org wrote:
> > > > From: "Joel Fernandes (Google)" <joel@joelfernandes.org>
> > > >
> > > > The rcu_barrier() section of the "Hotplug CPU" section discusses
> > > > deadlocks, however the description of deadlocks other than those involving
> > > > rcu_barrier() is rather incomplete.
> > > >
> > > > This commit therefore continues the section by describing how RCU's
> > > > design handles CPU hotplug in a deadlock-free way.
> > > >
> > > > Signed-off-by: Joel Fernandes (Google) <joel@joelfernandes.org>
> > > > Signed-off-by: Paul E. McKenney <paulmck@kernel.org>
> > > > ---
> > > > .../RCU/Design/Requirements/Requirements.rst | 49 +++++++++++++++++-----
> > > > 1 file changed, 39 insertions(+), 10 deletions(-)
> > > >
> > > > diff --git a/Documentation/RCU/Design/Requirements/Requirements.rst b/Documentation/RCU/Design/Requirements/Requirements.rst
> > > > index 1ae79a1..98557fe 100644
> > > > --- a/Documentation/RCU/Design/Requirements/Requirements.rst
> > > > +++ b/Documentation/RCU/Design/Requirements/Requirements.rst
> > > > @@ -1929,16 +1929,45 @@ The Linux-kernel CPU-hotplug implementation has notifiers that are used
> > > > to allow the various kernel subsystems (including RCU) to respond
> > > > appropriately to a given CPU-hotplug operation. Most RCU operations may
> > > > be invoked from CPU-hotplug notifiers, including even synchronous
> > > > -grace-period operations such as ``synchronize_rcu()`` and
> > > > -``synchronize_rcu_expedited()``.
> > >
> > > I was under the impression that this rst crap now recognises func() and
> > > you no longer need to make the text unreadable with "``".
> >
> > It was there to start with, but good point. How about the commit
> > below?
>
> Much appreciated, thanks!
Thanks for making the change, I built it and it looks good in my web browser
;-).
BTW, these APIs are obsolete due to consolidation. Paul could you remove them
from the document?:
synchronize_rcu_bh(), synchronize_rcu_bh_expedited(), call_rcu_bh(),
rcu_barrier_bh().
thanks!
-Joel
next prev parent reply other threads:[~2020-11-10 20:33 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-05 23:04 [PATCH tip/core/rcu 0/4] Documentations updates for v5.11 Paul E. McKenney
2020-11-05 23:05 ` [PATCH tip/core/rcu 1/4] doc: Present the role of READ_ONCE() paulmck
2020-11-09 12:21 ` Peter Zijlstra
2020-11-09 16:20 ` Paul E. McKenney
2020-11-05 23:05 ` [PATCH tip/core/rcu 2/4] docs: Update RCU's hotplug requirements with a bit about design paulmck
2020-11-09 12:23 ` Peter Zijlstra
2020-11-09 16:24 ` Paul E. McKenney
2020-11-09 17:14 ` Peter Zijlstra
2020-11-10 20:33 ` Joel Fernandes [this message]
2020-11-11 0:20 ` Paul E. McKenney
2020-11-05 23:05 ` [PATCH tip/core/rcu 3/4] docs: RCU: Requirements.rst: Fix a list block paulmck
2020-11-05 23:05 ` [PATCH tip/core/rcu 4/4] docs/rcu: Update the call_rcu() API paulmck
2020-11-09 12:24 ` Peter Zijlstra
2020-11-10 1:20 ` Paul E. McKenney
2020-11-10 9:25 ` Peter Zijlstra
2020-11-10 14:37 ` 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=20201110203328.GA694269@google.com \
--to=joel@joelfernandes.org \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=edumazet@google.com \
--cc=fweisbec@gmail.com \
--cc=jiangshanlai@gmail.com \
--cc=josh@joshtriplett.org \
--cc=kernel-team@fb.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mathieu.desnoyers@efficios.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=paulmck@kernel.org \
--cc=peterz@infradead.org \
--cc=rcu@vger.kernel.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
/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).