Proceedings of the 7th ACM &Amp; IEEE International Conference on Embedded Software - EMSOFT '07 2007
DOI: 10.1145/1289927.1289970
|View full text |Cite
|
Sign up to set email alerts
|

Sirap

Abstract: This paper presents a protocol for resource sharing in a hierarchical real-time scheduling framework. Targeting realtime open systems, the protocol and the scheduling framework significantly reduce the efforts and errors associated with integrating multiple semi-independent subsystems on a single processor. Thus, our proposed techniques facilitate modern software development processes, where subsystems are developed by independent teams (or subcontractors) and at a later stage integrated into a single product.… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
3
0

Year Published

2008
2008
2023
2023

Publication Types

Select...
3
2
1

Relationship

0
6

Authors

Journals

citations
Cited by 87 publications
(3 citation statements)
references
References 26 publications
(40 reference statements)
0
3
0
Order By: Relevance
“…For instance, Lamastra et al 34 and De Niz et al 35 proposed budget inheritance mechanisms (also called proxy execution ) for uniprocessor systems, which allow the reservation managing a task blocked on a shared resource to inherit the budget of another reservation that is waiting for the same resource. This mechanism has been later extended to multiprocessor systems, for example, by Faggioli et al 36 Differently, the SIRAP 37 protocol performs a budget check every time a lock on a shared resource is requested: if the budget is enough to complete the critical section the lock is given to the requesting reservation, otherwise the access is granted only at the next budget replenishment. The BROE 38,39 protocol performs a similar budget check at each lock request, but, if the current budget is not enough to complete the execution of the critical section, the budget is replenished to the maximum value and the deadline is postponed proportionally.…”
Section: Related Workmentioning
confidence: 99%
“…For instance, Lamastra et al 34 and De Niz et al 35 proposed budget inheritance mechanisms (also called proxy execution ) for uniprocessor systems, which allow the reservation managing a task blocked on a shared resource to inherit the budget of another reservation that is waiting for the same resource. This mechanism has been later extended to multiprocessor systems, for example, by Faggioli et al 36 Differently, the SIRAP 37 protocol performs a budget check every time a lock on a shared resource is requested: if the budget is enough to complete the critical section the lock is given to the requesting reservation, otherwise the access is granted only at the next budget replenishment. The BROE 38,39 protocol performs a similar budget check at each lock request, but, if the current budget is not enough to complete the execution of the critical section, the budget is replenished to the maximum value and the deadline is postponed proportionally.…”
Section: Related Workmentioning
confidence: 99%
“…HSRP uses budget overrun and payback mechanisms to limit priority inversion. SIRAP (Subsystem Integration and Resource Allocation Policy) [98] uses the idea of self-blocking to bound delays on accessing shared resources without knowing the timing parameters of other subsystems. RRP (Rollback Resource Policy) [99] uses a rollback mechanism to avoid a lock-holding task to be blocked while holding a lock.…”
Section: Related Workmentioning
confidence: 99%
“…Specifically, multi-core synchronization mechanisms designed for non-hierarchical scheduling, such as MPCP [12,13] and MSRP [87], can lead to excessive blocking times due to the preemption and budget depletion of VCPUs, as discussed in Section 2.3.1. Available solutions in the uni-core hierarchical scheduling context [97,98,99] have not yet been extended to multi-core platforms. More importantly, in current virtualization solutions, the hypervisor is unaware of the executions of critical sections of tasks within VCPUs and there is no systematic mechanism to do so.…”
Section: Synchronization For Multi-core Virtual Machinesmentioning
confidence: 99%