2015
DOI: 10.1007/978-3-319-14720-8_2
|View full text |Cite
|
Sign up to set email alerts
|

Liveness in Transactional Memory

Abstract: Despite the large amount of work on Transactional Memory (TM), little is known about how much liveness it could provide. This paper presents the first formal treatment of the question. We prove that no TM implementation can ensure local progress, the analogous of wait-freedom in the TM context, and we highlight different ways to circumvent the impossibility.

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

1
9
0

Year Published

2015
2015
2022
2022

Publication Types

Select...
5
1
1

Relationship

0
7

Authors

Journals

citations
Cited by 8 publications
(10 citation statements)
references
References 26 publications
1
9
0
Order By: Relevance
“…As for wait-freedom we adopt the definition adapted for TM that was introduced by Attiya et al [4]: a TM is wait-free [19] if any transaction executed by a non-faulty process eventually commits in a finite number of steps despite the behavior of concurrent transactions 2 . We consider processes to be non-parasitic, i.e., they eventually request the commit of every transaction that they start unless they crash or the transaction is aborted by the TM [9]. Hereafter, we refer to a read-only transaction that guarantees wait-freedom as WFRO; also, if such a read-only transaction also provides invisible reads, then we name it WFIRO (i.e., the union of WFRO and IRO).…”
Section: Configurations Events and Executionsmentioning
confidence: 99%
See 1 more Smart Citation
“…As for wait-freedom we adopt the definition adapted for TM that was introduced by Attiya et al [4]: a TM is wait-free [19] if any transaction executed by a non-faulty process eventually commits in a finite number of steps despite the behavior of concurrent transactions 2 . We consider processes to be non-parasitic, i.e., they eventually request the commit of every transaction that they start unless they crash or the transaction is aborted by the TM [9]. Hereafter, we refer to a read-only transaction that guarantees wait-freedom as WFRO; also, if such a read-only transaction also provides invisible reads, then we name it WFIRO (i.e., the union of WFRO and IRO).…”
Section: Configurations Events and Executionsmentioning
confidence: 99%
“…For a formal definition of the strongest progress condition specifically defined for (S)TM, i.e., local progress, the reader can refer to the work in[9].…”
mentioning
confidence: 99%
“…This is modeled via the UNPUSH rule and typically implemented via inverse operations (such as remove on an element that had been added). The UNPUSH rule is also needed in open nested transactions [30] and for ensuring liveness [3].…”
Section: The Push/pull Modelmentioning
confidence: 99%
“…This choice carves out a design space for implementations to take advantage of the full spectrum of possibilities (e.g. dependent transactions [32], open nested transactions [30], liveness [3]) and is relatively unrestrictive in terms of TM correctness criteria. However, despite expressive power, the model also gives the appropriate criteria to ensure serializability [31].…”
mentioning
confidence: 99%
“…The vision of pioneers is finally being materialized in the form of novel TM-enabled multicores like Intel Haswell [5] and IBM Blue Gene [6]. The emergence of these brand new TM-enabled multicores has been preceded with an intensive theoretical research on TM correctness [3], [4], liveness [7], and programming language level semantics [8], [9], [10], which seems to be culminating in what would be a theoretical foundation of contemporary TM-based systems. Looking from current prospective it seems that the main reason for the TM success are the two main advantages of TM over traditional locks.…”
Section: Introductionmentioning
confidence: 99%