Opacity of Memory Management in Software Transactional Memory

08/13/2013
by   Holger Machens, et al.
0

Opacity of Transactional Memory is proposed to be established by incremental validation. Quiescence in terms of epoch-based memory reclamation is applied to deal with doomed transactions causing memory access violations. This method unfortunately involves increased memory consumption and does not cover reclamations outside of transactions. This paper introduces a different method which combines incremental validation with elements of sandboxing to solve these issues.

READ FULL TEXT

page 1

page 2

page 3

page 4

research
07/05/2019

On the Cost of Concurrency in Hybrid Transactional Memory

State-of-the-art software transactional memory (STM) implementations ach...
research
07/17/2020

Software Transactional Memory with Interactions

Software Transactional memory (STM) is an emerging abstraction for concu...
research
02/13/2019

Mesh: Compacting Memory Management for C/C++ Applications

Programs written in C/C++ can suffer from serious memory fragmentation, ...
research
01/14/2023

RMM: Reinforced Memory Management for Class-Incremental Learning

Class-Incremental Learning (CIL) [40] trains classifiers under a strict ...
research
01/31/2018

Incremental kernel PCA and the Nyström method

Incremental versions of batch algorithms are often desired, for increase...
research
07/19/2019

Optimizing Validation Phase of Hyperledger Fabric

Blockchain technologies are on the rise, and Hyperledger Fabric is one o...
research
01/12/2018

Safe Privatization in Transactional Memory

Transactional memory (TM) facilitates the development of concurrent appl...

Please sign up or login with your details

Forgot password? Click here to reset