From: Christoph Hellwig <hch@infradead.org>
To: Linus Torvalds <torvalds@osdl.org>
Cc: Ingo Molnar <mingo@elte.hu>, Andi Kleen <ak@suse.de>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.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>,
Christoph Hellwig <hch@infradead.org>,
David Howells <dhowells@redhat.com>,
Alexander Viro <viro@ftp.linux.org.uk>,
Oleg Nesterov <oleg@tv-sign.ru>,
Benjamin LaHaise <bcrl@kvack.org>
Subject: Re: [patch 00/15] Generic Mutex Subsystem
Date: Mon, 19 Dec 2005 23:37:54 +0000 [thread overview]
Message-ID: <20051219233754.GA20058@infradead.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0512191203120.4827@g5.osdl.org>
On Mon, Dec 19, 2005 at 12:12:26PM -0800, Linus Torvalds wrote:
> And don't get me wrong: if it's easier to just ignore the performance bug,
> and introduce a new "struct mutex" that just doesn't have it, I'm all for
> it. However, if so, I do NOT want to do the unnecessary renaming. "struct
> semaphore" should stay as "struct semaphore", and we should not affect old
> code in the _least_.
>
> Then code can switch to "struct mutex" if people want to. And if one
> reason for it ends up being that the code avoids a performance bug in the
> process, all the better ;)
>
> IOW, I really think this should be a series of small patches that don't
> touch old users of "struct semaphore" at all. None of this "semaphore" to
> "arch_semaphore" stuff, and the new "struct mutex" would not re-use _any_
> of the names that the old "struct semaphore" uses.
That's exactly what Ingo's series does if you ignore the two odd patches ;-)
next prev parent reply other threads:[~2005-12-19 23:38 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 1:34 [patch 00/15] Generic Mutex Subsystem Ingo Molnar
2005-12-19 4:22 ` Andi Kleen
2005-12-19 4:28 ` Steven Rostedt
2005-12-19 4:31 ` Andi Kleen
2005-12-19 6:24 ` Linus Torvalds
2005-12-19 12:56 ` Steven Rostedt
2005-12-19 16:55 ` Ingo Molnar
2005-12-19 15:50 ` Ingo Molnar
2005-12-19 19:11 ` Linus Torvalds
2005-12-19 19:25 ` Benjamin LaHaise
2005-12-19 19:55 ` Linus Torvalds
2005-12-21 16:42 ` Oleg Nesterov
2006-01-10 10:28 ` Balbir Singh
2006-01-10 18:03 ` Oleg Nesterov
2006-01-11 6:33 ` Balbir Singh
2006-01-11 9:22 ` Oleg Nesterov
2005-12-19 20:11 ` Ingo Molnar
2005-12-19 20:19 ` Benjamin LaHaise
2005-12-19 20:32 ` Russell King
2005-12-19 20:57 ` Ingo Molnar
2005-12-19 19:55 ` Ingo Molnar
2005-12-19 20:12 ` Linus Torvalds
2005-12-19 23:37 ` Christoph Hellwig [this message]
2005-12-20 8:03 ` Nick Piggin
2005-12-20 8:06 ` Arjan van de Ven
2005-12-20 8:21 ` Nick Piggin
2005-12-20 8:36 ` Arjan van de Ven
2005-12-20 8:48 ` Nick Piggin
2005-12-19 16:22 ` 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=20051219233754.GA20058@infradead.org \
--to=hch@infradead.org \
--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=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--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.