6.3.6 · D4 · HinglishInterconnects, Buses & SoC

ExercisesNetwork-on-Chip (NoC) topologies

2,511 words11 min read↑ Read in English

6.3.6 · D4 · Hardware › Interconnects, Buses & SoC › Network-on-Chip (NoC) topologies

Yeh page ek self-test ladder hai. Har exercise apna level batata hai (L1 → L5). Pehle khud try karo, phir collapsible solution kholо. Har formula jo tumhe chahiye woh parent topic mein build kiya gaya tha — lekin hum use karte waqt har baar re-state kar dete hain, taaki tumhe koi symbol dhundhna na pade.

Reference numbers jo poore mein use hote hain: ek link bits per cycle carry karta hai frequency par, toh ek link ki bandwidth hai

Figure — Network-on-Chip (NoC) topologies

Level 1 — Recognition

Recall Solution 1.1

YEH kya hai: routers ka ek grid jisme sirf up/down/left/right links hain aur koi edge-wrapping nahi, woh Mesh (2D grid) hai. Degree = ek router se nikalne wale links ki sankhya. Figure s01 dekho.

  • Centre router ke saare chaar neighbours present hain → degree .
  • Corner router sirf do neighbours ko touch karta hai → degree . Answer: Mesh; centre degree , corner degree .
Recall Solution 1.2

Ek closed loop jisme har router sirf apne do loop-neighbours se link karta hai woh Ring hai. Har node mein exactly links hote hain, isliye degree uniformly hoti hai. Answer: Ring.


Level 2 — Application

Recall Solution 2.1

Yahan . Answer: hops. (Figure s02 dekho: bottom-left se top-right tak ka red staircase 6 links lamba hai.)

Recall Solution 2.2

Formula: . Ek mesh mein vertical cut har row mein ek link = links tod deta hai. Answer: .

Recall Solution 2.3

Diameter: worst case woh node hai jo loop ke directly "across" hai. hops. Bisection: loop ko kahin bhi kato aur tum hamesha exactly links todoge (loop mein do arcs hain), isliye Answer: hops, — tiny bisection hi reason hai ki rings heavy traffic mein choke ho jaate hain (dekho Latency and Throughput Trade-offs).


Level 3 — Analysis

Recall Solution 3.1

Mesh: hops. Torus: wraparound ka matlab hai ki har dimension mein tumhe zyada se zyada aadha chakkar lagana padega, . Toh Reduction: . Answer: Mesh , Torus hops — ki drop. Wraparound links shortcuts hain.

Recall Solution 3.2

hai XOR = chosen bit flip karo. Node .

  • Neighbours: — exactly (degree ). Diameter: koi bhi do nodes at most bit positions mein differ karte hain, aur har hop ek bit fix karta hai, isliye hops. Answer: neighbours ; .

Level 4 — Synthesis

Recall Solution 4.1

Har ek compute karo (sab ke saath):

Topology Diameter Degree
Mesh (interior)
Torus (uniform)
4D Hypercube
16-node Ring
Ranking (best→worst diameter): Torus Hypercube < Mesh < Ring .
Diameter par winner: Torus aur Hypercube ka par tie hai. Yahan dono ka degree bhi hai, isliye par degree cost identical hai — deciding factors ban jaate hain physical layout (torus ko long wraparound wires chahiye; hypercube non-planar hai) aur bisection bandwidth. Layout constraint ke liye System-on-Chip (SoC) Design dekho.
Answer: Torus aur Hypercube diameter par tie karte hain, dono degree ; Ring sabse kharab par.
Recall Solution 4.2

Hypercube degree . Solve karo . Agla power of two hai , jahan degree . Answer: par (degree ). Yeh kyun matter karta hai: har extra port ek crossbar row/column, buffers, aur arbitration logic add karta hai, isliye router area/power roughly degree ke saath scale karta hai. se aage hypercube ka router grow karta hai jabki torus ka par fixed rehta hai — yeh ek real power aur area penalty hai, chahe hypercube ka diameter abhi bhi tiny ho.


Level 5 — Mastery

Recall Solution 5.1

, , binary tree isliye . (a) Root link — ek leaf link ka , yahi reason hai ki ise fat tree kehte hain. (b) — kisi bhi cut par koi bottleneck nahi. (c) hops (leaf upar root tak, root neeche leaf tak). (d) Mesh bisection tha; fat-tree hai = zyada. Price paid: huge root switch bada aur power-hungry hai, aur -hop diameter (mesh ke ki tulna mein) ka matlab hai nearby nodes ke liye higher latency. Bandwidth-critical designs (datacenter-jaisa traffic) yeh accept karte hain; latency-critical designs shayad na karein.

Recall Solution 5.2

All-to-all traffic bisection bandwidth par stress dalta hai (aadhe cores doosre aadhe ko flood karte hain). Power budget jo long wires forbid karta hai woh Torus (wraparound wires chip span karti hain) aur Hypercube (non-planar long links) aur Fat-Tree root wires ko penalise karta hai. Bisection numbers par ( Gb/s):

Topology Bisection BW Long wires?
Ring Gb/s no
Mesh Gb/s no (saare links short/local)
Torus Gb/s yes (wraparound)
Hypercube Gb/s yes (non-planar)
Fat-Tree Gb/s yes (fat root wires)
Reasoning: highest-bisection options (Fat-Tree, Torus, Hypercube) sab "no long wires" constraint violate karte hain. Wire-friendly, planar options mein (Ring, Mesh), Mesh ring ki bisection double karta hai ( vs Gb/s) sirf short, local links ke saath.
Winner: Mesh — physically-allowed, short-wire topologies mein best bisection, aur uska regular grid 2D floorplan par cleanly map hota hai. Agar power rule relax ho jaaye, toh Torus (hypercube jaisa diameter, uniform degree , mesh se double bisection) aage aa jaata.