Proceedings Real-Time Systems Symposium
DOI: 10.1109/real.1997.641276
|View full text |Cite
|
Sign up to set email alerts
|

A novel approach to multiprogrammed multiprocessor synchronization for real-time kernels

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1

Citation Types

0
29
0

Publication Types

Select...
4
3
1

Relationship

0
8

Authors

Journals

citations
Cited by 20 publications
(29 citation statements)
references
References 10 publications
0
29
0
Order By: Relevance
“…FIFO spin locks are used to protected short resources while semaphores are adopted to protect long resources. SPEPP [26] and M-BWI [15], [19] apply the notion of a helping mechanism, where a waiting task can execute on behalf of the preempted resource holder. More recently, a protocol named RNLP [28], [27] has been developed to support nested resource requests by applying a token mechanism and a set of request satisfaction mechanisms that can fit into different system models.…”
Section: B Related Workmentioning
confidence: 99%
“…FIFO spin locks are used to protected short resources while semaphores are adopted to protect long resources. SPEPP [26] and M-BWI [15], [19] apply the notion of a helping mechanism, where a waiting task can execute on behalf of the preempted resource holder. More recently, a protocol named RNLP [28], [27] has been developed to support nested resource requests by applying a token mechanism and a set of request satisfaction mechanisms that can fit into different system models.…”
Section: B Related Workmentioning
confidence: 99%
“…Finally, several researchers have suggested operating system mechanisms that provide user applications with a limited degree of control over scheduling, allowing them to avoid [4,5,14,19,25] or recover from [1,2,31,33] inopportune preemption. Commercial support for such mechanisms, however, is neither universal nor consistent.…”
Section: Related Workmentioning
confidence: 99%
“…All work known to us on preemptable queue locks involves list-based locks [21,22]. This is probably due to the advantages listed in the previous paragraph that (nonpreemptable) list-based locks have over array-based ones.…”
Section: Implementing Objectsmentioning
confidence: 99%
“…In our approach, a task performs an operation on an object by first acquiring a lock; if a task is preempted before its operation is completed, then its operation is retried. In comparison to previous preemptable queue-lock algorithms [21,22], ours is quite simple. Its simplicity is mostly due to the fact that it was designed for systems satisfying the Preemption Axiom.…”
mentioning
confidence: 99%