Re: Difference between atomic operations and memory barriers

[Chris Friesen]

On 10/26/2009 12:22 PM, Leonidas . wrote:
> On Mon, Oct 26, 2009 at 11:49 PM, Noah Watkins <noah@xxxxxxxxxxxx> wrote:
>>> Trying to understand difference between atomic ops and memory barriers.
>>>
>> There is a bit of info in:
>>    Documentation/atomic_ops.txt

> Thanks for the pointer, there are no atomic operations for pointers, right?
> I guess barrier is what we need in that case.

You need barriers for the atomics too, at least in some cases.  From
that document:

*** WARNING: atomic_read() and atomic_set() DO NOT IMPLY BARRIERS! ***


For simple assignments, I'm fairly sure linux assumes that writes to
individual variables are atomic.  ie, if you're assigning to an int you
won't get half of the assignment completed while the other half isn't.

What the atomic ops buy you is the ability to do increment-and-test,
compare-and-exchange, etc. in an atomic fashion.

Barriers are needed to make sure that operations are visible on other
cpus in the correct order, and to ensure that the compiler doesn't
reorder the operations.

If you use the normal locking mechanisms (mutexes, spinlocks, etc.) the
barriers are implicit in the lock.

Chris
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/