On Thu, Dec 26, 2013 at 2:23 PM, Carter Schonwald <carter.schonw...@gmail.com> wrote: > I'd be interested too. A good lock-free wait-free data structure is a > powerful abstraction in terms of the programmer's quality of life. > > Likewise, afaik, hardware lock Ellision is only a real win in the no / low > contention case. You still need to provide a code path to fall back on if > there's any contention.
Hardware transactional memory has a fallback case for when it fails to commit the transaction. Lock elision is a separate feature providing a subset of the functionality. It allows for speculative execution in the presence of locks by avoiding the cache synchronization the `cmpxchg` operation would cause if the work inside the lock scopes doesn't conflict. _______________________________________________ Rust-dev mailing list Rust-dev@mozilla.org https://mail.mozilla.org/listinfo/rust-dev
