2009 18th International Conference on Parallel Architectures and Compilation Techniques 2009
DOI: 10.1109/pact.2009.19
|View full text |Cite
|
Sign up to set email alerts
|

FASTM: A Log-based Hardware Transactional Memory with Fast Abort Recovery

Abstract: In this paper, we present FASTM, an eager log-based HTM that takes advantage of the processor's cache hierarchy to provide fast abort recovery. FASTM uses a novel coherence protocol to buffer the transactional modifications in the first level cache and to keep the non-speculative values in the higher levels of the memory hierarchy. This mechanism allows fast abort recovery of transactions that do not overflow the first level cache resources.Contrary to lazy HTM systems, committing transactions do not have to p… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
31
0

Year Published

2010
2010
2016
2016

Publication Types

Select...
5
3
1

Relationship

0
9

Authors

Journals

citations
Cited by 46 publications
(31 citation statements)
references
References 31 publications
0
31
0
Order By: Relevance
“…Lupon et al proposed FASTM [17] to minimize abort overhead of LogTM-SE by leaving old values in higher levels of the memory hierarchy and discarding new values that are stored in-place (pinned in L1 caches) in case of abort, behaving similar to a lazy version management scheme. However, FASTM has several differences with respect to our proposal: (1) it modifies the cache coherence protocol with the inclusion of an additional state, (2) an entry in the log must be added for every transactional store, even if the log is not used, (3) after abort recovery, data is not present in L1, making re-executed transactions slower, and (4) in case of transactional overflow of L1, the entire log must be restored.…”
Section: Related Workmentioning
confidence: 99%
“…Lupon et al proposed FASTM [17] to minimize abort overhead of LogTM-SE by leaving old values in higher levels of the memory hierarchy and discarding new values that are stored in-place (pinned in L1 caches) in case of abort, behaving similar to a lazy version management scheme. However, FASTM has several differences with respect to our proposal: (1) it modifies the cache coherence protocol with the inclusion of an additional state, (2) an entry in the log must be added for every transactional store, even if the log is not used, (3) after abort recovery, data is not present in L1, making re-executed transactions slower, and (4) in case of transactional overflow of L1, the entire log must be restored.…”
Section: Related Workmentioning
confidence: 99%
“…Bobba et al [1] present a discussion of pathogical cases encountered in eager and lazy designs. Subsequent optimizations like signature based LogTM and FASTM [10] improve upon buffering and abort handling capabilities by extending coherence protocols.…”
Section: Related Workmentioning
confidence: 99%
“…At the opposite end of the spectrum from STM is hardware transactional memory (HTM) [4,5,11,17,24,29]. HTM systems eliminate the need for software barriers by extending the processor or memory system to natively perform version management and conflict detection entirely in hardware, allowing them to demonstrate impressive performance.…”
Section: Htmmentioning
confidence: 99%