2011
DOI: 10.1155/2011/561794
|View full text |Cite
|
Sign up to set email alerts
|

Optimizing Distributed Real-Time Embedded System Handling Dependence and Several Strict Periodicity Constraints

Abstract: This paper focuses on real-time nonpreemptive multiprocessor scheduling with precedence and strict periodicity constraints. Since this problem is NP-hard, there exist several approaches to resolve it. In addition, because of periodicity constraints our problem stands for a decision problem which consists in determining if, a solution exists or not. Therefore, the first criterion on which the proposed heuristic is evaluated is its schedulability. Then, the second criterion on which the proposed heuristic is eva… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
3
1
1

Citation Types

0
7
0

Year Published

2013
2013
2020
2020

Publication Types

Select...
3
1

Relationship

4
0

Authors

Journals

citations
Cited by 4 publications
(7 citation statements)
references
References 6 publications
0
7
0
Order By: Relevance
“…• The proposed nonpolynomial sufficient schedulability condition noticed NP_SSC: if( 13) ∧ ( 14) else (15). • The proposed polynomial sufficient schedulability condition noticed P_SSC: if( 13) ∧ (14) else (16).…”
Section: Schedulability Conditions Evaluationmentioning
confidence: 99%
See 1 more Smart Citation
“…• The proposed nonpolynomial sufficient schedulability condition noticed NP_SSC: if( 13) ∧ ( 14) else (15). • The proposed polynomial sufficient schedulability condition noticed P_SSC: if( 13) ∧ (14) else (16).…”
Section: Schedulability Conditions Evaluationmentioning
confidence: 99%
“…However, it turns out that strict periodicity is more constrained than the period constraint commonly taken into account which leads, generally, to an underutilization of the processor resources and an impractical schedulability analysis. 15 Therefore, it is quite conceivable to consider that only task input part necessitates the highest priority and, thus, is strictly periodic, while the remaining part of the task, including outputs, must rather run before a deadline. This way, as a strictly periodic part of the control task, input portion (shaded in red in Figure 1) is necessarily nonpreemptive whereas the remaining part of the task (shaded in blue in Figure 1) is a process that it may be preempted.…”
Section: Introductionmentioning
confidence: 99%
“…As periods are strict then siT0.3emTj, the start‐time of μiT0.3emTj, is given by siTTj=siTT0+j·TiTT where siT0.3emT0 is the start‐time of the first instance of μiT0.3emT. More details on strict periodicity may be found in .…”
Section: Model and Problem Formulationmentioning
confidence: 99%
“…Moreover, most of works cited before impose their own tasks scheduling, not necessarily, compliant with the one provided by the real-time operating system on which we aim to reduce the synchronization effects. Indeed, any scheduling algorithm applied on a real-time operating system can deal with one or several constraints [9] such temporal constraints, load balancing, , etc., and it is excluded to modify the resulting schedule otherwise constraints will not be met any more.…”
Section: Introductionmentioning
confidence: 99%
“…In a word, it automatically generates synchronized distributed executives from both application and target architecture description models. Some applications running under SynDEx are given in [9].…”
Section: Introductionmentioning
confidence: 99%