Proceedings of the 23rd International Conference on Real Time and Networks Systems 2015
DOI: 10.1145/2834848.2834874
|View full text |Cite
|
Sign up to set email alerts
|

A contention-sensitive fine-grained locking protocol for multiprocessor real-time systems

Abstract: Prior work on multiprocessor real-time locking protocols has shown how to support fine-grained lock nesting with asymptotically optimal worst-case priority-inversion blocking (pi-blocking) bounds. However, contention for each resource has heretofore been considered an unconstrained variable. This paper presents the first fine-grained multiprocessor realtime locking protocol with contention-sensitive worst-case pi-blocking bounds. Contention-sensitive pi-blocking is made possible by incorporating knowledge of m… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
5
0

Year Published

2016
2016
2022
2022

Publication Types

Select...
4
2
2

Relationship

0
8

Authors

Journals

citations
Cited by 14 publications
(5 citation statements)
references
References 14 publications
0
5
0
Order By: Relevance
“…Dynamic group locks (DGLs) ( Ward and Anderson, 2013 ; Ward, 2016 ) are the multi-resource lock variant of RNLP, and reader–writer RNLP (R/W RNLP) ( Ward and Anderson, 2014 ) provides a reader–writer extension to DGL. With contention-sensitive RNLP (C-RNLP) ( Jarrett et al, 2015 ), there is also an extension to RNLP that relaxes the strict FIFO ordering and tries to dynamically eliminate transitive blocking chains . The RNLP family provides the tightest blocking bounds known in the real-time literature, proven to be asymptotically optimal.…”
Section: Setting the Requirements For Real-time Locking In Roboticsmentioning
confidence: 99%
See 1 more Smart Citation
“…Dynamic group locks (DGLs) ( Ward and Anderson, 2013 ; Ward, 2016 ) are the multi-resource lock variant of RNLP, and reader–writer RNLP (R/W RNLP) ( Ward and Anderson, 2014 ) provides a reader–writer extension to DGL. With contention-sensitive RNLP (C-RNLP) ( Jarrett et al, 2015 ), there is also an extension to RNLP that relaxes the strict FIFO ordering and tries to dynamically eliminate transitive blocking chains . The RNLP family provides the tightest blocking bounds known in the real-time literature, proven to be asymptotically optimal.…”
Section: Setting the Requirements For Real-time Locking In Roboticsmentioning
confidence: 99%
“…Conceptually, RNLP locks are always presented by using dedicated queues per resource in the literature ( Ward and Anderson, 2012 ; Ward and Anderson, 2013 ; Ward and Anderson, 2014 ; Ward, 2016 ). However, later work of the authors gives a hint to single-queue implementations of the non-reader–writer variants ( Jarrett et al, 2015 ). R/W RNLP cannot be implemented using a single queue, as its complex arbitration rules require multiple queues.…”
Section: Setting the Requirements For Real-time Locking In Roboticsmentioning
confidence: 99%
“…In 2015, Jarrett et al [117] introduced a contention-sensitive variant of the RNLP [201], denoted C-RNLP. In contrast to the original RNLP, and the vast majority of other protocols considered herein, the C-RNLP exploits knowledge of maximum critical section lengths at runtime to react dynamically to actual contention levels.…”
Section: Asymptotically Optimal Multiprocessor Real-time Lockingmentioning
confidence: 99%
“…In recent overhead-oriented work, Nemitz et al [158,160] added a fastpath to the RNLP [201] to optimize for the common case of non-nested lock acquisitions, and Afshar et al [10] presented an implementation of spin locks with flexible spin priorities [5]. Motivated by the fact that the contentionsensitive C-RNLP [117] exhibits relatively high acquisition and release overheads due to its complex request-sequencing rules, Nemitz et al [159] went a significant step further and introduced a novel and rather unconventional approach to implementing locking protocols. Specifically, Nemitz et al…”
Section: Rtos and Programming Language Integrationmentioning
confidence: 99%
“…Most of them are based on priority inheritance. In particular Jarrett et al [17] apply priority inheritance to multi-cores and propose a resource management protocol which bounds the access latency to a shared resource. Negrean et al [20] provide a method to compute the blocking time induced by concurrent tasks in order to determine their response time.…”
Section: Related Workmentioning
confidence: 99%