[lkml]   [2005]   [Dec]   [13]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: [PATCH 1/19] MUTEX: Introduce simple mutex implementation

* Ingo Molnar <> wrote:

> > Nick Piggin <> wrote:
> >
> > > We have atomic_cmpxchg. Can you use that for a sufficient generic
> > > implementation?
> >
> > No. CMPXCHG/CAS is not as available as XCHG, and it's also unnecessary.
> take a look at the PREEMPT_RT implementation of mutexes: it uses
> cmpxchg(), and thus both the down() and the up() fastpath is lockless!
> (And that is a mutex type that does alot more things, as it supports
> priority inheritance.)
> architectures which dont have cmpxchg can use a spinlock just fine.

the cost of a spinlock-based generic_cmpxchg could be significantly
reduced by adding a generic_cmpxchg() variant that also includes a
'spinlock pointer' parameter.

Architectures that do not have the instruction, can use the specified
spinlock to do the cmpxchg. This means that there wont be one single
global spinlock to emulate cmpxchg, but the mutex's own spinlock can be
used for it.

Architectures that have the cmpxchg instruction would simply ignore the
parameter, and would incur no overhead.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
More majordomo info at
Please read the FAQ at

 \ /
  Last update: 2005-12-13 11:37    [W:0.247 / U:0.020 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site