From: "Paul E. McKenney" <paulmck@linux.ibm.com>
To: rcu@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, 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 tip/core/rcu 0/4] RCU-sync updates for v5.3
Date: Thu, 30 May 2019 08:08:16 -0700 [thread overview]
Message-ID: <20190530150816.GA32130@linux.ibm.com> (raw)
Hello!
This series contains flavor-consolidation updates to RCU-sync:
1. Kill rcu_sync_type/gp_type, courtesy of Oleg Nesterov.
2. Use DEFINE_STATIC_PERCPU_RWSEM() to initialize dup_mmap_sem in
uprobes, courtesy of Oleg Nesterov.
3. Add DEFINE_PERCPU_RWSEM(), use it to initialize
cgroup_threadgroup_rwsem in percpu-rwsem, courtesy of Oleg Nesterov.
4. Simplify the state machine, courtesy of Oleg Nesterov.
Thanx, Paul
------------------------------------------------------------------------
include/linux/percpu-rwsem.h | 10 +
include/linux/rcu_sync.h | 40 ++-----
kernel/cgroup/cgroup.c | 3
kernel/events/uprobes.c | 4
kernel/locking/percpu-rwsem.c | 2
kernel/rcu/sync.c | 220 +++++++++++++++++++-----------------------
6 files changed, 121 insertions(+), 158 deletions(-)
next reply other threads:[~2019-05-30 15:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-30 15:08 Paul E. McKenney [this message]
2019-05-30 15:08 ` [PATCH tip/core/rcu 1/4] rcu/sync: Kill rcu_sync_type/gp_type Paul E. McKenney
2019-05-30 15:08 ` [PATCH tip/core/rcu 2/4] uprobes: Use DEFINE_STATIC_PERCPU_RWSEM() to initialize dup_mmap_sem Paul E. McKenney
2019-05-30 15:08 ` [PATCH tip/core/rcu 3/4] locking/percpu-rwsem: Add DEFINE_PERCPU_RWSEM(), use it to initialize cgroup_threadgroup_rwsem Paul E. McKenney
2019-05-30 15:08 ` [PATCH tip/core/rcu 4/4] rcu/sync: Simplify the state machine 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=20190530150816.GA32130@linux.ibm.com \
--to=paulmck@linux.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=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