From: Ingo Molnar <mingo@elte.hu>
To: Andi Kleen <ak@suse.de>
Cc: 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>,
Christoph Hellwig <hch@infradead.org>,
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 09/15] Generic Mutex Subsystem, mutex-migration-helper-x86_64.patch
Date: Mon, 19 Dec 2005 17:34:41 +0100 [thread overview]
Message-ID: <20051219163441.GD8160@elte.hu> (raw)
In-Reply-To: <20051219043032.GH23384@wotan.suse.de>
* Andi Kleen <ak@suse.de> wrote:
> On Mon, Dec 19, 2005 at 02:38:27AM +0100, Ingo Molnar wrote:
> >
> > introduce the arch_semaphore type on x86_64, to ease migration to
> > mutexes.
>
> As a small feedback I don't think the name arch_semaphore is very good
> because it means nothing. How about counting_semaphore which is what
> it actually is?
yeah, this is one of the open issues, and i have no strong preference
for any of the naming variants. I considered two things when i went for
the 'arch_semaphore' name:
1) the name should be temporary, and we could make it 'struct semaphore'
once the transition phase is over. Linus is totally correct
suggesting that there's nothing wrong about the 'struct semaphore'
name. It just happens to clash with my intended type-based
categorization of 'known counting semaphores' from 'unknown
semaphores'.
2) i wanted to signal that this is the per-arch semaphore
implementation.
another candidate name was 'struct __semaphore'. I like 'struct
counting_semaphore' too, but maybe it's a bit too long as a name?
Anyway, i'm very much open to suggestions how to name it best.
Ingo
prev parent reply other threads:[~2005-12-19 16:35 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-19 1:38 [patch 09/15] Generic Mutex Subsystem, mutex-migration-helper-x86_64.patch Ingo Molnar
2005-12-19 4:30 ` Andi Kleen
2005-12-19 16:34 ` 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=20051219163441.GD8160@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox