2013 IEEE 31st International Conference on Computer Design (ICCD) 2013
DOI: 10.1109/iccd.2013.6657018
|View full text |Cite
|
Sign up to set email alerts
|

Phoenix NoC: A distributed fault tolerant architecture

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
23
0

Year Published

2015
2015
2016
2016

Publication Types

Select...
4
1

Relationship

3
2

Authors

Journals

citations
Cited by 7 publications
(23 citation statements)
references
References 9 publications
0
23
0
Order By: Relevance
“…It comprises hardware part placed on each NoC router and software part (i.e. OsPhoenix) placed into the operating system of each PE [5], which is composed of a processormemory pair [4]. In addition, Phoenix NoC employs a direct 2D mesh topology consisting of routers using bidirectional links to connect with other routers and PEs.…”
Section: Phoenix Noc's Architecturementioning
confidence: 99%
See 1 more Smart Citation
“…It comprises hardware part placed on each NoC router and software part (i.e. OsPhoenix) placed into the operating system of each PE [5], which is composed of a processormemory pair [4]. In addition, Phoenix NoC employs a direct 2D mesh topology consisting of routers using bidirectional links to connect with other routers and PEs.…”
Section: Phoenix Noc's Architecturementioning
confidence: 99%
“…The main challenge of FPM design is how the threshold parameters have to be set for the correct detection of fault tendency and permanent faults. FPM is part of the fault-tolerant mechanism of Phoenix NoC [4], and each input link of NoC's router contains a FPM.…”
Section: Introductionmentioning
confidence: 99%
“…Moreover, in a given set of scenarios, some ones can cover others, reducing a large set of preprocessing scenarios, which provides two new and important contributions of this work: (i) a novel way to reduce a large set of scenarios based on cross-correlation measure to identify dissimilarities in sets of irregular matrix topologies, which enables to minimize the storage area of preprocessing scenarios; and (ii) a method to identify the most similar scenarios, and, consequently, the best scenario substitution, which enables to search fast and efficient routing solutions. Figure 1 shows the Phoenix distributed fault-tolerant architecture [5] over an NoC-based MPSoC platform comprising a hardware part (i.e. HwPhoenix) placed on each router of the NoC and a software part (i.e.…”
Section: Related Work and Main Contributionsmentioning
confidence: 99%
“…Examples of control packets are (i) TEST_LINKS used to test all links of the local router; (ii) TR_ROUT_TAB, RD_ROUT_TAB and WR_ROUT_TAB used to transmit, to read and to write the Routing Table of This work aggregates to the previous Phoenix architecture [5], the follow contributions: (i) fault detection and correction modules encompassed by a Hamming Encoder (HE) and a Hamming Decoder (HD); (ii) a fault diagnosis circuit named Fault Prediction Module (FPM); and (iii) the scenarios preprocessing capability, providing fast reconfiguration and deadlock-free routing in case of fault detection.…”
Section: Phoenix's Architecturementioning
confidence: 99%
See 1 more Smart Citation