Proceedings of the Twentieth International Conference on Architectural Support for Programming Languages and Operating Systems 2015
DOI: 10.1145/2694344.2694359
|View full text |Cite
|
Sign up to set email alerts
|

Asynchronized Concurrency

Abstract: We introduce "asynchronized concurrency (ASCY)," a paradigm consisting of four complementary programming patterns. ASCY calls for the design of concurrent search data structures (CSDSs) to resemble that of their sequential counterparts. We argue that ASCY leads to implementations which are portably scalable: they scale across different types of hardware platforms, including single and multisocket ones, for various classes of workloads, such as readonly and read-write, and according to different performance met… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
9
0

Year Published

2016
2016
2022
2022

Publication Types

Select...
3
3
1

Relationship

0
7

Authors

Journals

citations
Cited by 83 publications
(9 citation statements)
references
References 37 publications
0
9
0
Order By: Relevance
“…We used a variant of EBR that uses clock vectors. In particular, we used ssmem, an EBR that accompanies the ASCYLIB algorithms [David et al 2015].…”
Section: Memory Managementmentioning
confidence: 99%
“…We used a variant of EBR that uses clock vectors. In particular, we used ssmem, an EBR that accompanies the ASCYLIB algorithms [David et al 2015].…”
Section: Memory Managementmentioning
confidence: 99%
“…For example, if a lock-free write is interrupted by the scheduler, it might need to retry the operation after being rescheduled if the shared state has changed. To protect against starvation, many indexes use non-blocking reads and blocking, lock-protected writes [4,16,48,53].…”
Section: Concurrency and Isolationmentioning
confidence: 99%
“…The design aims at addressing the cachecoherence problem by ensuring that each update to the hash table requires one cache line access in the common case. To ensure that a non-blocking reader finds the correct value, CLHT uses atomic snapshots of key-value pairs [16,18] Non-SMOs. CLHT installs any update to the hashtable by locking the appropriate bucket, performing the update inplace and then unlocking it.…”
Section: Trie: Height Optimized Trie (Hot)mentioning
confidence: 99%
See 2 more Smart Citations