Proceedings of the 8th Annual IEEE/ACM International Symposium on Code Generation and Optimization 2010
DOI: 10.1145/1772954.1772970
|View full text |Cite
|
Sign up to set email alerts
|

An efficient software transactional memory using commit-time invalidation

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
36
0
1

Year Published

2010
2010
2017
2017

Publication Types

Select...
4
3
3

Relationship

0
10

Authors

Journals

citations
Cited by 36 publications
(40 citation statements)
references
References 26 publications
0
36
0
1
Order By: Relevance
“…STMs that use eager concurrency control for both reads and writes, including our Lark-TM, can guarantee not only livelock freedom but also starvation freedom, as long as they provide support for aborting either thread involved in a conflict (since this flexibility enables age-based contention management; Section 3.4) [23]. (An interesting related design is InvalSTM, which uses fully lazy concurrency control and allows a thread to abort another thread's transaction [22]. )…”
Section: Progress Guaranteesmentioning
confidence: 99%
“…STMs that use eager concurrency control for both reads and writes, including our Lark-TM, can guarantee not only livelock freedom but also starvation freedom, as long as they provide support for aborting either thread involved in a conflict (since this flexibility enables age-based contention management; Section 3.4) [23]. (An interesting related design is InvalSTM, which uses fully lazy concurrency control and allows a thread to abort another thread's transaction [22]. )…”
Section: Progress Guaranteesmentioning
confidence: 99%
“…Calciu et al present a novel hybrid transactional memory (HyTM), called Invyswell, that uses hardware transactions from Haswell's RTM in conjunction with software transactions from a heavily modified design of InvalSTM [22] , an STM designed to provide scalability and performance for large transactions with notable contention [20] . As our results show, Haswell's RTM performs best for small transactions with low contention, as it imposes no instrumentation overhead in fallback policies.…”
Section: Related Workmentioning
confidence: 99%
“…Before conducting further tests, it is necessary to test whether the proposed method is memory-intensive or not [16]. Here memory intensive means that the cheating detection process frequently occupies RAM, and insufficient free RAM would lead to aborted detection.…”
Section: B Memory-intensive Testmentioning
confidence: 99%