Sequentially consistent versus linearizable counting networks

Marlos Mavronicolas, Michael Merritt, Gadi Taubenfeld

Research output: Contribution to conferencePaperpeer-review

Abstract

We compare the impact of timing conditions on implementing sequentially consistent and linearizable counters using counting networks in distributed systems. For counting problems in application domains which do not require linearizability but will run correctly if only sequential consistency is provided, the potential payoffs of our investigation are threefold: First, we show that sequential consistency and linearizability cannot be distinguished by the timing conditions previously considered in the context of counting networks, and thus in contexts in which these constraints apply, it is possible to rely on the stronger semantics of linearizability, which simplifies proofs and enhances compositionality. Second, we identify local timing conditions that support sequential consistency but not linearizability, and thus suggest weaker, easily implementable timing conditions that are likely to be sufficient in many applications. Third, we show that any kind of synchronization that is too weak to support even sequential consistency, may violate it significantly for some counting networks; hence, we identify timing conditions that are to be totally ruled out for specific applications that rely critically on either sequential consistency or linearizability.

Original languageEnglish
Pages133-142
Number of pages10
DOIs
StatePublished - 1999
Externally publishedYes
EventProceedings of the 1999 18th Annual ACM Symposium on Principles of Distributed Computing (PODC), FCRC'99 - Atlanta, GA, USA
Duration: 3 May 19996 May 1999

Conference

ConferenceProceedings of the 1999 18th Annual ACM Symposium on Principles of Distributed Computing (PODC), FCRC'99
CityAtlanta, GA, USA
Period3/05/996/05/99

Fingerprint

Dive into the research topics of 'Sequentially consistent versus linearizable counting networks'. Together they form a unique fingerprint.

Cite this