6.5.18 · D4 · HinglishAdvanced & Emerging Architectures

ExercisesCo-packaged optics trends

2,662 words12 min read↑ Read in English

6.5.18 · D4 · Hardware › Advanced & Emerging Architectures › Co-packaged optics trends

Sirf ek formula hai jo tumhe sach mein chahiye, woh parent note wala. Chalo usse zero se dobara earn karte hain taaki kuch bhi assume na ho.

Do aur tools jo hum use karenge, unhe chhune se pehle define kar lete hain:


Level 1 — Recognition

L1.1

Inme se kaun CPO design mein switch ASIC ke same package substrate par rehta hai: (a) ek QSFP-DD faceplate module, (b) optical engine, (c) External Laser Source?

Recall Solution

Answer: (b) optical engine. Definition ke hisaab se, co-packaged optics optical engine ko (modulators + photodetectors + short-reach SerDes/driver) ASIC ke same package par rakhta hai. QSFP-DD faceplate par hota hai (yahi woh cheez hai jo CPO hataata hai). External Laser Source (ELS) ko jaanbujhkar hot package ke bahar rakha jaata hai taaki failed laser swap ki ja sake — isliye woh package par nahi hota. Sirf (b) qualify karta hai.

L1.2

Inhe electrical reach ke hisaab se order karo, sabse chhote se: Pluggable, On-board optics (OBO), Co-packaged optics.

Recall Solution

Chhota → bada: CPO (1–5 mm) < OBO (5–10 cm) < Pluggable (10–30 cm). Integration spectrum ka poora point yahi hai ki optics ko die ke paas laane se electrical journey chhoti hoti hai. CPO in teeno mein sabse chhoti hai (sirf monolithic optical I/O, 0 par, aur chhoti hai).

L1.3

ko joules per bit mein convert karo. ko bits per second mein convert karo.

Recall Solution

(kyunki "pico" = ). (kyunki "tera" = ). Yahi woh do numbers hain jo tum seedha mein agle level par daaloge.


Level 2 — Application

L2.1

Ek 51.2 Tb/s switch faceplate SerDes use karta hai par. Electrical-interface power compute karo.

Recall Solution

Mantissas multiply karo: . Powers of ten multiply karo: . Iska matlab: sirf electrical I/O ke liye 256 W, switch core ke upar — woh "SerDes tax" jiske baare mein parent note warn karta hai.

L2.2

Same switch, lekin CPO reach shrink karta hai toh . compute karo aur L2.1 ke comparison mein fractional saving bhi.

Recall Solution

Saving . Dhyan se padho: yeh 80% sirf SerDes-reach portion ke liye hai is idealized assumption ke under. Whole-link saving zyada honest 30–50% hai (L2 ka trap dekho).

L2.3

Bandwidth double hokar 102.4 Tb/s ho gayi. Same CPO par, kya hai?

Recall Solution

Kyunki fixed par mein linear hai, bandwidth double karne se power exactly double hoti hai ( W). Parent note jo scary baat flag karta hai woh yeh hai ki real world mein bhi line rate ke saath badhta hai, toh power is clean doubling se zyada tez badhti hai.

L2.4

Ek copper trace ka loss hai operating frequency par. Faceplate reach hai; CPO reach (3 mm) hai. Dono dB budgets compute karo aur reduction bhi.

Recall Solution

use karo (loss length mein linear hai). Faceplate: . CPO: . Equalizer ko recover karna hai vs sirf — ek chhota budget. Isliye CPO ek tiny, low-power SerDes use kar sakta hai: equalize karne ke liye almost kuch hai hi nahi.


Level 3 — Analysis

L3.1

Do designs same 51.2 Tb/s move karte hain: (A) faceplate at , (B) LPO jo DSP hata deta hai aur reach karta hai pluggable form factor rakhte hue. B ki power compute karo, A se uski saving, aur argue karo ki full CPO ke jagah B kab choose karoge.

Recall Solution

A se saving: . Analysis: LPO link power ka half capture karta hai (vs CPO ka idealized 80% SerDes-slice) lekin pluggable form factor rakhta hai — isliye tum field serviceability aur per-port reach/speed mixing retain karte ho. LPO tab choose karo jab serviceability aur modularity power ke last increment se zyada matter kare; CPO tab choose karo jab tum power/faceplate-limited ho aur ek sealed, non-serviceable switch accept kar sako.

L3.2

Parent note kehta hai loss jaisi badhti hai. Low frequency par kaun sa term dominate karta hai, aur bahut high frequency par kaun sa? Gb/s par lanes move hone se kya imply hota hai?

Recall Solution

Growth rates compare karo. Chhote ke liye, (skin effect) (dielectric) se bada hota hai, toh skin-effect term dominate karta hai. Jaise badhta hai, linear term eventually ko overtake kar leta hai (ek line ek square-root ko beat karti hai), toh very high frequency par dielectric term dominate karta hai. Implication: lane rate Gb/s double karne se signal energy frequency mein upar jaati hai jahan tez badhne wala dielectric term rule karta hai — loss disproportionately badhti hai. Yahi hai "jahan copper reach sach mein toot ti hai," jo CPO / short-reach SerDes ko motivate karta hai.

