2004
DOI: 10.1016/j.vlsi.2004.07.015
|View full text |Cite
|
Sign up to set email alerts
|

Issues in the development of a practical NoC: the Proteo concept

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1
1
1

Citation Types

0
17
0

Year Published

2006
2006
2021
2021

Publication Types

Select...
3
3
1

Relationship

0
7

Authors

Journals

citations
Cited by 33 publications
(17 citation statements)
references
References 12 publications
(10 reference statements)
0
17
0
Order By: Relevance
“…1 We assume that a deterministic routing function is utilized for routing packets, as most existing NoC architectures support only a deterministic routing function [9], [12], [13]. This is because the area-power overhead involved in adaptive routing is quite high.…”
Section: Problem Formulationmentioning
confidence: 99%
“…1 We assume that a deterministic routing function is utilized for routing packets, as most existing NoC architectures support only a deterministic routing function [9], [12], [13]. This is because the area-power overhead involved in adaptive routing is quite high.…”
Section: Problem Formulationmentioning
confidence: 99%
“…It uses very large packets (544 bytes) and buffers and, hence, requires large area. Proteo NoC also promises multiple topologies, however, currently it has been implemented only with ring topology [27]. The Proteo implementation reported in [20] also suffers from large buffering overhead due to store-and-forward routing.…”
Section: Related Workmentioning
confidence: 99%
“…Therefore, the latency is not affected notably. However, for the configurations resulting in higher latencies (configurations [12][13][14][15][16][17][18][19][20][21][22][23][24][25][26][27], the high priority offers great benefit. Regarding all configurations, high relative priority obtains 31% lower average latency and 41% lower maximum latency than the low priority.…”
Section: The Effect Of Network Parametersmentioning
confidence: 99%
“…In [8] a fully synchronous, pipelined NoC called ×pipes has been described, featuring wormhole switching with static routing tables and software tools for automatic instantiation of application specific NoCs. A similar NoC, called Proteo and developed in Tampere University of Technology, is introducing the Globally-Asynchronous Locally-Synchronous (GALS) approach [9] in order to solve the problem of the clock skew and delay. Finally, a NoC with Spatial Division Multiple Access has been introduced in [10], in contrast to the much more widely used TDMA technique.…”
Section: Introduction and Related Workmentioning
confidence: 99%