Proceedings of the 28th ACM SIGPLAN Conference on Programming Language Design and Implementation 2007
DOI: 10.1145/1250734.1250744
|View full text |Cite
|
Sign up to set email alerts
|

Enforcing isolation and ordering in STM

Abstract: Transactional memory provides a new concurrency control mechanism that avoids many of the pitfalls of lock-based synchronization. High-performance software transactional memory (STM) implementations thus far provide weak atomicity: Accessing shared data both inside and outside a transaction can result in unexpected, implementation-dependent behavior. To guarantee isolation and consistent ordering in such a system, programmers are expected to enclose all shared-memory accesses inside transactions.A system that … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
116
0

Year Published

2008
2008
2018
2018

Publication Types

Select...
5
2
2

Relationship

0
9

Authors

Journals

citations
Cited by 137 publications
(121 citation statements)
references
References 68 publications
0
116
0
Order By: Relevance
“…However, strong atomicity is more difficult to implement in software transactional memory systems. Most software transactional memory proposals so far have only supported weak atomicity, but recent work, e.g., [13,91,6,2], show how some of these short-comings can be addressed.…”
Section: Strong and Weak Atomicitymentioning
confidence: 99%
See 1 more Smart Citation
“…However, strong atomicity is more difficult to implement in software transactional memory systems. Most software transactional memory proposals so far have only supported weak atomicity, but recent work, e.g., [13,91,6,2], show how some of these short-comings can be addressed.…”
Section: Strong and Weak Atomicitymentioning
confidence: 99%
“…One problem with software transactional memory systems only supporting weak atomicity (isolation) is the privatization problem [95,91,1]. The problem occurs when a thread makes some shared object(s) private for, e.g., performance reasons.…”
Section: Privatizationmentioning
confidence: 99%
“…It follows that war and waw dependencies are implicitly satisfied. In-place models [16,8,20] access (modify) directly the program state, while still enforcing the sequential semantics. Important differences with respect to serial commit models are that (i) all types of dependencies (raw, war and waw) may generate violations, but (ii) they are scalable -in number of processors that may contribute to speed-up, and (iii) allow a more flexible iteration-to-thread partitioning (threads may execute non-consecutive groups of iterations, see later).…”
Section: Software Tlsmentioning
confidence: 99%
“…Many possible semantics for TM have been proposed, including strong and weak isolation (also known as strong and weak atomicity) [1,17], single lock atomicity (SLA) [7], and approaches based on language memory models [4], linearizability [5,15], and operational semantics [12]. Of these, SLA has received the most attention.…”
Section: Introductionmentioning
confidence: 99%