On Jan 6, 2015, at 6:16 PM, George Bosilca <bosi...@icl.utk.edu> wrote:
> This is correct. We need the memory fences and atomic operations for shared > memory in all cases. When thread support is enabled we also need them in > various other places. However, this option also turns on the lock prefix for > the atomic operations, forcing them to always be atomic. I am not sure that > this has no unexpected side-effects on the code. Mmm. Is this right? Right now, the default is --enable-smp-locks. This enables the sm/vader BTLs to be correct. It also turns on some other required atomic magic which is necessary for correctness. If you use --disable-smp-locks, the sm/vader BTLs will be incorrect. Atomics won't necessarily be atomic, so they might/will be incorrect in multi-threaded scenarios. -- Jeff Squyres jsquy...@cisco.com For corporate legal information go to: http://www.cisco.com/web/about/doing_business/legal/cri/
