Cost-Effective and Flexible Asynchronous Interconnect Technology for GALS Systems

Cost-Effective and Flexible Asynchronous Interconnect Technology for GALS Systems

GENERAL INTEREST Cost-Effective and Flexible Asynchronous Interconnect Technology for GALS Systems Davide Bertozzi, Gabriele Miorandi, and Alberto Ghiribaldi, University of Ferrara, Ferrara, 44122, Italy Wayne Burleson, University of Massachusetts Amherst, Amherst, MA, 01003, USA Greg Sadowski, Advanced Micro Devices, Inc., Boxborough, MA, 01719, USA Kshitij Bhardwaj, Weiwei Jiang, and Steven M. Nowick, Columbia University, New York, NY, 10027, USA In this article, a novel interconnect technology is presented for the cost-effective and flexible design of asynchronous networks-on-chip. It delivers asynchrony in heterogeneous system integration while yielding low-energy on-chip data movement. The approach consists of both a lightweight asynchronous switch architecture (using transition-signaling protocols and bundled-data encoding) and a complete synthesis flow built on top of mainstream industrial CAD tools. For the first time, this article demonstrates compelling area, performance and power benefits when compared to a recent commercial synchronous switch, and the ability of the tool flow to correctly instantiate a complete and competitive network topology. urrent computing architectures bear less islands of synchronicity that interact over a fully asyn- and less resemblance to the early multicore chronous interconnection network. Cprocessors. On the one hand, critical design Compared to synchronous counterparts, asyn- challenges are being tackled, ranging from the utili- chronous NoCs bring several potential advantages: zation wall and dark silicon issues1 to power/ther- mal management and reliability.2 On the other › No overhead of global clock distribution, tuning, hand, fundamental shifts from traditional von Neu- and management. 3 mann architectures are gaining traction. Among › No need for performance equalization within them, spiking neural-network-based neuromorphic individual unbalanced pipelines, and across 4,5 systems use biological inspiration and obtain different pipelines, in the network, leading to fi energy ef ciency by exploiting asynchronous event- aggregate system-level performance benefits. driven computation. › Support for optimized flit-level performance, From the system design viewpoint, the common tailored to the different timing paths that each challenge to the above trends consists of integrating a flit-type activates, unlike traditional worst-case fi large number of ne-grain computational units while clocked design. decoupling their operating mechanisms and conditions. This challenge motivates the recent surge of inter- However, despite their promise, two main barriers est, in industry and academia, in globally-asynchro- still prevent asynchronous NoCs from fulfilling modern nous locally-synchronous (GALS) architectures, and optimization, scaling and flexibility requirements, thus the design of asynchronous networks-on-chip (NoCs) limiting applicability. to support them.6 In a GALS system, cores are local First, the choice of communication protocols and data-encoding schemes in most state-of-the-art asyn- chronous NoCs aims to simplify hardware design (e.g., using four-phase, or “return-to-zero,” protocols) and to “ ß enforce extreme timing robustness (e.g., using delay- 0272-1732 2020 IEEE ” Digital Object Identifier 10.1109/MM.2020.3002790 insensitive data encoding), at the cost of low through- Date of publication 16 June 2020; date of current version put, high area occupancy, poor coding efficiency, and 20 January 2021. high energy-per-bit. January/February 2021 Published by the IEEE Computer Society IEEE Micro 69 Authorized licensed use limited to: Columbia University Libraries. Downloaded on January 28,2021 at 20:06:53 UTC from IEEE Xplore. Restrictions apply. GENERAL INTEREST ASYNCHRONOUS COMMUNICATION CHANNELS: PROTOCOLS AND DATA ENCODING synchronous components communicate via Alternative data-encoding schemes, such as single- A clockless handshaking, which involves defining rail bundled-data [see Figure S1(d)], use moderate timing both a handshaking protocol and a data-encoding constraints, while offering high coding efficiency and low scheme.1,2 energy-per-bit. This approach uses a standard There are two common handshaking protocols. synchronous-style single-rail data channel with binary Four-phase handshaking (“return-to-zero”) requires two data encoding. An extra request (“req”) wire is then round-trip communications per transaction [see Figure S1 “bundled” with the data, serving as a local strobe on (a)], but potentially leads to simpler hardware, since demand, whenever data are sent, along with a backwards signals return to a baseline value (i.e., 0) between acknowledgment (“ack”) wire. This scheme has the transactions. In contrast, in two-phase handshaking benefit of allowing the use of synchronous-style, i.e., (“non-return-to-zero,” or transition- signaling), each hazardous, computation blocks. Both four-phase and control signal makes a single toggle, with no return-to- two-phase protocols are common.1,2 For correct zero phase, incurring only one round-trip communication implementation, a single one-sided relative timing per transaction [see Figure S1(b)]. Hence, two-phase constraint (RTC) must be satisfied, that the req delay is protocols are preferred for high-performance circuits, always longer than worst case data transmission. This though they may lead to more complex hardware. A key bundling constraint is typically met by inserting a small challenge addressed by the current research is to employ matched delay on the control line, when needed.2 Unlike two-phase handshaking extensively in the NoC switch synchronous timing, however, such constraints are while retaining low hardware overhead. localized: there is no global timing constraint, and The most common data-encoding schemes are delay- unbalanced stages can correctly interact with their own insensitive (DI) codes and single-rail bundled data. DI matched delays. However, current commercial CAD codes support robust communication by explicitly tools offer poor support for these RTCs, since they target encoding both data validity and actual data values. Most min/max delay constraints with absolute timing only. common is dual-rail encoding [see Figure S1(c)], where each bit is encoded with two rails or wires. Independent REFERENCES of transmission time or relative bit skew, the receiver can 1. S. M. Nowick and M. Singh, “Asynchronous design - unambiguously identify when each bit is valid using a part 1: Overview and recent advances,” IEEE Des. completion detector. Overall, these codes provide great Test, vol. 32, no. 3, pp. 5–18, Jun. 2015. resilience to physical and operating variability. However, 2. S. M. Nowick and M. Singh, “High-performance fi most DI schemes have poor coding ef ciency and high asynchronous pipelines: An overview,” IEEE Des. Test energy-per-bit, due to their wiring overhead. Comput., vol. 28, no. 5, pp. 8–22, Sep./Oct. 2011. FIGURE S1. Asynchronous (a-b) handshaking protocols, and (c-d) data-encoding schemes. 70 IEEE Micro January/February 2021 Authorized licensed use limited to: Columbia University Libraries. Downloaded on January 28,2021 at 20:06:53 UTC from IEEE Xplore. Restrictions apply. GENERAL INTEREST ASYNCHRONOUS NOC ARCHITECTURES AND SYNTHESIS TOOL FLOWS ost asynchronous NoC architectures target are a few promising recent exceptions,7 but the early M highly robust design techniques to facilitate stage of the hierarchical tool flow for network synthesis timing closure, composability, and tolerance of physical prevents the bundled-data NoC from keeping up with and operational delay variations. These designs use performance expectations. The goal of our research is to delay-insensitive (DI) codes on data channels, and a overcome these overheads, in both switch design and so-called “quasi-delay-insensitive” (QDI) style for switch tool development. design—whose only timing assumption is that wire forks are “isochronic,” i.e., have roughly equal branches.1,2 While this approach provides ease-of-design, it typically REFERENCES comes at a significant cost in area and power, due to the 1. J. Bainbridge and S. Furber, “Chain: A delay-insensi- use of two wires per bit and return-to-zero protocols. As tive chip area interconnect,” IEEE Micro, vol. 22, an example, the first generation of a mainstream QDI – switch with DI channels, ANoC, reports a 25% energy- no. 5, pp. 16 23, Sep./ Oct. 2002. “ per-flit overhead and 80% greater area compared to a 2. A. Lines, Asynchronous interconnect for synchro- ” – synchronous counterpart.3 However, it still achieves nous SoC design, IEEE Micro, vol. 24, no. 1, pp. 32 41, significant savings in total network power (85%) on low- Jan./ Feb. 2004. traffic telecom benchmarks, due to its inherent 3. Y. Thonnart, P. Vivet, and F. Clermidy, “A fully-asyn- asynchronous ability to exploit sparse activity. chronous low-power framework for GALS NoC Alternatively, several single-rail bundled-data integration,” in Proc. ACM/IEEE Des., Autom. Test Eur. asynchronous NoCs have been proposed, which Conf., 2010, pp. 33–38. incorporate relative timing constraints (RTCs), and show 4. T. Bjerregaard and J. Sparsoe, “A router architec- promise in overall cost metrics: coding efficiency, area, ture for connection-oriented service guarantees in power, and performance.4,5,6,7 However, the the MANGO clockless network-on-chip,” in Proc. development of automated CAD flows for these NoCs is ACM/IEEE Des., Autom. Test Eur. Conf., 2005, pp. especially challenging. Commercial CAD tools typically 1226–1231. support only absolute

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    13 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us