A Reliable Routing Architecture and Algorithm for Nocs

A Reliable Routing Architecture and Algorithm for Nocs

1 A Reliable Routing Architecture and Algorithm for NoCs Andrew DeOrio, Student Member, IEEE, David Fick, Student Member, IEEE, Valeria Bertacco, Member, IEEE, Dennis Sylvester, Fellow, IEEE, David Blaauw, Senior Member, IEEE, Jin Hu, Student Member, IEEE and Gregory Chen Member, IEEE Abstract—Aggressive transistor scaling continues to drive in- then direct traffic within the network, moving flits from source creasingly complex digital designs. The large number of tran- to destination according to the information encoded in each sistors available today enables the development of chip multi- packet, usually located in the header (first flit) of the packet. processors that include many cores on one die communicating through an on-chip interconnect. As the number of cores in- In particular, in wormhole routing [40], a single packet’s flits creases, scalable communication platforms, such as networks-on- may be spread across multiple routers as they traverse the chip (NoCs), have become more popular. However, as the sole network, until all the constituent flits are collected at the communication medium, these interconnects are a single point destination. Compared to bus-based systems, network-on-chip of failure, so that any permanent fault in the NoC can cause the designs have the advantage of allowing many messages in entire system to fail. Compounding the problem, transistors have become increasingly susceptible to wear-out related failures as flight simultaneously, thus providing efficient communication their critical dimensions shrink. As a result, the on-chip network among many nodes. has become a critically exposed unit that must be protected. While NoCs provide a scalable, distributed communication To this end, we present Vicis, a fault-tolerant architecture and solution, they are also a single point of failure in a chip companion routing protocol that is robust to a large number of multi-processor (CMP). Unlike the cores in a CMP, which are permanent failures, allowing communication to continue in the face of permanent transistor failures. Vicis makes use of a two- uniform, distributed, and therefore inherently redundant, there level approach. First, it attempts to work around errors within is only one communication medium in the chip, constituting a router by leveraging reconfigurable architectural components. a weakness in the presence of faults. Unreliable silicon sub- Second, when faults within a router disable a link’s connectivity, strates, brought on by aggressively scaled transistors, threaten or even an entire router, Vicis reroutes around the faulty the reliability of on-chip communication infrastructures, where node or link with a novel, distributed routing algorithm for meshes and tori. Tolerating permanent faults in both the router a single transistor failure in the NoC could cause the entire components and the reliability hardware itself, Vicis enables chip to fail [38]. The possibility of frequent failures in the graceful performance degradation of networks-on-chip.1 field is soon expected to become a reality [5], [55], leading to system failure [6], [18] or even causing security flaws [43]. Transistor failures can be caused by a variety of wear-out I. INTRODUCTION mechanisms in highly scaled technology nodes. As transistor Continuously shrinking transistor dimensions enable ever- dimensions approach the atomic scale, oxide breakdown [56] increasing density on modern microchips: each new technol- becomes a concern, since the gate oxide tends to become ogy node facilitates additional cores in chip multi-processors. less effective over time. Moreover, negative bias temperature For example, the Intel SCC [36] contains 48 cores, the Tilera instability (NBTI) [1] is of special concern in PMOS devices, Tile64 has 64 cores [2] and the experimental Intel Polaris where increased threshold voltage is observed over time. chip incorporates 80 cores [59]. However, bus communica- Additionally, thin wires are susceptible to electromigration tion and crossbar interconnects have not scaled efficiently: [19], because conductor material is gradually worn away high core counts necessitate efficient, scalable interconnects during chip operation until an open circuit occurs. Since these capable of providing communication among the processor mechanisms occur over time, traditional burn-in procedures cores. Networks-on-chip alleviate this problem with fast, scal- and manufacturing tests are ineffective in detecting them. able communication provided by small, distributed, packet- Fault Model. With the reality of decreasing transistor reliabil- switched routers [11]. ity and increasing failures, our goal is to mitigate permanent Network-on-chip routers communicate via a common inter- faults, those that affect the hardware for the remaining life connect, connecting processor cores, memory controllers, etc. of the chip. Thus, our fault model uses stuck-at failures at the At each node (usually a core or memory), a network interface hardware level to portray these permanent faults. Vicis’ goal is controller (NIC) connects the core to the local router, and ensure that all permanent faults in router datapath, and control converts messages from the core into data packets of varying logic are handled. Furthermore, any hardware additions may size for the network. These packets are further divided into be susceptible to the same faults that they aim to address: flits, the smallest unit of data traveling in the network, which faults may occur in the reliability hardware itself. dictates the width of a link connecting two routers. Routers Robust, architectural solutions are needed to mitigate the problem of permanent faults. When an error occurs in the 1Earlier versions of this work appeared in [15] and [16]. Included in field, a typical reliability solution will leverage a detection this paper are the following additional contributions: 1) a study on FIFO mechanism to identify the problem and notify the system unit reliability, 2) extended experimental results on larger networks and with additional workloads, including PARSEC benchmarks, 3) additional results of the failure (Figure 1). Detection can be achieved, for in- and in-depth presentation of the fault model, and 4) discussion of limitations. stance, with error correcting codes (ECC) [34] or custom NoC 2 Vicis’ focus Restricted location of faults. Other routing algorithms are Reconfig- Detection Diagnosis Recovery able to accommodate more faults, but restrict their location to uration specific types of “fault regions”. A fault region is a subnetwork notifies the determines modifies the recoups lost data of a restricted shape that contains faults, and oftentimes system that a fault the location NoC to work and resumes has occurred of the fault around the fault normal operation correctly functioning nodes must be disabled to satisfy the constraints of the region. The shape of fault regions may be Fig. 1. Steps in fault tolerance and Vicis’ focus. Vicis provides a novel convex [9], [60], or rectangular [58], and sometimes it is also diagnosis solution to determine the location of a permanent fault. It then restricted from including the network boundary [57]. Other leverages this information to reconfigure the system and overcome the failure. solutions require fault regions that are polygons [29], +, L or T shapes [7], or contain no holes [17], [48]. Finally, faults may be limited to datapath components, excluding control logic testing mechanisms [24], [26]. Next, the system undergoes [35], or to links and crossbars [30] diagnosis to determine the fault location. It can then enter a Unrestricted faults. A number of on-chip proposals tackle reconfiguration phase, isolating the failure or working around the problem of unconstrained faults. uLBDR [49] handles it. Finally, recovery can take place, recouping lost data with routing for any 2D-mesh topology without the need for routing mechanisms such as checkpointing [46], [54]. Following a tables. It adds logic to each input port, which facilitate completed recovery, normal system operation can resume. In routing around faulty links. However, this approach requires this paper, we focus on the diagnosis and reconfiguration virtual cut-though routing, requiring the entire packet to be phases, which are critical for a high-performance and fault- buffered at each router. Other solutions address permanent tolerant system, and we rely on solutions proposed in the faults by flooding the network to overcome lost network literature, such as those cited, for detection and recovery. connections, which incurs high performance overhead [45], Contributions. In this work, we present Vicis, a reliable [51]. Stochastic approaches [4], [53] provide tolerance to solution for networks-on-chip with mesh and torus topologies. permanent and transient faults by means of a probabilistic Vicis leverages a reconfigurable router architecture and routing broadcast mechanism. Immunet [47] routes packets adaptively algorithm. Our solution takes advantage of the redundancy towards their destinations, based on buffer availability. If inherent in on-chip networks through a two-level approach. necessary, packets switch to a reserved, escape, virtual channel First, it reconfigures individual routers with a novel and that guarantees that they will reach their destination and avoid flexible NoC router architecture. Second, when errors cannot faulty links. This channel is aware of the fault locations and be contained within a single router, Vicis invokes a novel routes deterministically in a ring through

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    14 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