All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ingo Molnar <mingo@elte.hu>
To: Christoph Hellwig <hch@infradead.org>,
	linux-kernel@vger.kernel.org, Linus Torvalds <torvalds@osdl.org>,
	Andrew Morton <akpm@osdl.org>,
	Arjan van de Ven <arjanv@infradead.org>,
	Steven Rostedt <rostedt@goodmis.org>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>, Andi Kleen <ak@suse.de>,
	David Howells <dhowells@redhat.com>,
	Alexander Viro <viro@ftp.linux.org.uk>,
	Oleg Nesterov <oleg@tv-sign.ru>, Paul Jackson <pj@sgi.com>
Subject: Re: [patch 10/15] Generic Mutex Subsystem, mutex-migration-helper-core.patch
Date: Tue, 20 Dec 2005 05:48:23 +0100	[thread overview]
Message-ID: <20051220044823.GA567@elte.hu> (raw)
In-Reply-To: <20051219150007.GA9809@infradead.org>


* Christoph Hellwig <hch@infradead.org> wrote:

> On Mon, Dec 19, 2005 at 02:38:37AM +0100, Ingo Molnar wrote:
> > 
> > introduce the mutex_debug type, and switch the semaphore APIs to it in a 
> > type-sensitive way. Plain semaphores will still use the proper 
> > arch-semaphore calls.
> 
> I think we shouldn't introduce this one.  It just encourages people to do
> really things.
        ^---("weird" ?)

ok. I can keep it a separate patch - it's needed for -rt, and it's also 
a good debugging tool to test-drive the mutex implementation.  

historically, i found 90% of the mutex.c bugs by stress-testing it from 
userspace, but a crutial 10% did come from the DEBUG_MUTEX_FULL mode, 
where almost all of the 7000+ semaphore users are switched over to 
mutexes.

but in terms of keeping the upstream kernel code base clean, i agree 
with a clean and separate set of mutex APIs that are introduced into 
subsystems gradually.

>  Everything else in the patchseries looks sensible to me.

great!

	Ingo

      parent reply	other threads:[~2005-12-20  4:49 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-19  1:38 [patch 10/15] Generic Mutex Subsystem, mutex-migration-helper-core.patch Ingo Molnar
2005-12-19 14:12 ` Steven Rostedt
2005-12-19 16:38   ` Ingo Molnar
2005-12-19 14:16 ` Steven Rostedt
2005-12-19 16:39   ` Ingo Molnar
2005-12-19 14:25 ` Steven Rostedt
2005-12-19 16:41   ` Ingo Molnar
2005-12-19 15:00 ` Christoph Hellwig
2005-12-19 15:35   ` Steven Rostedt
2005-12-20  4:48   ` Ingo Molnar [this message]

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=20051220044823.GA567@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=dhowells@redhat.com \
    --cc=hch@infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=oleg@tv-sign.ru \
    --cc=pj@sgi.com \
    --cc=rostedt@goodmis.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.