2012 Design, Automation &Amp; Test in Europe Conference &Amp; Exhibition (DATE) 2012
DOI: 10.1109/date.2012.6176442
|View full text |Cite
|
Sign up to set email alerts
|

A divide and conquer based distributed run-time mapping methodology for many-core platforms

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
2
1

Citation Types

0
15
0
1

Year Published

2012
2012
2021
2021

Publication Types

Select...
4
3

Relationship

0
7

Authors

Journals

citations
Cited by 11 publications
(16 citation statements)
references
References 14 publications
0
15
0
1
Order By: Relevance
“…Al Faruque et al [1] present a distributed cluster oriented framework for homogeneous platforms which is based on agents for the task-to-cluster mapping. Anagnostopoulos et al [2] present a divide and conquer based distributed run-time mapping framework for both homogeneous and heterogeneous platforms with the introduction of a matching factor. In order to reduce the on-chip node intercommunication Cui et al [4] present a decentralized cluster-based scheme for task mapping, designed for reduction of the communication traffic between agents.…”
Section: Related Workmentioning
confidence: 99%
“…Al Faruque et al [1] present a distributed cluster oriented framework for homogeneous platforms which is based on agents for the task-to-cluster mapping. Anagnostopoulos et al [2] present a divide and conquer based distributed run-time mapping framework for both homogeneous and heterogeneous platforms with the introduction of a matching factor. In order to reduce the on-chip node intercommunication Cui et al [4] present a decentralized cluster-based scheme for task mapping, designed for reduction of the communication traffic between agents.…”
Section: Related Workmentioning
confidence: 99%
“…with smaller r and M D values. This leads to a higher chance of finding a feasible mapping (Section 5.2.1) along with a better mapping quality (Section 5.2.2) compared to related work [14,29,[33][34][35].…”
Section: Fault-aware Mappingmentioning
confidence: 85%
“…Afterwards, for each M ET task (tc), we collect the set of available accessible nodes ( N -line 9) which are in the first square around AM (r = 1) 3 and with the smallest Manhattan Distance (M D = 1) from parent of tc. Among the collected nodes, we select the one, if any, which keeps the mapping feasible to allocate to tc (lines [10][11][12][13][14][15]. MD increases once all M ET tasks are examined for feasible mappings while current radius, r, increases once all possible MD values are tried.…”
Section: Fault-aware Mappingmentioning
confidence: 99%
See 2 more Smart Citations