From: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
To: Peter Zijlstra <peterz@infradead.org>
Cc: torvalds@linux-foundation.org, akpm@linux-foundation.org,
oleg@redhat.com, dhowells@redhat.com, willy@linux.intel.com,
tglx@linutronix.de, rostedt@goodmis.org, airlied@gmail.com,
maarten.lankhorst@canonical.com, walken@google.com,
linux-kernel@vger.kernel.org, Ingo Molnar <mingo@kernel.org>
Subject: Re: [RFC 0/8] Move locking primitives into kernel/locking/
Date: Wed, 6 Nov 2013 06:29:21 -0800 [thread overview]
Message-ID: <20131106142921.GJ18245@linux.vnet.ibm.com> (raw)
In-Reply-To: <20131105105244.666320103@infradead.org>
On Tue, Nov 05, 2013 at 01:10:44PM +0100, Peter Zijlstra wrote:
> Hi all,
>
> During Kernel Summit Dave mentioned that there wasn't a clear maintainer for
> locking bits.
>
> To remedy this Ingo suggested gathering all the various locking primitives and
> lockdep into a single place: kernel/locking/.
>
> I would further like to propose a MAINTAINERS entry like:
>
> LOCKING
> M: Ingo Molnar <mingo@redhat.com>
> M: Peter Zijlstra <peterz@infradead.org>
> M: Oleg Nesterov <oleg@redhat.com>
> M: "Paul E. McKenney" <paulmck@linux.vnet.ibm.com>
> M: Linus Torvalds <torvalds@linux-foundation.org>
> T: git git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git locking/core
> S: Maintained
> F: kernel/locking/
>
> Because for most 'fun' locking discussions we usually end up with at least
> those people anyway :-)
>
> Comments?
OK, I am in.
How are we organizing this? I could imagine divvying up the various
types of locks, having a minimum number of reviews or acks coupled
with a maximum review time, or just requiring the full set of reviews
and acks given the criticality of locking code. Other approaches?
Thanx, Paul
> ---
> kernel/lglock.c | 89
> kernel/lockdep.c | 4257 -----------------------------------
> kernel/lockdep_internals.h | 170 -
> kernel/lockdep_proc.c | 683 -----
> kernel/lockdep_states.h | 9
> kernel/mutex-debug.c | 110
> kernel/mutex-debug.h | 55
> kernel/mutex.c | 960 -------
> kernel/mutex.h | 48
> kernel/rtmutex-debug.c | 187 -
> kernel/rtmutex-debug.h | 33
> kernel/rtmutex-tester.c | 420 ---
> kernel/rtmutex.c | 1060 --------
> kernel/rtmutex.h | 26
> kernel/rtmutex_common.h | 126 -
> kernel/rwsem.c | 157 -
> kernel/semaphore.c | 263 --
> kernel/spinlock.c | 399 ---
> lib/percpu-rwsem.c | 165 -
> lib/rwsem-spinlock.c | 296 --
> lib/rwsem.c | 293 --
> lib/spinlock_debug.c | 302 --
> kernel/locking/Makefile | 25
> kernel/locking/lglock.c | 89
> kernel/locking/lockdep.c | 4257 +++++++++++++++++++++++++++++++++++
> kernel/locking/lockdep_internals.h | 170 +
> kernel/locking/lockdep_proc.c | 683 +++++
> kernel/locking/lockdep_states.h | 9
> kernel/locking/mutex-debug.c | 110
> kernel/locking/mutex-debug.h | 55
> kernel/locking/mutex.c | 960 +++++++
> kernel/locking/mutex.h | 48
> kernel/locking/percpu-rwsem.c | 165 +
> kernel/locking/rtmutex-debug.c | 187 +
> kernel/locking/rtmutex-debug.h | 33
> kernel/locking/rtmutex-tester.c | 420 +++
> kernel/locking/rtmutex.c | 1060 ++++++++
> kernel/locking/rtmutex.h | 26
> kernel/locking/rtmutex_common.h | 126 +
> kernel/locking/rwsem-spinlock.c | 296 ++
> kernel/locking/rwsem-xadd.c | 293 ++
> kernel/locking/rwsem.c | 157 +
> kernel/locking/semaphore.c | 263 ++
> kernel/locking/spinlock.c | 399 +++
> kernel/locking/spinlock_debug.c | 302 ++
> kernel/Makefile | 22
> kernel/futex.c | 2
> lib/Makefile | 4
> 48 files changed, 10138 insertions(+), 10131 deletions(-)
>
>
>
next prev parent reply other threads:[~2013-11-06 14:29 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-05 12:10 [RFC 0/8] Move locking primitives into kernel/locking/ Peter Zijlstra
2013-11-05 12:10 ` [RFC 1/8] locking: Move mutex " Peter Zijlstra
2013-11-05 20:26 ` Michel Lespinasse
2013-11-05 21:20 ` Peter Zijlstra
2013-11-05 21:24 ` Michel Lespinasse
2013-11-06 5:40 ` Ingo Molnar
2013-11-06 11:36 ` Ingo Molnar
2013-11-05 12:10 ` [RFC 2/8] locking: Move lockdep " Peter Zijlstra
2013-11-05 12:10 ` [RFC 3/8] locking: Move spinlock " Peter Zijlstra
2013-11-05 12:10 ` [RFC 4/8] locking: Move semaphore " Peter Zijlstra
2013-11-05 12:10 ` [RFC 5/8] locking: Move rtmutex " Peter Zijlstra
2013-11-05 12:10 ` [RFC 6/8] locking: Move rwsem " Peter Zijlstra
2013-11-05 12:10 ` [RFC 7/8] locking: Move lglocks " Peter Zijlstra
2013-11-05 12:10 ` [RFC 8/8] locking: Move percpu-rwsem " Peter Zijlstra
2013-11-05 13:18 ` [RFC 0/8] Move locking primitives " Steven Rostedt
2013-11-05 13:21 ` Maarten Lankhorst
2013-11-05 14:12 ` Steven Rostedt
2013-11-05 13:26 ` Ingo Molnar
2013-11-05 14:13 ` Steven Rostedt
2013-11-05 19:38 ` Michel Lespinasse
2013-11-06 14:29 ` Paul E. McKenney [this message]
2013-11-08 7:37 ` Peter Zijlstra
2013-11-08 23:19 ` 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=20131106142921.GJ18245@linux.vnet.ibm.com \
--to=paulmck@linux.vnet.ibm.com \
--cc=airlied@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maarten.lankhorst@canonical.com \
--cc=mingo@kernel.org \
--cc=oleg@redhat.com \
--cc=peterz@infradead.org \
--cc=rostedt@goodmis.org \
--cc=tglx@linutronix.de \
--cc=torvalds@linux-foundation.org \
--cc=walken@google.com \
--cc=willy@linux.intel.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