Exercises — Dynamic voltage and frequency scaling (DVFS)
6.4.2 · D4· Hardware › Power, Thermal & Reliability › Dynamic voltage and frequency scaling (DVFS)
Recall Teen formulas jo aap har jagah reuse karenge
Dynamic power: — energy per switch () times switches per second (). Static (leakage) power: — woh current jo powered-on transistors mein trickle karta rehta hai, chahe kuch switch na ho. Fixed work cycles ke liye task energy: jahan . Pure dynamic power ke liye yeh collapse hota hai mein — frequency cancel ho jaati hai, isliye energy voltage par depend karti hai, speed par nahi (jab tak leakage ignore hai).
Is page par use hone wale symbols, ek baar defined:
Level 1 — Recognition
L1.1 — Quadratic term kaun sa hai?
mein, agar aap sirf frequency double karein (voltage fixed), toh dynamic power ka kya hoga? Agar aap sirf voltage double karein (frequency fixed)?
Recall Solution
KYA: Exponents padho. power 1 par hai, power 2 par. double karo: . Power double ho jaati hai (×2). double karo: . Power chaar guna ho jaati hai (×4). YEH KYUN MATTER KARTA HAI: quadratic hi woh reason hai kyun DVFS voltage ko lower karta hai, sirf frequency ko nahi.
L1.2 — P-state table padho
Parent note ki Intel table use karte hue, kaun sa P-state sabse kam power deta hai, aur kaun sa sabse zyada frequency?
Recall Solution
Sabse kam power: P3 (0.90 V, 2.0 GHz, 22 W). Sabse zyada frequency: P0 (1.35 V, 4.0 GHz, 95 W). P0 "sprint" hai, P3 "coast" hai. Clock generation and PLs dekhein ki frequency actually kaise generate hoti hai, aur Voltage regulators dekhein ki voltage kaise deliver hoti hai.
L1.3 — Constraint ka naam batao
P3 ki frequency (2.0 GHz) ke saath P0 ki impossibly-low voltage (say 0.5 V) kyun set nahi kar sakte? Ek sentence mein.
Recall Solution
Kyunki lower voltage transistors ko slower switch karta hai (), isliye kisi voltage ke neeche logic next clock edge se pehle finish nahi ho sakta — chip galat results deta hai. Voltage aur frequency ko saath-saath scale karna padta hai.
Level 2 — Application
L2.1 — Proportional scaling savings
Ek core par run karta hai. Aap dono ko se scale down karte ho. Dynamic power kitne fraction se girti hai? Task energy kitne fraction se girti hai (task = fixed cycles)?
Recall Solution
Power: . Power girti hai. Energy: task leta hai, se zyada lamba. Toh . Energy girti hai. DIFFERENCE KYUN: power se scale hoti hai ( ke teen factors), lekin energy ek factor wapas kho deti hai kyunki slower clock runtime stretch karta hai. Net: energy .
L2.2 — Table mein plug karo
P1 (1.20 V, 3.5 GHz) se P3 (0.90 V, 2.0 GHz) move karo. Power ko pure dynamic maante hue (), ratio kya hai?
Recall Solution
Toh model predict karta hai ki P3, P1 ki dynamic power ka lagbhag 32.1% draw karta hai. (Table ka listed 22 W vs 65 W = 33.8% close hai — thoda gap leakage aur rounding ki wajah se hai.)
L2.3 — Fixed job ki energy
Ek task ko cycles chahiye. Isse P0 (4.0 GHz, 95 W) aur P2 (2.8 GHz, 40 W) par run karo. Dono ke liye time aur energy compute karo.
Recall Solution
P0: , . P2: , . Savings: energy, s () zyada time ki cost par.

Level 3 — Analysis
L3.1 — Voltage-only vs voltage+frequency
Student A sirf frequency half karta hai: , fixed. Student B frequency half karta hai aur voltage par drop karta hai. Original ke fractions mein unki dynamic powers compare karo.
Recall Solution
A: . → original ka 50%. B: . → original ka 24.5%. Analysis: B, A se half se bhi kam burn karta hai, same clock speed ke liye, purely term ki wajah se. Yahi DFS aur DVFS ka fark hai.
L3.2 — Deadline floor
Ek control loop ko har mein cycles run karne chahiye. Minimum frequency kya hai? Agar chip ka max 4.0 GHz hai, toh kya DVFS ka low P-state yahan usable hai?
Recall Solution
Yeh 4.0 GHz max se zyada hai — yeh task jaise likha hai, kisi bhi P-state par apna deadline meet nahi kar sakta. Aapko cut karna hoga (code optimize karo) cycles se neeche. Real-time systems aur CPU scheduling dekhein: hard deadlines ke liye, DVFS deadline floor se neeche scale nahi kar sakta.
L3.3 — Dynamic aur static power kahan cross karte hain
Maano aur , with , , aur fixed. Kis frequency par dono powers ek doosre ke equal hoti hain?
Recall Solution
set karo: 2 GHz se neeche, leakage dominate karti hai; usse upar, switching dominate karti hai. 2 GHz se neeche crawling leakage par energy waste karta hai.

