Proceedings of the 27th International Conference on Real-Time Networks and Systems 2019
DOI: 10.1145/3356401.3356410
|View full text |Cite
|
Sign up to set email alerts
|

Precise scheduling of mixed-criticality tasks by varying processor speed

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
13
0

Year Published

2020
2020
2023
2023

Publication Types

Select...
5
1
1

Relationship

2
5

Authors

Journals

citations
Cited by 26 publications
(13 citation statements)
references
References 24 publications
0
13
0
Order By: Relevance
“…In this subsection, we describe the RTA for our scheduling algorithm, which considers the following assumption: Assumption: We assume that the WCET and the processor speed has a linear relationship [13], i.e., if τ i starts executing on a processor (with C lo i ) with a degraded speed s lo , it will take C lo i /s lo time units to finish execution. Recall that under the lo-criticality mode, all the lo-and hi-criticality tasks execute at an energy-conserving speed, i.e., s lo .…”
Section: B Rta Of Our Algorithmmentioning
confidence: 99%
See 3 more Smart Citations
“…In this subsection, we describe the RTA for our scheduling algorithm, which considers the following assumption: Assumption: We assume that the WCET and the processor speed has a linear relationship [13], i.e., if τ i starts executing on a processor (with C lo i ) with a degraded speed s lo , it will take C lo i /s lo time units to finish execution. Recall that under the lo-criticality mode, all the lo-and hi-criticality tasks execute at an energy-conserving speed, i.e., s lo .…”
Section: B Rta Of Our Algorithmmentioning
confidence: 99%
“…All these papers assumed that all lo-criticality tasks are dropped after a modeswitch. The recent work in [13] proposed the technique to provide a full-service guarantee to all lo-criticality tasks (even after a mode switch) and most related to this work. However, it is also based on the pessimistic assumption that all the tasks will execute up to their WCET (at the corresponding system criticality level) and did not consider the probabilistic information to derive the lo-criticality execution time thresholds.…”
Section: Related Workmentioning
confidence: 99%
See 2 more Smart Citations
“…The criticism mainly arises from the impreciseness of the execution of less critical functionalities, as a result of their execution budget reduction in hi-mode. A recent paper [12] suggested a novel precise MC scheduling framework, where all tasks receive full execution budget under all circumstances. By following the MC-Fluid framework [6,28] and leveraging the dynamic voltage and frequency scaling (DVFS) technique, the processor execution speed is minimized under normal circumstances, while resumed to full speed when there is task overrun (characterized as a mode switch).…”
Section: Introductionmentioning
confidence: 99%