2016
DOI: 10.1515/itit-2016-0022
|View full text |Cite
|
Sign up to set email alerts
|

Providing fault tolerance through invasive computing

Abstract: As a consequence of technology scaling, today's complex multi-processor systems have become more and more susceptible to errors. In order to satisfy reliability requirements, such systems require methods to detect and tolerate errors. This entails two major challenges: (a) providing a comprehensive approach that ensures fault-tolerant execution of parallel applications across different types of resources, and (b) optimizing resource usage in the face of dynamic fault probabilities or with varying fault toleran… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1

Citation Types

0
3
0

Year Published

2016
2016
2019
2019

Publication Types

Select...
2
2
1

Relationship

2
3

Authors

Journals

citations
Cited by 5 publications
(3 citation statements)
references
References 0 publications
0
3
0
Order By: Relevance
“…Employed appropriately, this significantly improves resource utilization and hence efficiency. Furthermore, the capability to claim resources exclusively (such as processors, memory, and communication) allows to isolate applications and thus make multi‐core program execution predictable concerning non‐functional requirements such as execution time, 7 fault tolerance, 20 or power 21 …”
Section: Invasive Computingmentioning
confidence: 99%
“…Employed appropriately, this significantly improves resource utilization and hence efficiency. Furthermore, the capability to claim resources exclusively (such as processors, memory, and communication) allows to isolate applications and thus make multi‐core program execution predictable concerning non‐functional requirements such as execution time, 7 fault tolerance, 20 or power 21 …”
Section: Invasive Computingmentioning
confidence: 99%
“…Whereas, hard requirements must never be violated. Details on security and reliability requirements can be found in [9] and [15].…”
Section: Constraints and User Requirementsmentioning
confidence: 99%
“…Furthermore, hardware faults might occur more often thus making resources temporally or, due to manufacturing variability and aging, even permanently unavailable (cf. [13]), as detailed [15] (part this special issue). It is not possible to cope with these situations by static application mapping.…”
Section: Introductionmentioning
confidence: 99%