Cluster based MPSoC architecture: an on-chip message passing implementation

Brillu, Romain; Pillement, Sébastien; Lemonnier, Fabrice; Millet, Philippe

doi:10.1007/s10617-014-9146-5

Cited by 2 publications

(2 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…5.3, SP7 sends to SP1 a set of messages with the task contents. After receiving all messages related to the task migration, SP1 notifies to all application tasks the new location of the migrated task (6). The task migration ends with SP1 notifying the MP h (CM0) the end of the migration process (7).…”

Section: Recovery Protocol Stepsmentioning

confidence: 99%

“…Large MCSoCs demand one or more dedicated Processing Element (PE) for management actions, as task mapping, task migration, power management (DVFS), QoS management, self-awareness adaptation, system monitoring (energy, temperature, deadlines). The management of a MCSoC may be centralized or hierarchically organized in clusters (Definition 1) [6,9]. Definition 1 Cluster-an MCSoC virtual region, with a set of PEs and one manager MPE.…”

Section: Introductionmentioning

confidence: 99%

See 1 more Smart Citation

System management recovery in NoC-based many-core systems

Silva

Caimi

Moraes

et al. 2020

Analog Integr Circ Sig Process

View full text Add to dashboard Cite

The technology nodes reduction enabled the emergence of NoC-based many-cores with dozens to hundreds of processing elements (PEs). Despite the processing power offered by a large number of processors and communication flexibility due to the adoption of NoCs, it is necessary to manage the many-core resources to ensure scalability. The execution of the management tasks requires a PE reserved exclusively to execute such actions. These processors are named managers PE-MPE. A centralized approach would induce a significant load to the MPE in large-scale systems, and a permanent fault in the MPE would compromise the entire system. The adoption of a distributed approach, organization adopted in this work, with MPEs hierarchically organized, reduces the management load, and a fault in an MPE would compromise only the PEs managed by the faulty MPE. The literature presents several fault-tolerant proposals targeting the NoC or the processors. However, there is a significant gap related to fault-tolerant methods at the system level, i.e., related to fault-tolerant techniques regarding the MPEs. The goal of this paper is to present a recovery method when an MPE became faulty, and propose a protocol to migrate the management software safely to a new PE. The method adopts task migration to release a processor if there is no processor to receive the kernel that was executing in a faulty processor. The proposal is transparent to the applications running in the many-core, with an overhead in the execution time varying between 1.5 and 1.65 ms during the management and task migration.

show abstract

Section: Recovery Protocol Stepsmentioning

confidence: 99%

Section: Introductionmentioning

confidence: 99%