2005
DOI: 10.1007/11561927_12
|View full text |Cite
|
Sign up to set email alerts
|

Restricted Stack Implementations

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
2

Citation Types

0
8
0

Year Published

2007
2007
2022
2022

Publication Types

Select...
4
1
1

Relationship

0
6

Authors

Journals

citations
Cited by 8 publications
(8 citation statements)
references
References 5 publications
0
8
0
Order By: Relevance
“…The exploration of consensus power 2 objects was initiated by Afek, Weisberger and Weisman in [3], where they defined the Common2 class of objects. Subsequently Common2 was shown to contain the stack object [2], various restricted versions of the FIFO queue [6-8, 16, 17], and the blurred history object [7]. In [3] Afek, Weisberger and Weisman sketched a wait-free swap implementation from 2-consensus objects, and the full construction appears in [21].…”
Section: Related Workmentioning
confidence: 99%
“…The exploration of consensus power 2 objects was initiated by Afek, Weisberger and Weisman in [3], where they defined the Common2 class of objects. Subsequently Common2 was shown to contain the stack object [2], various restricted versions of the FIFO queue [6-8, 16, 17], and the blurred history object [7]. In [3] Afek, Weisberger and Weisman sketched a wait-free swap implementation from 2-consensus objects, and the full construction appears in [21].…”
Section: Related Workmentioning
confidence: 99%
“…David et al [3] proposed another class of restricted stack implementations. Their implementation can support a maximum of two concurrent push operations.…”
Section: Related Workmentioning
confidence: 99%
“…Wait-free stacks have not received a lot of attention in the past, and we are not aware of algorithms that are particularly tailored to creating a generalized wait-free stack. However, approaches have been proposed to create wait-free stacks with certain restrictions [1], [3], [7], [8], and with universal constructions [10], [5]. The main reason that it has been difficult to create a wait-free stack is because there is a lot of contention at the stack top between concurrent push and pop operations.…”
Section: Introductionmentioning
confidence: 99%
See 1 more Smart Citation
“…The question whether queues belong to Common2 has been open for many years and has received a considerable amount of attention [2,4,5,6,8,14]. It essentially asks if there is an n-process linearizable wait-free implementation of a queue from Test&Set, for every n ≥ 3.…”
Section: Introductionmentioning
confidence: 99%