From: Ingo Molnar <mingo@elte.hu>
To: Linus Torvalds <torvalds@osdl.org>
Cc: lkml <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@osdl.org>,
Arjan van de Ven <arjanv@infradead.org>,
Jes Sorensen <jes@trained-monkey.org>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Oleg Nesterov <oleg@tv-sign.ru>,
David Howells <dhowells@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Benjamin LaHaise <bcrl@kvack.org>,
Steven Rostedt <rostedt@goodmis.org>,
Christoph Hellwig <hch@infradead.org>, Andi Kleen <ak@suse.de>,
Russell King <rmk+lkml@arm.linux.org.uk>,
Nicolas Pitre <nico@cam.org>
Subject: [patch 0/8] mutex subsystem, ANNOUNCE
Date: Wed, 21 Dec 2005 16:54:11 +0100 [thread overview]
Message-ID: <20051221155411.GA7243@elte.hu> (raw)
this is the latest version of the mutex subsystem patch-queue. It
consists of the following patches:
xfs-mutex-namespace-collision-fix.patch
add-atomic-xchg.patch
add-atomic-call-func-i386.patch
add-atomic-call-func-x86_64.patch
add-atomic-call-wrappers-rest.patch
mutex-core.patch
mutex-debug.patch
mutex-debug-more.patch
the patches are against Linus' latest tree, and were tested on i386,
x86_64 and ia64. [the tests were also done in DEBUG_MUTEX_FULL mode, to
make sure the code works fine. MUTEX_FULL support is not included in
this patchqueue].
The patches can also be downloaded from:
http://redhat.com/~mingo/generic-mutex-subsystem/
Changes since the previous version:
- dropped the semaphore-renaming and migration-helper patches. The
patches now contain only the pure mutex subsystem, nothing more.
- removed the fastpath dependency on __HAVE_ARCH_CMPXCHG: now every
architecture is able to use the generic mutex_lock/mutex_unlock
lockless fastpath. The quality of the fastpath is still as good as in
the previous version.
- added ARCH_IMPLEMENTS_MUTEX_FASTPATH for architectures that want to
hand-code their own fastpath. The mutex_lock_slowpath,
mutex_unlock_slowpath and mutex_lock_interruptible_slowpath global
functions can be used by such architectures in this case, and they
should implement the mutex_lock(), mutex_unlock() and
mutex_lock_interruptible() functions themselves. I have tested this
mechanism on x86. (but x86 wants to use the generic functions
otherwise, so those changes are not included in this patchqueue.)
- fixed the x86_64 register-clobber bug noticed by Zwane Mwaikambo
- XFS namespace collision fixes from Jes Sorensen
- lots of cleanups to "hide" the debugging code, it should now be much
less intrusive visually - kernel/mutex.c is now both smaller and
easier to read. There's no reduction in debugging functionality.
- cleaned up the debugging code
- unified all the externally visible debugging functions around the
mutex_debug_ prefix.
- added the proper atomic ops to every architecture - so in theory
mutexes should now work on every architectures. i386, x86_64 and ia64
was tested.
- created mutex-debug.h to hide some of the debugging details. Moved the
mm.h and sched.h debug-function declarations into this file.
- documentation updates
- eliminated the ->file, ->line debugging variant - __FUNCTION__ is good
enough and resulted in nicer code.
- properly check for held locks in kfree() too, if DEBUG.
- check for held-lock reinitialization via mutex_init(), if DEBUG.
- more micro-optimizations: eliminated an extra spinlock drop/reacquire
in the slowpath.
- dropped waiter->woken, profiles showed that it triggered very rarely.
- dropped the timeout/timer bits - nothing is using them right now, we
can add them back later.
- new mutex_trylock() optimization on architectures that support cmpxchg.
- marked ->name as const
- fixed typo: CONFIG_DEBUG_MUTEXESS -> CONFIG_DEBUG_MUTEXES
- mb() -> smp_mb() in mutex_is_locked()
- mutex_trylock doesnt need __sched
comments, fixes, bugreports are welcome,
Ingo
next reply other threads:[~2005-12-21 15:55 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-21 15:54 Ingo Molnar [this message]
2005-12-21 16:04 ` [patch 0/8] mutex subsystem, ANNOUNCE Arjan van de Ven
2005-12-21 18:07 ` Jes Sorensen
2005-12-22 2:36 ` Nick Piggin
2005-12-22 2:57 ` Nick Piggin
2005-12-22 7:19 ` Ingo Molnar
2005-12-22 7:56 ` Nick Piggin
2005-12-22 8:00 ` Arjan van de Ven
2005-12-22 8:10 ` Nick Piggin
2005-12-22 8:21 ` Arjan van de Ven
2005-12-22 8:32 ` Nick Piggin
2005-12-22 8:24 ` Ingo Molnar
2005-12-22 8:37 ` Nick Piggin
2005-12-21 22:43 ` Nicolas Pitre
2005-12-21 22:43 ` [patch 1/3] mutex subsystem: fix additions to the ARM atomic.h Nicolas Pitre
2005-12-21 22:44 ` [patch 2/3] mutex subsystem: add new atomic primitives Nicolas Pitre
2005-12-21 22:44 ` [patch 3/3] mutex subsystem: move the core to the new atomic helpers Nicolas Pitre
2005-12-21 23:12 ` Ingo Molnar
2005-12-22 1:16 ` Matt Mackall
2005-12-22 6:50 ` Nicolas Pitre
2005-12-22 6:51 ` [patch 2/5] mutex subsystem: add architecture specific mutex primitives Nicolas Pitre
2005-12-22 7:44 ` Nick Piggin
2005-12-22 8:03 ` Nick Piggin
2005-12-22 6:52 ` [patch 1/5] mutex subsystem: fix asm-arm/atomic.h Nicolas Pitre
2005-12-22 6:53 ` [patch 3/5] mutex subsystem: move the core to the new atomic helpers Nicolas Pitre
2005-12-22 6:53 ` [patch 4/5] mutex subsystem: allow architecture defined fast path for mutex_lock_interruptible Nicolas Pitre
2005-12-22 6:53 ` [patch 5/5] mutex subsystem: allow for the fast path to be inlined Nicolas Pitre
-- strict thread matches above, loose matches on Subject: below --
2005-12-21 22:36 [patch 0/8] mutex subsystem, ANNOUNCE Ingo Molnar
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=20051221155411.GA7243@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjanv@infradead.org \
--cc=bcrl@kvack.org \
--cc=dhowells@redhat.com \
--cc=hch@infradead.org \
--cc=jes@trained-monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nico@cam.org \
--cc=oleg@tv-sign.ru \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=rostedt@goodmis.org \
--cc=torvalds@osdl.org \
--cc=zwane@arm.linux.org.uk \
/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