public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: linux-kernel@vger.kernel.org
Cc: mingo@kernel.org, jiangshanlai@gmail.com, dipankar@in.ibm.com,
	akpm@linux-foundation.org, mathieu.desnoyers@efficios.com,
	josh@joshtriplett.org, tglx@linutronix.de, peterz@infradead.org,
	rostedt@goodmis.org, dhowells@redhat.com, edumazet@google.com,
	fweisbec@gmail.com, oleg@redhat.com, joel@joelfernandes.org
Subject: [PATCH RFC tip/core/rcu 0/2] RCU consolidation patches
Date: Wed, 27 Jun 2018 13:48:35 -0700	[thread overview]
Message-ID: <20180627204835.GA25456@linux.vnet.ibm.com> (raw)

Hello!

This series is a sneak preview of a pair of patches that does the actual
consolidation of RCU-bh and RCU-sched functionality into RCU-preempt.
This does pass some light rcutorture testing, but left unattended will
no doubt do unspeakable things to your pets, your loved ones, and your
household devices.  Once fully debugged, this patch set will be followed
up with a cleanup series that actually removes RCU-bh and RCU-sched.
In the meantime:

1.	Make RCU-preempt treat disabling of interrupts, preemption,
	and/or softirq as read-side critical sections.	Most of the
	complexity deals with composite read-side critical sections in
	which sometimes preemption is disabled, other times there is an
	rcu_read_lock() in force, yet other times interrupts are disabled,
	and so on.

2.	Make the "rcu" torture type create composite read-side critical
	sections in order to test #1 above.

There is some faint hope of these going into the next merge window,
but it is far more likely that bug fixing will take longer than that,
pushing them into the merge window following the next one.  Furthermore,
without the cleanup patches, the actual goal of having only one flavor
of RCU is not met.  Besides, given the large number of patches already
slated for the next merge window, deferring any additional patches might
not be such a bad idea anyway.

							Thanx, Paul

------------------------------------------------------------------------

 Documentation/RCU/Design/Requirements/Requirements.html |   50 ++---
 include/linux/rcutiny.h                                 |    5 
 kernel/rcu/rcutorture.c                                 |    1 
 kernel/rcu/tree.c                                       |    9 +
 kernel/rcu/tree.h                                       |    3 
 kernel/rcu/tree_exp.h                                   |   71 ++++++--
 kernel/rcu/tree_plugin.h                                |  138 +++++++++++-----
 7 files changed, 200 insertions(+), 77 deletions(-)


             reply	other threads:[~2018-06-27 20:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-27 20:48 Paul E. McKenney [this message]
2018-06-27 20:49 ` [PATCH RFC tip/core/rcu 1/2] rcu: Defer reporting RCU-preempt quiescent states when disabled Paul E. McKenney
2018-07-01 17:40   ` Joel Fernandes
2018-07-01 22:25     ` Paul E. McKenney
2018-07-02  0:37       ` Joel Fernandes
2018-07-02  3:03         ` Paul E. McKenney
2018-07-01 18:38   ` Joel Fernandes
2018-07-01 22:27     ` Paul E. McKenney
2018-07-02  0:35       ` Joel Fernandes
2018-07-02  3:11         ` Paul E. McKenney
2018-07-02  4:49           ` Joel Fernandes
2018-07-02 13:02             ` Paul E. McKenney
2018-07-04  6:43   ` [lkp-robot] [rcu] e46874dd99: WARNING:suspicious_RCU_usage kernel test robot
2018-07-04 11:47     ` Paul E. McKenney
2018-06-27 20:49 ` [PATCH RFC tip/core/rcu 2/2] rcutorture: Handle extended "rcu" read-side critical sections 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=20180627204835.GA25456@linux.vnet.ibm.com \
    --to=paulmck@linux.vnet.ibm.com \
    --cc=akpm@linux-foundation.org \
    --cc=dhowells@redhat.com \
    --cc=dipankar@in.ibm.com \
    --cc=edumazet@google.com \
    --cc=fweisbec@gmail.com \
    --cc=jiangshanlai@gmail.com \
    --cc=joel@joelfernandes.org \
    --cc=josh@joshtriplett.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mathieu.desnoyers@efficios.com \
    --cc=mingo@kernel.org \
    --cc=oleg@redhat.com \
    --cc=peterz@infradead.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