Using local-spin k -exclusion algorithms to improve wait-free object implementations

We present the first shared-memory algorithms for k-exclusion in which all process blocking is achieved through the use of 'local-spin' busy waiting. Such algorithms are designed to reduce interconnect traffic, which is important for good performance. Our k-exclusion algorithms are starvat...

Full description

Saved in:
Bibliographic Details
Published inDistributed computing Vol. 11; no. 1; pp. 1 - 20
Main Authors Anderson, James H., Moir, Mark
Format Journal Article
LanguageEnglish
Published 08.12.1997
Online AccessGet full text
ISSN0178-2770
1432-0452
DOI10.1007/s004460050039

Cover

More Information
Summary:We present the first shared-memory algorithms for k-exclusion in which all process blocking is achieved through the use of 'local-spin' busy waiting. Such algorithms are designed to reduce interconnect traffic, which is important for good performance. Our k-exclusion algorithms are starvation-free, and are designed to be fast in the absence of contention, and to exhibit scalable performance as contention rises. In contrast, all previous starvation-free k-exclusion algorithms require unrealistic operations or generate excessive interconnect traffic under contention. We also show that efficient, starvation-free k-exclusion algorithms can be used to reduce the time and space overhead associated with existing wait-free shared object implementations, while still providing some resilience to delays and failures. The resulting 'hybrid' object implementations combine the advantages of local-spin spin locks, which perform well in the absence of process delays (caused, for example, by preemptions), and wait-free algorithms, which effectively tolerate such delays. We present performance results that confirm that this k-exclusion-based technique can improve the performance of existing wait-free shared object implementations. These results also show that lock-based implementations can be susceptible to severe performance degradation under multiprogramming, while our hybrid implementations are not.
Bibliography:ObjectType-Article-2
SourceType-Scholarly Journals-1
ObjectType-Feature-1
content type line 23
ISSN:0178-2770
1432-0452
DOI:10.1007/s004460050039