30.07.2015 Views

Actas JP2011 - Universidad de La Laguna

Actas JP2011 - Universidad de La Laguna

Actas JP2011 - Universidad de La Laguna

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

<strong>Actas</strong> XXII Jornadas <strong>de</strong> Paralelismo (<strong>JP2011</strong>) , <strong>La</strong> <strong>La</strong>guna, Tenerife, 7-9 septiembre 2011and focus the <strong>de</strong>scription of the mechanism and themapping tool. Then, we <strong>de</strong>scribe the LBDRx mechanismto cover practical topologies from SoC <strong>de</strong>signs.In Section III we <strong>de</strong>scribe the mapping tool. Finally,in Section IV we provi<strong>de</strong> evaluation results and conclu<strong>de</strong>the paper in Section V.II. LBDRx <strong>de</strong>scriptionThe <strong>de</strong>scription of the proposed LBDRx mechanismwill be presented as an evolution from the basicLBDR mechanism [8] previously proposed (withlow coverage for complex irregular topologies) to themost enhanced version (with full coverage to all thecomplex topologies analyzed).A. Preliminary: Basic I<strong>de</strong>aIn regular networks, e.g. a 2D-mesh network, theregular connectivity pattern is useful when <strong>de</strong>signingthe routing algorithm. In<strong>de</strong>ed, with the Dimension-Or<strong>de</strong>r routing (DOR), the implementation is quitestraightforward as messages are forwar<strong>de</strong>d with minimalpaths first in the X direction and then in theY direction. Thus, there is no need for a routing table,only a set of gates is enough. This ren<strong>de</strong>rs to anefficient implementation of the routing algorithm interms of area, power, and <strong>de</strong>lay.If we consi<strong>de</strong>r small irregularities on 2D-mesh networks,for instance due to manufacturing <strong>de</strong>fects,then the inherent irregularity complicates the routingimplementation. For instance, DOR is no longervalid as some paths are not possible now. However,other routing algorithms are still suitable for suchtopologies, for instance, topology-agnostic routingalgorithms like up*/down* [12]. Their implementationis usually performed with routing tables. Effortsto provi<strong>de</strong> efficient implementations of such algorithmsin those irregular topologies have been performedin the recent years.One important method is LBDR, which collapsesall the routing information required on every switchon a small set of bits, thus reducing significantly implementationcosts. LBDR still relies on the factthat the topology is a 2D-mesh network but withsome missing links. Adding some bits enables LBDRto successfully <strong>de</strong>al with the irregularity induced bymissing links. However, LBDR still relies on the factthat every switch has at most four links connectingneighboring switches (at North, East, West, or Southdirections). LBDR uses, as DOR does, the coordinatesof the <strong>de</strong>stination switch in the message andthe coordinates of the current switch, to computethe appropriate set of output ports. Thus, LBDRstill benefits from the original 2D-mesh layout.In this paper, what we propose is the extensionand applicability of the LBDR concept to trulyapplication-specific and irregular networks (as an examplesee Figure 1). The approach we follow is tomap the topology into a 2D grid (notice, however, wedo not change the initial topology). Once the topologyis mapped, we need to provi<strong>de</strong> coordinates to everyswitch in the network. Based on the coordinatesof the <strong>de</strong>stination switch and the current switch, the<strong>de</strong>rived LBDR logic will <strong>de</strong>ci<strong>de</strong> the output port thatneeds to be used to forward the packet towards its<strong>de</strong>stination. In or<strong>de</strong>r to correctly map the topologyinto a 2D grid, we have <strong>de</strong>veloped a mapping algorithmthat will search the space of combinations andwill <strong>de</strong>liver the most suitable ones, always guaranteeing<strong>de</strong>adlock freedom and connectivity.Due to the mapping performed, and because of thehigh irregularity we will find, some switches will requirea varying number of ports to connect to otherswitches, and in that situation some links will connectswitches not placed closely in the 2D grid. Thiskind of connectivity has not been provi<strong>de</strong>d by theoriginal LBDR mechanism, and thus, requires modifications.In this paper, we further extend LBDR forits support in this kind of mappings.B. LBDR Extension: LBDRxWe start the <strong>de</strong>scription with the mechanism requiredat every switch to <strong>de</strong>al with the irregulartopologies. In or<strong>de</strong>r to be concise, we take as a referencethe mapping of the initial topology (Figure 1)that appears in Figure 2. This mapping is obtainedwith the mapping tool that will be <strong>de</strong>scribed in thenext section. The mapping is representative of allthe connectivity patterns between switches that weneed to address in this section.Fig. 2.Mapping example for the initial topology.As we can see in the figure, there are switches withvarying connectivity patterns with other switches.For instance, switch 1, mapped at row 2 and column2, is connected to switches 4, 2, and 21 with differentlink mapped lengths. In particular, mapped length oflinks are 2 hops for links connecting to switches 2 and4, and 3 hops for the link connecting to switch 21.In addition, links with the same number of mappedhops have different orientations/directions, thus, beingdifferent. This is the case for link connecting toswitch 4 which is located one hop north and one hopwest from switch 1, and link connecting to switch 2that is two hops north.As previously <strong>de</strong>scribed, LBDR relies on switcheswith up to four ports, and each one connectingswitches in one direction in the 2D mesh plane (N,<strong>JP2011</strong>-676

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!