Brendon Costa

@herbsutter:Thanks for the clarification Herb. I thought that would be the case.

@ajasmin:One scenario I can think of is a very simple wait free "bounded" Single Producer Multi Consumer read-copy-update object (that doesn't handle overflows). I am sure there are many others.

Thanks for the talks. I appreciate all the help I can get trying to understand memory ordering

Is it strictly necessary that acquire/release "come in a pairs"? I have heard this a few times.

As an example, a single thread that uses a store/release to publish some data where multiple other threads that use a load/acquire to read that data. This is permitted right? I.e. One release can be "viewed" by many acquires or does it need to be strictly one-to-one?

Also, where would people suggest is a good place to ask questions and learn more about using atomics (and ask if others can help verify my reasoning)?

Thanks,
Brendon.