3 ms·
This post could have its publishing year 2008 included in the HN title. Seven years later, we have some perspective on the author's prediction: "Indeed, like
by pavlov 12y ago
This post could have its publishing year 2008 included in the HN title.
Seven years later, we have some perspective on the author's prediction:
"Indeed, like an apparition from beyond the grave, the Intel 432 story should serve as a chilling warning to those working on transactional memory today."
Intel's transactional memory implementation TSX was famously broken in its initial incarnations in Haswell/Broadwell. [1]
[1] http://en.wikipedia.org/wiki/Transactional_Synchronization_Extensions http://en.wikipedia.org/wiki/Transactional_Synchronization_E...
- bcantrill 12y agoAnd a few months after that, the gloves really came off.[1] [1] http://dtrace.org/blogs/bmc/2008/11/03/concurrencys-shysters/ http://dtrace.org/blogs/bmc/2008/11/03/concurrencys-shysters...
- acqq 12y agoThanks! The link to the article in ACM Queue (October 24, 2008) which is a deadlink on that page at the noment is now: http://queue.acm.org/detail.cfm?id=1454462 http://queue.acm.org/detail.cfm?id=1454462 "Real-world Concurrency, Bryan Cantrill and Jeff Bonwick, Sun Microsystems" It's sad that ACM is not able to redirect their old links properly. The other article mentioned is probably: http://queue.acm.org/detail.cfm?id=1454466 http://queue.acm.org/detail.cfm?id=1454466 "Software Transactional Memory: Why is it only a Research Toy?" I'm actually searching for the analysis of the Intel's implementation.
- bcantrill 12y agoArgh -- my apologies for the dead links! I have updated all of them, with my apologies again for the apparent inability of the ACM to honor old links.
- willvarfar 12y ago(There is a distinction to be made between STM and HTM)