L3.3

Ek ring-modulator resonance drift karta hai. Agar hot ASIC par co-locate karne se optics temperature badhti hai, toh resonance kitna drift karta hai, aur yeh CPO ka central headache kyun hai?

Recall Solution

Drift . Ek ring sirf apni resonant wavelength ke paas light pass karta hai; ek 3 nm shift use laser ke channel se bahar move kar sakta hai, link ko kill karte hue. Faceplate optics cool, controlled air mein baithe hote hain; CPO optics ko ek aisi die se glue kar deta hai jo hundreds of watts dump karti hai. Isliye thermal management (aur laser ko external rakhna) woh make-or-break engineering problem hai — pJ/bit math nahi, jo easy part hai.


Level 4 — Synthesis

L4.1

Ek total-power model banao. Ek 51.2 Tb/s switch ka core power hai. Case A: faceplate I/O at . Case C: CPO I/O at . Dono cases mein total power compute karo aur system-level saving (sirf I/O slice nahi). Phir explain karo ki honest headline 80% se chhoti kyun hai.

Recall Solution

I/O powers (L2 se): , . Totals: System saving . Synthesis point: wahi absolute 204.8 W saving I/O slice ka 80% hai lekin total ka sirf ~37%, kyunki 300 W core unchanged hai. Isliye parent note ka honest headline ~30–50% whole-system hai, 80% nahi.

L4.2

Ek architect jo Pluggable, LPO, aur CPO mein choose karta hai, uska decision (Mermaid flow ke roop mein) sketch karo, teen factors se driven: power budget, serviceability need, faceplate/density limit.

Recall Solution
flowchart TD
  A["Start: choose optics strategy"] --> B["Is power budget the hard limit"]
  B -->|no| C["Keep Pluggable QSFP-DD or OSFP"]
  B -->|yes| D["Must optics be field serviceable"]
  D -->|yes| E["Use LPO keep pluggable trim DSP"]
  D -->|no| F["Is faceplate density also limiting"]
  F -->|no| E
  F -->|yes| G["Go Co-packaged Optics sealed max density"]

Isko padhna: power pressure gate hai; agar tum serviceability bhi nahi kho sakte toh LPO par laandte ho; sirf tab jab tum ek sealed switch accept karte ho aur faceplate density bhi limit kar rahi ho tab full CPO jeetता hai. Yeh L3.1 aur L3.3 ke trade-offs ko ek path mein encode karta hai.


Level 5 — Mastery

L5.1

Design target: ek architect chahta hai total switch I/O power at . Optical I/O ko kaun sa end-to-end (pJ/bit) hit karna hoga? Kya yeh parent note ke stated CPO targets ke andar hai? Jawab defend karo.

Recall Solution

Engine invert karo: . Defence: parent note ka CPO target hai < 5 pJ/bit end-to-end, ~1 pJ/bit optical I/O ki taraf aim karta hua. require karna ~1 pJ/bit aspiration se bhi neeche hai — toh yeh budget current CPO goals se bhi zyada aggressive hai. Yeh physically sahi direction hai (short reach + silicon photonics) lekin better-than-state-of-the-art efficiency demand karta hai; architect ko ya toh budget ~100 W tak relax karna chahiye (~1 pJ/bit deta hai) ya monolithic optical I/O ka wait karna chahiye.

L5.2

Mastery synthesis: par, compare karo (i) faceplate 5 pJ/bit, (ii) LPO 2.5 pJ/bit, (iii) CPO 1 pJ/bit. Har ek I/O power aur faceplate ke comparison mein har ek saving do. Phir ek-ek sentence mein batao ki list mein neeche jaane par kaun sa non-power cost accept karte ho.

Recall Solution

use karke:

  • (i) Faceplate: — baseline.
  • (ii) LPO: → saving .
  • (iii) CPO: → saving .

Neeche jaane par accept kiye gaye non-power costs:

  • Faceplate → LPO: tum on-module DSP ki safety kho dete ho; link ab host SerDes par depend karta hai ek longer channel equalize karne ke liye (ek link-budget risk), lekin pluggable body reh jaati hai.
  • LPO → CPO: tum field serviceability aur modularity kho dete ho — optics package substrate par seal ho jaati hain, aur ek dead engine ka matlab switch scrap karna ho sakta hai, jabki hot ASIC ab optical thermal stability ko threaten karta hai. Verdict: power savings aur integration risk saath-saath badhte hain; koi free lunch nahi hai, sirf curve par ek chosen point hai.

Recall Ek-line self-check

CPO whole-switch saving (~37% L4.1 mein) I/O-slice saving (80%) se itni kam kyun hai? ::: Kyunki untouched switch core power whole-switch percentage ke denominator mein baithta hai lekin I/O-slice percentage mein nahi — same joules saved, bada base.

Yeh bhi dekho: Switch ASIC Bandwidth Scaling · Data Center Network Topologies · Co-packaged optics trends