public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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/19] mutex subsystem, -V10
Date: Mon, 2 Jan 2006 17:33:24 +0100	[thread overview]
Message-ID: <20060102163324.GA31501@elte.hu> (raw)

this is version -V10 of the generic mutex subsystem. It consists of the 
following 19 patches:

  add-atomic-xchg.patch
  add-function-typecheck.patch

  mutex-generic-asm-implementations.patch
  mutex-asm-mutex.h-i386.patch
  mutex-asm-mutex.h-x86_64.patch
  mutex-asm-mutex.h-arm.patch
  mutex-arch-mutex-h.patch
  mutex-core.patch

  mutex-docs.patch
  mutex-debug.patch
  mutex-debug-more.patch

  sem2mutex-xfs.patch
  sem2mutex-vfs-i-sem.patch
  sem2mutex-vfs-i-sem-more.patch
  sem2mutex-simple-ones.patch

  sem2completion-sx8.patch
  sem2completion-cpu5wdt.patch
  sem2completion-ide-gendev.patch
  sem2completion-loop.patch

the patches are against 2.6.15-rc7, and they should work fine on every 
Linux architecture. They can also be downloaded from:

  http://redhat.com/~mingo/generic-mutex-subsystem/

i have tested all 5 mutex implementation variants under MUTEX_DEBUG_FULL 
on x86: native, -dec, -xchg, -null and debug. I have also boot-tested 
x86_64 native mutexes.

Changes since -V9:

  136 files changed, 1172 insertions(+), 1041 deletions(-)

- function-typechecking cleanup (Chuck Ebbert)

- added "From:" attribution lines. (the S-o-b lines were OK.)

- added Arjan's mass conversion which converts simple semaphore users to 
  mutexes: all the use is within a single .c file, the semaphore was 
  declared static, and all down()+up() uses are within a single 
  function. These conditions were reviewed manually, and conversion was 
  generated automatically via a script.

- semaphore to completion: CPU3WDT (Steven Rostedt)
- semaphore to completion: SX8 (Steven Rostedt)
- semaphore to completion: IDE ->gendev_rel_sem (Aleksey Makarov)
- semaphore to completion: drivers/block/loop.c

- updates to Documentation/mutex-design.txt

- added __mutex_fastpath_lock_retval to asm-x86_64/mutex.h

- converted ipc/mqueue.c and security/inode.c to ->i_mutex

- more header file cleanups

	Ingo

             reply	other threads:[~2006-01-02 16:33 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-01-02 16:33 Ingo Molnar [this message]
2006-01-02 16:41 ` [patch 00/19] mutex subsystem, -V10 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=20060102163324.GA31501@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