From: Ingo Molnar <mingo@elte.hu>
To: Nick Piggin <nickpiggin@yahoo.com.au>
Cc: lkml <linux-kernel@vger.kernel.org>,
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: Re: [patch 04/19] mutex subsystem, add include/asm-i386/mutex.h
Date: Tue, 3 Jan 2006 16:21:17 +0100 [thread overview]
Message-ID: <20060103152117.GA2445@elte.hu> (raw)
In-Reply-To: <43BA7B2E.4070101@yahoo.com.au>
* Nick Piggin <nickpiggin@yahoo.com.au> wrote:
> >+#ifdef __HAVE_ARCH_CMPXCHG
> >+ if (likely(atomic_cmpxchg(count, 1, 0)) == 1)
> >+ return 1;
> >+ return 0;
> >+#else
> >+ return fail_fn(count);
> >+#endif
> >+}
>
> asm-i386 version I think really should just use atomic_cmpxchg
> unconditionally, because otherwise an i386 compatible kernel will not
> use cmpxchg even when running on 486+ (not sure how important that is
> these days, but still...).
yeah. This code predates the generic-atomic-cmpxchg code. (Feel free to
review all __HAVE_ARCH_CMPXCHG users after this goes in, and remove
__HAVE_ARCH_CMPXCHG altogether with a CONFIG_ flag.)
but ... the spinlock based variant is quite likely faster (on i386) than
generic-cmpxchg. Couldnt we introduce a new API, something along the
lines of:
atomic_cmpxchg_lock(&count, &lock->wait_lock);
and if the cmpxchg fails, it would hold the spinlock? The cmpxchg
semantics could be guaranteed by the spinlock. (because it is 'global'
for that particular critical section)
Ingo
next prev parent reply other threads:[~2006-01-03 15:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-03 10:07 [patch 04/19] mutex subsystem, add include/asm-i386/mutex.h Ingo Molnar
2006-01-03 13:25 ` Nick Piggin
2006-01-03 15:21 ` Ingo Molnar [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-03 16:46 Ingo Molnar
2006-01-02 16:33 Ingo Molnar, Arjan van de Ven
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=20060103152117.GA2445@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=nickpiggin@yahoo.com.au \
--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