Changes between Version 21 and Version 22 of InterconnexionNetworks
- Timestamp:
- Aug 29, 2010, 6:00:24 PM (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
InterconnexionNetworks
v21 v22 15 15 == 2. VCI initiators & targets indexing == 16 16 17 A s a given hardware component can have several VCI ports (for example the L1 cache has three VCI ports : one initiator port to the direct network, one initiator port to the coherence network, and one target port on the coherence network), each VCI port hasa different identifier that is defined by three indexes :17 A given hardware component can have several VCI ports. For example the L1 cache has three VCI ports : one initiator port to the direct network, one initiator port to the coherence network, and one target port on the coherence network. Each VCI port can have a different identifier that is defined by three indexes : 18 18 19 19 * '''X_ID''' is the cluster X-coordinate. … … 21 21 * '''L_ID''' is the local index inside the cluster. 22 22 23 An hardware component that has several VCI ports can have several different values for the L_ID local index. 24 23 25 The X_ID, Y_ID and L_ID are coded on NX, NY, NL bits respectively. 24 NX, NY and NL are global parameters for the TSAR architecture, but NX & NY cannot be larger than 5 (no more than 1024 clusters), and NL cannot be larger than 4 25 (no more than 16 ports per cluster). 26 The NX, NY and NL parameters are global for a given instance of the TSAR architecture, but NX & NY cannot be larger than 5 (no more than 1024 clusters), and NL cannot be larger than 4 (no more than 16 ports per cluster). 26 27 27 In order to simplify the hardware implementation of the memory coherence protocol, the L_ID values are standardized on the coherence network, and the same value is used 28 for an initaitor port and for a target port: 28 In order to simplify the hardware implementation of the memory coherence protocol, the L_ID values are standardized on the coherence network, and the same value is used for an initaitor port and for a target port: 29 29 30 30 ||COMPONENT ||LOCAL_INDEX|| … … 117 117 There is actually Five types of DSPIN packets: 118 118 119 ==== 3.3.1 DSPIN Read Command packet format ====119 ==== 3.3.1 DSPIN Read Command packet format (40 bits) ==== 120 120 121 121 A single flit VCI Read Command packet (this includes LL packets) is translated to a 2 flits DSPIN Read Command packet : … … 128 128 || 1 || 14 || 2 || 2 || 8 || 4 || 4 || 5 || 129 129 130 ==== 3.3.2 DSPIN write Command packet format ====130 ==== 3.3.2 DSPIN write Command packet format (40 bits) ==== 131 131 132 132 A N flits VCI Write Command packet (this includes SC packets) is translated to a N+2 flits DSPIN Write Command packet : … … 142 142 || 1 ||3 ||4 || 32 || 143 143 144 ==== 3.3.3 DSPIN Broadcast Command packet format ====144 ==== 3.3.3 DSPIN Broadcast Command packet format (40 bits) ==== 145 145 146 146 The single flit VCI Write Broadcast is translated to a 2 flits DSPIN Broadcast Command packet. … … 149 149 150 150 Flit 0 : 151 ||EOP||XMI ||XMA||YMI||YMA|| CID ||TRDID||PKTID||BC||151 ||EOP||XMIN||XMAX||YMIN||YMAX|| CID ||TRDID||PKTID||BC|| 152 152 || 1 || 5 || 5 || 5 || 5 || 10 || 4 || 4 ||1 || 153 153 Flit 1 : … … 155 155 || 1 || 5 || 34 || 156 156 157 ==== 3.3.4 DSPIN Read Response packet format ====157 ==== 3.3.4 DSPIN Read Response packet format (33 bits) ==== 158 158 159 159 A N flits VCI Read Response packet is translated to a N+1 flits DSPIN Read Response packet : 160 160 161 161 Flit 0 : 162 ||EOP||RSRCID||RERROR||RTRDID||RPKTID||res erved||BC||163 || 1 || 14 || 2 || 4 || 4 || 5||1 ||162 ||EOP||RSRCID||RERROR||RTRDID||RPKTID||res||BC|| 163 || 1 || 14 || 2 || 4 || 4 || 7 ||1 || 164 164 Flit 1 : 165 ||EOP||---------------RDATA------------------------ --||166 || 1 || 32 165 ||EOP||---------------RDATA------------------------|| 166 || 1 || 32 || 167 167 168 ==== 3.3.5 DSPIN Write response packet format ====168 ==== 3.3.5 DSPIN Write response packet format (33 bits) ==== 169 169 170 170 A single flit VCI Write Response packet is translated to a single flit DSPIN Write Response packet. 171 171 172 172 Flit 0 : 173 ||EOP||RSRCID||RERROR||RTRDID||RPKTID||res erved||BC||174 || 1 || 14 || 2 || 4 || 4 || 5||1 ||173 ||EOP||RSRCID||RERROR||RTRDID||RPKTID||res||BC|| 174 || 1 || 14 || 2 || 4 || 4 || 7 ||1 || 175 175 176 176 Note : This format is also used for the response packets to a broadcast command, as each VCI response packet to a broadcast command is actually a VCI response packet to a single flit write command.
