2015
DOI: 10.1145/2858788.2688506
|View full text |Cite
|
Sign up to set email alerts
|

Software partitioning of hardware transactions

Abstract: Best-effort hardware transactional memory (HTM) allows complex operations to execute atomically and in parallel, so long as hardware buffers do not overflow, and conflicts are not encountered with concurrent operations. We describe a programming technique and compiler support to reduce both overflow and conflict rates by partitioning common operations into readmostly (planning) and write-mostly (completion) operations, which then execute separately. The completion operation remains transactional; planning can … Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
8
0

Year Published

2015
2015
2020
2020

Publication Types

Select...
2
2
2

Relationship

0
6

Authors

Journals

citations
Cited by 8 publications
(8 citation statements)
references
References 22 publications
0
8
0
Order By: Relevance
“…Partitioned Transactions (ParT) [19] also uses the same trend of splitting the operations into a traversal (called planning) phase and a commit (called update) phase, but it gives more general guidelines than OTB. Specifically, ParT does not restrict the planning phase to be a traversal of a data structure and it allows this phase to be any generic block of code.…”
Section: Optimistic Semantic Synchronizationmentioning
confidence: 99%
“…Partitioned Transactions (ParT) [19] also uses the same trend of splitting the operations into a traversal (called planning) phase and a commit (called update) phase, but it gives more general guidelines than OTB. Specifically, ParT does not restrict the planning phase to be a traversal of a data structure and it allows this phase to be any generic block of code.…”
Section: Optimistic Semantic Synchronizationmentioning
confidence: 99%
“…Recent work on reducing bookkeeping and conflict avoidance costs in STM includes techniques for exploiting hardware transactional memory [4,10,11,37,50]. These efforts focus on structuring transactions to reduce conflicts and minimize the transaction data footprint so they can run in hardware.…”
Section: Related Workmentioning
confidence: 99%
“…COP [17] and ParT [18] are generic methods for splitting large transactions in smaller fine-grained ones, and use RBT as a use case. They both employ an unsynchronized lookup phase followed by an HTM transaction that validates the lookup phase's outcome and updates the RBT.…”
Section: Related Workmentioning
confidence: 99%