From: Ingo Molnar <mingo@elte.hu>
To: lkml <linux-kernel@vger.kernel.org>
Cc: Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Arjan van de Ven <arjan@infradead.org>,
Nicolas Pitre <nico@cam.org>,
Jes Sorensen <jes@trained-monkey.org>,
Al Viro <viro@ftp.linux.org.uk>, Oleg Nesterov <oleg@tv-sign.ru>,
David Howells <dhowells@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Christoph Hellwig <hch@infradead.org>, Andi Kleen <ak@suse.de>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: [patch 00/21] mutex subsystem, -V15
Date: Thu, 5 Jan 2006 16:36:38 +0100 [thread overview]
Message-ID: <20060105153638.GA31013@elte.hu> (raw)
this is version 15 of the generic mutex subsystem, against v2.6.15.
The patch-queue consists of 21 patches, which can also be downloaded
from:
http://redhat.com/~mingo/generic-mutex-subsystem/
Changes since -V14:
5 files changed, 164 insertions(+), 191 deletions(-)
- micro-optimization #1: changed waiter->ti to be waiter->task, this
shaved off 2 more instructions from the slowpath. Suggested by David
Howells.
- micro-optimization #2: beware, this is evil black magic: i've enabled
architectures to do tail-merging of the slowpath if they want to, and
implemented this on x86. This shaves off another 3 instructions
from the slowpath, which can now directly branch into the slowpath
function, and the ret from there will bring us back to the call site.
The cost is that no other code but the fastpath must be put into
mutex_lock()/_unlock(). I have added big warnings to the affected
places. The non-assembly generic includes, nor the debugging code is
affected by this.
- reordered the API functions to be in likelyhood-of-use order:
mutex_lock()-fastpath, mutex_unlock()-fastpath,
mutex_lock()-slowpath, mutex_unlock()-slowpath,
mutex_lock_interruptible() fastpath/slowpath, mutex_trylock().
- cleanup: got rid of the intermediate __mutex_lock()/__mutex_unlock()
wrappers, they were unnecessary. Renamed the _noinline functions to
_slowpath - this is more descriptive.
Ingo
reply other threads:[~2006-01-05 15:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20060105153638.GA31013@elte.hu \
--to=mingo@elte.hu \
--cc=ak@suse.de \
--cc=akpm@osdl.org \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.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=torvalds@osdl.org \
--cc=viro@ftp.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
all inboxes | Powered by JetHome®