3 ms·
This is pretty cool. Is it done naively and using one global lock, or is it be more intelligent? Can GCC identify what memory location require locking for a giv
by CGamesPlay 15y ago
This is pretty cool. Is it done naively and using one global lock, or is it be more intelligent? Can GCC identify what memory location require locking for a given transaction, and lock just those? What is the granularity?
- roxtar 15y agoIt's smarter than a global lock (come on!). I would suggest reading the article which describes the implementation [1]. [1]: http://www.velox-project.eu/velox-transactional-memory-stack http://www.velox-project.eu/velox-transactional-memory-stack (courtesy scott_s)