From: Nicolas Pitre <nico@cam.org>
To: Ingo Molnar <mingo@elte.hu>
Cc: lkml <linux-kernel@vger.kernel.org>,
Linus Torvalds <torvalds@osdl.org>, Andrew Morton <akpm@osdl.org>,
Arjan van de Ven <arjanv@infradead.org>,
Jes Sorensen <jes@trained-monkey.org>,
Zwane Mwaikambo <zwane@arm.linux.org.uk>,
Oleg Nesterov <oleg@tv-sign.ru>,
David Howells <dhowells@redhat.com>,
Alan Cox <alan@lxorguk.ukuu.org.uk>,
Benjamin LaHaise <bcrl@kvack.org>,
Steven Rostedt <rostedt@goodmis.org>,
Christoph Hellwig <hch@infradead.org>, Andi Kleen <ak@suse.de>,
Russell King <rmk+lkml@arm.linux.org.uk>
Subject: Re: [patch 0/8] mutex subsystem, -V6
Date: Thu, 22 Dec 2005 18:55:08 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0512221846470.26663@localhost.localdomain> (raw)
In-Reply-To: <20051222230438.GA13302@elte.hu>
On Fri, 23 Dec 2005, Ingo Molnar wrote:
> this release picks up Arjan's asm/mutex.h implementation, which adds
> asm-generic/mutex-dec.h, asm-generic/mutex-xchg.h for architectures to
> pick up. i386 and x86_64 use their own optimized version already, the
> other architectures default to mutex-xchg.h.
Great, this is in substance what I've been proposing for a while.
> Architectures specify the
> following functions:
>
> -------------------------------------------------------------------
> * __mutex_fastpath_unlock - try to promote the mutex from 0 to 1
> * @count: pointer of type atomic_t
> * @fn: function to call if the original value was not 1
> -------------------------------------------------------------------
The above should read "function to call if the original value was not 0".
> and __mutex_slowpath_needs_to_unlock(), to specify whether the fastpath
> has touched the count or not.
Note that, in most cases (but not necessarily all of them) the count is
always touched. It should rather be "has set the count to 1 or not" to
be precise..
> Nico, Christoph, does this approach work for you? Nico, you might want
> to try an ARM-specific mutex.h implementation.
Yes, I'm happy. And the ARM version will be sent your way soon.
Nicolas
next prev parent reply other threads:[~2005-12-22 23:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-22 23:04 Ingo Molnar
2005-12-22 23:55 ` Nicolas Pitre [this message]
2005-12-23 5:04 ` Nicolas Pitre
2005-12-23 8:09 ` Ingo Molnar
2005-12-23 4:59 ` Nicolas Pitre
2005-12-23 8:04 ` Ingo Molnar
2005-12-23 5:12 ` Nicolas Pitre
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=Pine.LNX.4.64.0512221846470.26663@localhost.localdomain \
--to=nico@cam.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=hch@infradead.org \
--cc=jes@trained-monkey.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mingo@elte.hu \
--cc=oleg@tv-sign.ru \
--cc=rmk+lkml@arm.linux.org.uk \
--cc=rostedt@goodmis.org \
--cc=torvalds@osdl.org \
--cc=zwane@arm.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®