[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1264090331.31321.212.camel@gandalf.stny.rr.com>
Date: Thu, 21 Jan 2010 11:12:11 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Mathieu Desnoyers <mathieu.desnoyers@...ymtl.ca>
Cc: Peter Zijlstra <peterz@...radead.org>,
linux-kernel@...r.kernel.org,
"Paul E. McKenney" <paulmck@...ux.vnet.ibm.com>,
Oleg Nesterov <oleg@...hat.com>, Ingo Molnar <mingo@...e.hu>,
akpm@...ux-foundation.org, josh@...htriplett.org,
tglx@...utronix.de, Valdis.Kletnieks@...edu, dhowells@...hat.com,
laijs@...fujitsu.com, dipankar@...ibm.com
Subject: Re: [RFC PATCH] introduce sys_membarrier(): process-wide memory
barrier (v5)
On Thu, 2010-01-21 at 11:07 -0500, Mathieu Desnoyers wrote:
> * Peter Zijlstra (peterz@...radead.org) wrote:
> We can even create a generic fallback with the following kind of code in
> the meantime:
>
> static inline void spin_lock_mb(spinlock_t *lock)
> {
> spin_lock(&lock);
That would be spin_lock(lock);
> smp_mb();
> }
>
> static inline void spin_unlock_mb(spinlock_t *lock)
> {
> smp_mb();
> spin_unlock(&lock);
and spin_unlock(lock);
;-)
> }
>
> How does that sound ?
You may also need spin_lock_irqsave, et al. variants too.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists