290
Network-on-Chip
not feasible in Application Specific Integrated Circuit (ASIC) design environment. For ASIC-based NoCs, the suggested reconfigurations are as
follows:
1. Local reconfiguration of core attachments to neighboring routers
(Soumya et al. 2013). Multiplexers are introduced to change the
attachments of cores to different routers for different applications.
2. Topology reconfiguration (Modarressi et al. 2011) via topology
switches to evolve application-specific topologies for individual
applications.
3. Router wrapper design (Stensgaard et al. 2008) to effect
reconfiguration.
4. Link reconfiguration (Lan et al. 2011) to change directions of links
connecting any two routers, based on traffic load in each direction.
In this chapter, these strategies will be discussed. However, to start with,
Section 10.2 performs a brief review of the literature in the domain of reconfigurable NoC design.
10.2 Literature Review
A ReNoC architecture has been presented in Stensgaard et al. (2008) which
enables the network topology to be configured by the application running
on the SoC by using topology switches. Core mapping mechanisms for
ReNoC architectures have been presented by Modarressi and SarbaziAzad (2007) and Modarressi et al. (2010, 2011), where reconfiguration is
achieved via programmable switches in the network. The reconfigurability allows NoC to dynamically tailor its topology to the traffic pattern of
different applications. Reconfigurable hybrid bus–network architecture
has been proposed by Avakian et al. (2010), where the number of processor cores attached to each bus is reconfigurable and is dependent on the
needs of the active processes and applications. Wu et al. (2011) proposed a
dynamic bypass circuit and north-last-weave routing algorithm to realize
dynamically reconfigurable ReNoCs. The network reconfigures itself for
different applications at runtime. OperaNP, a ReNoC-based platform, has
been proposed by Elmiligi et al. (2007) in which cores can be embedded
on an array of programmable logic blocks while the data routing is done
using another array of configurable routers. A topology allocation algorithm has been presented in Kunert et al. (2007) considering the demands
of different applications. It selects topology depending on the application
running on NoC. A hybrid-communication ReNoC (HCR-NoC) has been
Network-on-Chip
not feasible in Application Specific Integrated Circuit (ASIC) design environment. For ASIC-based NoCs, the suggested reconfigurations are as
follows:
1. Local reconfiguration of core attachments to neighboring routers
(Soumya et al. 2013). Multiplexers are introduced to change the
attachments of cores to different routers for different applications.
2. Topology reconfiguration (Modarressi et al. 2011) via topology
switches to evolve application-specific topologies for individual
applications.
3. Router wrapper design (Stensgaard et al. 2008) to effect
reconfiguration.
4. Link reconfiguration (Lan et al. 2011) to change directions of links
connecting any two routers, based on traffic load in each direction.
In this chapter, these strategies will be discussed. However, to start with,
Section 10.2 performs a brief review of the literature in the domain of reconfigurable NoC design.
10.2 Literature Review
A ReNoC architecture has been presented in Stensgaard et al. (2008) which
enables the network topology to be configured by the application running
on the SoC by using topology switches. Core mapping mechanisms for
ReNoC architectures have been presented by Modarressi and SarbaziAzad (2007) and Modarressi et al. (2010, 2011), where reconfiguration is
achieved via programmable switches in the network. The reconfigurability allows NoC to dynamically tailor its topology to the traffic pattern of
different applications. Reconfigurable hybrid bus–network architecture
has been proposed by Avakian et al. (2010), where the number of processor cores attached to each bus is reconfigurable and is dependent on the
needs of the active processes and applications. Wu et al. (2011) proposed a
dynamic bypass circuit and north-last-weave routing algorithm to realize
dynamically reconfigurable ReNoCs. The network reconfigures itself for
different applications at runtime. OperaNP, a ReNoC-based platform, has
been proposed by Elmiligi et al. (2007) in which cores can be embedded
on an array of programmable logic blocks while the data routing is done
using another array of configurable routers. A topology allocation algorithm has been presented in Kunert et al. (2007) considering the demands
of different applications. It selects topology depending on the application
running on NoC. A hybrid-communication ReNoC (HCR-NoC) has been