Linearizable implementations do not suffice for randomized distributed computation
From MaRDI portal
Recommendations
Cited in
(27)- Wait-freedom is harder than lock-freedom under strong linearizability
- The correctness proof of Ben-Or's randomized consensus algorithm
- Randomized consensus with regular registers
- On atomic registers and randomized consensus in m\&m systems
- Strongly linearizable implementations, possibilities and impossibilities
- Sublogarithmic test-and-set against a weak adversary
- Tight bounds for asynchronous renaming
- Strongly Linearizable Implementations of Snapshots and Other Types
- Eventually linearizable shared objects
- Are shared objects composable under an oblivious adversary?
- Automata, Languages and Programming
- Brief Announcement: Intermediate Value Linearizability: A Quantitative Correctness Criterion
- Faster randomized consensus with an oblivious adversary
- The limits of helping in non-volatile memory data structures
- Intermediate value linearizability: a quantitative correctness criterion
- Quorum tree abstractions of consensus protocols
- On implementing SWMR registers from SWSR registers in systems with Byzantine failures
- Randomized mutual exclusion with sub-logarithmic RMR-complexity
- A wait-free queue with polylogarithmic step complexity
- Optimal resilience in systems that mix shared memory and message passing
- Preserving hyperproperties of programs using primitives with consensus number 2
- Faithful simulation of randomized BFT protocols on block DAGs
- Faster randomized repeated choice and DCAS
- Strongly linearizable LL/SC from CAS
- Strong linearizability using primitives with consensus number 2
- Fast and fair randomized wait-free locks
- Intermediate value linearizability: a quantitative correctness criterion
This page was built for publication: Linearizable implementations do not suffice for randomized distributed computation
Report a bug (only for logged in users!)Click here to report a bug for this page (MaRDI item Q5419107)