Here is another article by Herb Sutter, known for his articles on concurrency, published on Dr. Dobb’s Journal on August 5th. An excerpt from the article:
“Given that lock-based synchronization has serious problems, it can be tempting to think lock-free code must be the answer. Sometimes that is true. In particular, it’s useful to have libraries provide hash tables and other handy types whose implementations are internally synchronized using lock-free techniques, such as Java’s ConcurrentHashMap, so that we can use those types safely from multiple threads without external synchronization and without having to understand the subtle lock-free implementation details. But replacing locks wholesale by writing your own lock-free code is not the answer. Lock-free code has two major drawbacks.”
2 responses so far ↓
1 Writing Lock-Free Code: A Corrected Queue // Sep 29, 2008 at 1:26 pm
[...] Sutter, known for his articles on concurrency, published an article on Lock-free code on August 5th. Herb continues his exploration of lock-free code–this time focusing on creating [...]
2 Writing a Generalized Concurrent Queue // Oct 29, 2008 at 12:15 pm
[...] Sutter, known for his articles on concurrency, published an article on Lock-free code on August 5th and another on creating a lock-free queue. Today Dr. Dobb’s Journal publishes [...]