Level 4 — Synthesis
L4.1 — Total-energy sweet spot
Ek job ko cycles chahiye. Total power ko model karo jahan , ke saath linearly track karta hai: with , . Use , . GHz par total energy compute karo aur batao kaun sa best hai.
Recall Solution
Pehle : 1 GHz par, ; 2 GHz par, ; 4 GHz par, . Time . Energy .
1 GHz: ; ; . 2 GHz: ; ; . 4 GHz: ; ; .
Best: 1 GHz at 0.75 J. Yahan leakage itni chhoti hai ki slow karna abhi bhi jeet jaata hai. L4.2 se contrast karo jahan leakage badi hai.
L4.2 — Jab leakage answer flip kar deti hai
Same setup L4.1 jaisa lekin ek leaky deep-submicron chip ke saath: . 1, 2, 4 GHz par energy recompute karo. Ab kaun jeetता hai?
Recall Solution
Leakage term 6× badi hai. 1 GHz: ; ; . 2 GHz: ; ; . 4 GHz: ; ; . Best abhi bhi 1 GHz hai (3.25 J) — lekin notice karo ki 1 GHz aur 4 GHz ka gap L4.1 ke 6× se shrink hokar 2.2× ho gaya. Leakage aur badhaao aur answer flip hokar racing mein aa jaayega. Yahi Race-to-idle vs race-to-dark tension hai, aur isliye Power gating exist karta hai: block band karke leakage ko zero pe cut karo.
L4.3 — Race-to-idle with sleep
Ek job ko cycles chahiye. Coast: hamesha 1 GHz par run karo (active power 0.6 W). Race-to-idle: 4 GHz par run karo (active power 4.5 W), jaldi khatam karo, phir sleep state mein drop ho jaao jo 0.05 W draw karta hai. Fixed 4-second window par total energy compare karo.
Recall Solution
Coast: active, phir idle. 4 s fairly compare karne ke liye, coast 2 s par finish karta hai phir bhi sleep karta hai. Active energy ; sleep ; total . Race: active ; sleep ; total . Coast yahan jeetta hai (1.3 J < 2.425 J) kyunki racing ka high active power leakage se bada hai jo woh avoid karta hai. Race-to-idle sirf tab jeetta hai jab sleep zyada save kare (bahut high leakage ya high fixed platform power). Thermal management dekhein: racing temperature bhi spike karta hai.
Level 5 — Mastery
L5.1 — Transition cost schedule badal deta hai
P-states switch karna free nahi hai: voltage regulator leta hai aur har transition par burn karta hai (dekhein Voltage regulators, Clock generation and PLs). Ek workload 1 ms bursts (P0 chahiye, 95 W) aur 4 ms idles (P3, 22 W) ke beech alternate karta hai. Ek poore 5 ms burst+idle cycle par compare karo (a) DVFS har phase switch karta hai vs (b) poori time P0 par rehta hai.
Recall Solution
(a) DVFS: cycle per 2 transitions (P0→P3 aur P3→P0). Burst: . Idle: . Transitions: . Total . (b) P0 par raho: . DVFS saves . 0.04 mJ transition cost yahan negligible hai kyunki phases (ms) transition time (µs).
L5.2 — Jab transitions dominate karte hain
Ab workload har millisecond ki jagah har mein flip karta hai. Same , . Kya DVFS yahan physically possible hai? Governor ko kya karna chahiye?
Recall Solution
Har phase chalta hai, lekin ek transition ko settle hone ke liye akele chahiye. Voltage phase khatam hone se pehle aa hi nahi sakta — DVFS is workload ko track nahi kar sakta. Governor decision: switch mat karo. Ek steady P-state choose karo (jaise average demand ke match karne wala ek mid P-state), ya idle micro-gaps ke liye faster Power gating use karo. Lesson: DVFS tabhi help karta hai jab workload phases transition latency se bahut lambe hon. Switch karne ka decide karne se pehle phase length measure karne ke liye Processor performance counters use karo.
L5.3 — Full optimization: deadline ke under energy minimize karo
Ek job ko cycles chahiye aur deadline ke andar finish hona chahiye. Power model with , , , (leakage ignore karo). Kaun si single frequency energy minimize karti hai aur deadline bhi meet karti hai?
Recall Solution
Leakage ignore karne par, energy = aur frequency cancel ho jaati hai — toh energy (hence ) ke ghattne par shrink hoti hai. Energy ke liye lower hamesha better hai. Deadline hume rokti hai: hona chahiye, yaani . Toh exactly 2 GHz par run karo — woh sabse slow speed jo deadline abhi bhi meet karti hai. Phir aur Yahi classic result hai: job ko exactly apna deadline fill karne tak stretch karo, na slower, na faster. (Leakage ke saath, answer deadline floor se upar nudge karta hai — L4 style — kyunki bahut zyada crawling bhi bahut zyada leak karta hai.)
Self-test recall
Right side cover karo aur answer do: