Using the holidays for a 2-week coding session. Writing a new transactional memory manager that’s O(1) for all operations, completely non-blocking and progress-guaranteeing, and uses atomics only for writes.
-
-
I only care about the infrequently-contended case, as that’s the case transactions have the opportunity to parallelize gainfully. High contention makes transactions serialize, so better to just run that code single threaded.
-
That’s a sensible approach and the one I see most often in talks. I have to wonder if there’s something processor manufacturers can do to mitigate it more.
- 2 more replies
New conversation -
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.