OcNoC: Efficient One-Cycle Router Implementation for 3D Mesh Network-on-Chip

Ramon Fernandes, Lucas Brahm, Thais Webber, Rodrigo Cataldo, Letícia B. Poehls, César Marcon*

*Corresponding author for this work

Research output: Chapter in Book/Report/Conference proceedingConference contribution

Abstract

The overall system-on-chip performance depends on the network architecture, whose communication latency significantly impacts on the application performance. The challenge for on-chip networks is reducing costs while providing high performance such as low latency and high throughput. One alternative to achieve such goals is to implement efficient router architectures capable of fast packet switching and routing for parallel and scalable Networks-on-Chip (NoCs). We propose a single cycle router implementation for 3D Mesh NoCs with two arbitration approaches. Our evaluations show that the proposed one-cycle router can reduce network latency up to 57% and application latency up to 67%, when compared to multistage routers. This improvement comes with minimal silicon area overhead when compared to baseline router micro architecture, while still maintaining short critical paths.

Original languageEnglish
Title of host publication2015 28th International Conference On Vlsi Design (vlsid)
Pages105-110
Number of pages6
DOIs
Publication statusPublished - 4 Feb 2015
Event28th International Conference on VLSI Design, VLSID 2015 - held concurrently with the 14th International Conference on Embedded Systems - Bangalore, India
Duration: 3 Jan 20157 Jan 2015

Conference

Conference28th International Conference on VLSI Design, VLSID 2015 - held concurrently with the 14th International Conference on Embedded Systems
Country/TerritoryIndia
CityBangalore
Period3/01/157/01/15

Keywords

  • 3D mesh NoC
  • Arbitration
  • Area consumption
  • Latency
  • Routing
  • Throughput

Fingerprint

Dive into the research topics of 'OcNoC: Efficient One-Cycle Router Implementation for 3D Mesh Network-on-Chip'. Together they form a unique fingerprint.

Cite this