2018 IEEE 21st International Symposium on Real-Time Distributed Computing (ISORC) 2018
DOI: 10.1109/isorc.2018.00011
|View full text |Cite
|
Sign up to set email alerts
|

Mixed-Criticality Scheduling on Multiprocessors with Service Guarantees

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

0
11
0

Year Published

2019
2019
2023
2023

Publication Types

Select...
4
2
1

Relationship

1
6

Authors

Journals

citations
Cited by 10 publications
(11 citation statements)
references
References 16 publications
0
11
0
Order By: Relevance
“…Also as future work, we plan to revisit some mixedcriticality scheduling algorithms such as the ones in [13], [14], [15], [16] that have previously been proposed for addressing the non-survivability of traditional mixed-criticality scheduling algorithms. We will seek to characterize the robustness and resilience properties of these algorithms on the basis of the metrics that we have proposed in this paper.…”
Section: Discussionmentioning
confidence: 99%
See 1 more Smart Citation
“…Also as future work, we plan to revisit some mixedcriticality scheduling algorithms such as the ones in [13], [14], [15], [16] that have previously been proposed for addressing the non-survivability of traditional mixed-criticality scheduling algorithms. We will seek to characterize the robustness and resilience properties of these algorithms on the basis of the metrics that we have proposed in this paper.…”
Section: Discussionmentioning
confidence: 99%
“…Much of the criticism that has been directed at mixed-criticality scheduling theory that is based on the Vestal model can be traced to these poor survivability properties of the proposed algorithms. Some efforts have recently been made at designing mixed-criticality scheduling algorithms that exhibit some forms of survivability (see, for example [13], [14], [15], [16]); however, these are all ad hoc approaches towards incorporating some properties that are desirable from the perspective of survivability and do not attempt to formally define and quantify survivability -to our knowledge, Burns et al [17] represents a first effort at doing so. The focus in [17] is on defining task models that allow for the representation of robustness properties (in particular, HI-criticality tasks are defined as being robust to the dropping of individual jobs in the sense that the functionality of the task is not compromised upon such dropping, and algorithms are derived in [17] for scheduling systems comprising such tasks that judiciously select jobs to be dropped in order to not need to discard any LO-criticality tasks).…”
Section: Verification Versus Survivabilitymentioning
confidence: 99%
“…Although authors in [7] have proposed an approach to enhance the QoS by determining a constant drop rate parameter for LC tasks and guaranteeing their schedulability in the H I mode based on the defined parameter, their presented scheme has been analyzed in the worst-case scenario of tasks' execution, while there may exist significant amount of idle time in the processor at run-time, which could be used for improving the QoS of LC tasks. Some articles in the field of MC systems such as [14][15][16] have presented the scheduling algorithms for multi-core processors, which can also improve the LC tasks' QoS (row 2). However, these methods have been presented to guarantee the tasks' deadlines in the worst-case scenario at design-time.…”
Section: Related Workmentioning
confidence: 99%
“…In lines 7-11, the number of dropped LC tasks are counted to be used in the learning process. If the system switches back to the LO mode, a parameter (CountDrop) for each task, which counts the number of released LC tasks in the H I mode, is set to zero (lines [13][14]. Besides, there is a function (line 17) that checks whether the output of each task is ready.…”
Section: Liquid Approachmentioning
confidence: 99%
“…However, if this core also switches mode then these tasks will be suspended. This model has been previously published in [96].…”
Section: Schedulingmentioning
confidence: 99%