23. Test signatures, electromigration, clocks and energy
Lecture 22 is, in the lecturer’s own word, a “grab bag”: four topics that finish the course’s circuit material before the last lecture turns to devices. It opens by finishing built-in self-test: a few flip-flops and one XOR gate, a linear feedback shift register, make a long pseudo-random test pattern, and a second such register folds the circuit’s whole response into a short signature. Then electromigration: why a steady current slowly drags a wire’s metal along with it, why supply straps and vias are the wires at risk, and the current-density limits in mA/µm² that size them. The middle of the lecture is clock distribution: the four things a clock network is judged by (skew, jitter, power and latency), why a network with a short latency has less skew and jitter, and the three ways chips have distributed their clocks (grids, H-trees and tree-driven grids). The lecture ends with energy-constrained design: the two kinds of wasted power and the gating that removes each, the energy–delay curve, and the supply voltage as the knob that moves a design along it (DVFS).
Two sections at the end are added. The lecture stops at “you can operate below threshold”; two past final parts ask how far below. Section 15 finds the lowest supply at which a subthreshold inverter still gives a valid logic level, and Section 16 finds when a lower supply stops saving energy.
After this chapter you can:
- build a maximum-length LFSR, list its states, and compress a response stream into a signature;
- explain electromigration, say why supply lines and vias are at risk and why burn-in runs hot, and size a wire from a current-density limit;
- define skew, jitter, power and latency, and explain why a clock network with low latency has less skew and jitter;
- compare a grid, an H-tree and a tree-driven grid, and explain why tree delays are tuned wire for wire and silicon for silicon;
- name the two sources of wasted power and the gating that removes each;
- read an energy–delay curve, use to move along it, and explain DVFS;
- find the lowest supply at which a subthreshold inverter still gives a valid logic level, and decide whether a logic block has a minimum-energy supply above it.
Boxes and equations marked board were written in the lecture. Parts marked added are explanations or examples this guide adds. The lecture writes almost no equations (only , and the current-density limits), so nearly every worked example here is added and uses illustrative values, built from the course’s earlier models.
Symbols
| Symbol | Meaning | Unit | First appears |
|---|---|---|---|
| the number of flip-flops in an LFSR or signature register | — | §1 | |
| , | the output and the input of flip-flop | — | §1 |
| exclusive OR (XOR): 1 when its inputs differ | — | §1 | |
| , | current density in a wire, ; its allowed limit | mA/µm² | §3, §4 |
| a wire’s current (DC unless stated) | mA | §3 | |
| , | a wire’s width and thickness | µm | §4 |
| latency: the clock network’s delay from its root to a leaf flip-flop added | ps | §6 | |
| signed skew (Chapter 14): how much later the capturing flip-flop’s clock arrives | ps | §6 | |
| , | the size of the static and of the transient spread in clock arrival | ps | §6 |
| the supply sensitivity of delay, ; Chapter 21 and FS1 write it | — | §6 | |
| , | supply voltage; threshold voltage | V, mV | §6 |
| , | the side of a square chip; the number of levels of an H-tree | mm | §8, §9 |
| the pitch of a clock grid | mm | §8 | |
| , | a driver’s resistance; a change of load capacitance | Ω, fF | §9 |
| , | the clock network’s capacitance; the clock frequency | pF, GHz | §8, §12 |
| the on-resistance of a power-gating switch | Ω | §12 | |
| , , | energy per operation: total, switching, leakage | J (or V² per ) | §13, §16 |
| the subthreshold slope: gate voltage per decade of current | mV/decade | §12, §15 | |
| the thermal voltage, 26 mV at room temperature | mV | §15 | |
| , | a transistor’s current at and at | nA | §15 |
| , | an inverter’s output voltage; the lowest supply at which the low output is at most added | mV | §15 |
| , | gates on the critical path (logic depth); gates in the whole block added | — | §16 |
| the fraction of the block’s nodes that rise in one operation added | — | §16 | |
| the time one operation takes | ns | §16 | |
| , | the supply in units of , ; the block constant added | — | §16 |
1. LFSRs: pseudo-random test patterns
You need
Logic BIST (Chapter 22). A tester checks a die by shifting patterns into its scan chains, clocking the logic once, and shifting the responses out (the scan test of Chapter 22). Built-in self-test puts that job on the chip. LBIST (logic BIST) generates the patterns, runs them through the scan chains and checks the responses on chip; ABIST does the same for memory arrays.
A D flip-flop (Chapter 13) copies its input D to its output Q at each clock edge and holds it until the next. Flip-flops in a row, each Q wired to the next D, form a shift register: at every edge each bit moves one place along.
XOR added. is 1 when and differ and 0 when they are equal. So , , and .
The question. LBIST needs a pattern generator on the chip: something small that produces a long, random-looking stream of bits to shift into the scan chains. How do four flip-flops and one XOR gate make such a stream, how long does it run before it repeats, and why is that length and not ?
Where the two registers of this section and the next sit added, after the lecture (00:37–05:59). A pattern generator (PRBS, from an LFSR) feeds the scan chains of the circuit under test (CUT); the responses go into a signature register (SIG), whose final contents are compared (=) with the expected signature; a BIST controller sequences the run. The expected signature is drawn as the shaded register SIG₀; ✓ and ✗ mark pass and fail.
From a shift register to a pattern generator (board, 00:37–03:45)
- What LBIST needs board. A pattern generator that makes a PRBS, a pseudo-random bit sequence: a stream that looks random but is fully determined, so a simulation of the good circuit can predict every response (00:51).
- The circuit board (01:40–02:28). Four flip-flops in a ring, numbered 1 to 4. Each drives , as in a shift register. Flop 1’s input comes from an XOR of and : the outputs of flip-flops one and four, “feeding them round” to the input. That is the linear feedback shift register (LFSR). The output is taken from flop 4.
- The rule, one clock at a time added. At each edge, The superscript + means “after the edge”. Everything moves one place right, and the new bit entering at the left is the XOR of the old first and last bits.
- The name of the feedback board (02:28). The board names this feedback by its generator polynomial, . added Which end of the register counts as is a convention: read from the other end, the same register is . The algebra is not needed here; what matters is the register drawn and the rule in step 3.
- How long it runs board (03:05). “The longest I can run before I repeat myself is 2 to the n minus 1”: for flip-flops, 15 clocks. Feedback that reaches that length gives a maximum-length sequence, and the board’s register is one.
- Other uses (03:32). The same PRBS generators test communication links, where a receiver compares the received bits with its own copy to measure the bit error rate.
The board’s four-flop LFSR board, redrawn (Lecture22 @ 05:53; drawn 01:40–03:00). The XOR of and feeds ; each feeds ; the output leaves flop 4. The board names the feedback and marks the output with the period . The flip-flops are drawn as boxes with a clock input (the board draws D shapes).
The board (Lecture22 @ 05:53)

Fair copy of the board above (Lecture22 @ 05:53), mark for mark in its own layout, all in black. A cyan pen wrote the recap down to “LFSR (linear feedback shift register)”; a pink pen wrote the rest: the four-flop LFSR, “maximum length sequence”, the generator polynomial and the six-flop signature register. The pink pen carries the topic on rather than marking a layer over the cyan, so it takes no accent. Nothing is hidden: the lecturer stands behind the strokes (checked against 00:57 and 05:08). The flip-flops keep the board’s D shapes, and the LFSR’s XOR faces left, as drawn. The hand’s “GSD” (general scan design) ends in an open loop that reads like “n”. The words are set smaller than the hand, and “polynomial” and x⁴ + x + 1 sit a little right of their place to clear the wider type.
Walking the register through its states
A worked example: the board's LFSR from 0001 (added)
-
The seed. Load . Any nonzero state would do (step 4 says why not zero).
-
The first clock. , and the other bits shift right: .
-
Keep going. Each column below is one clock later; the leftmost bit of each state is the XOR of the first and last bits of the state before it.
Clock 0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 0001 1000 1100 1110 1111 0111 1011 0101 1010 1101 0110 0011 1001 0100 0010 0001 After 15 clocks the register is back at 0001, and from then on the sequence repeats.
-
Why 15, not 16. The 15 states are all different, and they are every 4-bit pattern except 0000. That one is excluded because it is a trap: , so 0000 maps to itself forever. A register seeded with zeros produces only zeros. So the most an -flop register can visit is the nonzero states.
-
The output stream. Reading over one period gives 100011110101100: 8 ones and 7 zeros, as balanced as an odd length allows. It never has more than three zeros in a row, because four zeros in a row would mean the state 0000.
-
Not every feedback is maximal. Move the tap from to (, the polynomial ): from 0001 the register returns after only 6 clocks. The other nine nonzero states form separate, shorter cycles. A pattern generator needs a feedback that is known to be maximal, and tables of such polynomials exist for every .
Memorize it, with its reason: states, minus the all-zero trap.
Traps.
- states. The all-zero state is excluded; an -flop LFSR has period at most.
- Seeding with zeros. A reset that clears every flip-flop leaves the generator stuck at 0000; the seed must be nonzero.
- Any taps will do. Only some feedbacks are maximal; the , taps above give a period of 6.
Check yourself How many clocks does a 20-flop maximum-length LFSR run before it repeats?
1,048,575: about a million patterns from twenty flip-flops and a few XOR gates.
Check yourself Start the board's register at 1111. What are the next three states, and after how many clocks does 1111 come back?
Each new first bit is of the state before. From 1111: , so 0111; then : 1011; then : 0101. The register is maximal, so every nonzero state lies on the same 15-state cycle (it is the walk above, entered at clock 4): 1111 returns after 15 clocks.
Check yourself Why can the output stream of an n-flop LFSR never contain n zeros in a row?
The output is , and each bit of the register reaches the output a few clocks later: one clock later, two, three. So four zeros in a row out of are the four bits the register held at one moment: all four flip-flops held 0. That is the trap state, which a nonzero seed never reaches.
2. Signature registers: compressing the response
You need
The LFSR (Section 1). Flip-flops in a shift register with an XOR feeding back from the outputs; with a maximal feedback, flip-flops cycle through all nonzero states before repeating.
The response (Chapter 22). After each test pattern is captured, the scan chain shifts the logic’s response out of scan_out one bit per clock. A test of thousands of patterns gives millions of response bits, and each must match what a simulation of the good circuit predicts.
The question. Comparing millions of response bits one by one on chip would need the whole expected stream stored beside the circuit. How can a register of a few flip-flops fold the whole stream into a short signature that is compared once, and what can such a compression miss?
From an LFSR to a signature register (board, 04:02–05:59)
- A second LFSR, with an input board (04:26–04:49). Six flip-flops in a row. The incoming response bits enter through an XOR in front of flop 1, together with ; a second XOR in front of flop 2 combines with ; the rest simply shift. As equations added:
- Clock the response in (05:17). Reset the register, then clock the entire response stream through it, one bit per clock. Every bit is mixed into the state, and the feedback keeps mixing it.
- Read the signature. At the end the six flip-flops hold the signature: “a kind of compression” (05:17). The small arrows above the flip-flops on the board are the parallel read-out.
- One compare. The chip compares the signature with the one a simulation of the good circuit predicts. Equal: pass. Different: the circuit is faulty.
- Good enough (05:17–05:59). “It’s not going to be able to test everything, but … it provides some degree of coverage and it makes the whole thing manageable”: a PRBS in, a signature out, one compare, and an LBIST engine to sequence it.
The board’s signature register board, redrawn (Lecture22 @ 05:08; also at 05:53). The response stream enters at the left: and , the rest shift. The upward arrows read the six bits out in parallel at the end: the signature.
A worked signature
A worked example: a 12-bit response (added; the stream is illustrative)
-
The stream. Take a response of 12 bits, 101100111000, entering first bit first, and reset the register to 000000.
-
The first clocks. Clock 1, input 1: , the rest are 0: 100000. Clock 2, input 0: , : 010000. The feedback first matters when a 1 reaches (clock 6).
-
The whole run (state after each clock):
Clock 1 2 3 4 5 6 7 8 9 10 11 12 in 1 0 1 1 0 0 1 1 1 0 0 0 state 100000 010000 101000 110100 011010 001101 010110 101011 000101 110010 011001 111100 The signature is 111100.
-
A faulty circuit. Suppose a fault flips the fifth response bit (101110111000). The same run ends at 100100: a different signature, so the fault is caught.
-
Why every single error is caught. The register is linear: built from XORs and wires only. So the signature of a stream is the XOR of the signatures of any two streams that XOR to it. The faulty stream is the good one XOR an error stream 000010000000, whose own signature is 011000; and indeed . An error stream with a single 1 never has signature 000000: the 1 makes the state nonzero, and with no input the register’s step is reversible (each state has exactly one state before it, and 000000’s is 000000), so a nonzero state never becomes 000000. Every single-bit error therefore changes the signature.
-
What it can miss. A long, random error stream lands on the good signature only if its own signature happens to be 000000. Out of possible signatures, that is about one chance in 64: 1.6 % for six bits. This is aliasing. Real signature registers use 16 to 32 bits, which makes it negligible.
Memorize: each extra bit halves the chance a fault slips through.
Traps.
- “A matching signature proves the circuit right.” It makes a fault very unlikely, not impossible (aliasing), and it says nothing about faults the patterns never excite.
- No reset. The register must start in a known state, or the good circuit’s signature cannot be predicted.
Check yourself Why does any single wrong bit always change a linear signature?
The faulty stream is the good stream XOR an error stream with one 1 in it, and by linearity its signature is the good signature XOR the error stream’s signature. A single 1 clocked into a reset register makes its state nonzero, and with zeros coming in the register’s step is reversible (only 000000 leads to 000000), so the state never returns to zero. That second signature is never 000000, and the XOR changes the result.
Check yourself Reset the board's register to 000000 and clock in 1, 0, 0. Give the state after each clock.
Clock 1: : 100000. Clock 2: , : 010000. Clock 3: , , : 001000. With throughout, the register is a plain shift register so far.
Check yourself Roughly how many signature bits keep the aliasing probability below one in a million?
, just under , while is just over: 20 bits.
3. Electromigration: why DC current wears a wire out
You need
The inverter’s currents (Chapter 6). When the output rises, charge flows from through the PFET onto the load; when it falls, the charge flows from the load through the NFET to ground. So the supply wire only ever carries current out of , and the ground wire only ever carries it into ground, while the output wire carries it one way to charge and the other way to discharge.
Current density added. The current per unit of a wire’s cross-section, for a wire of width and thickness . The same current through a narrower or thinner place has a higher density.
Infant mortality and burn-in (Chapter 22). Some dies carry latent defects that fail early in use. Burn-in runs every die hot (about 85 °C) at a raised supply for a few hours in the factory, so those dies fail there instead of in the field.
The question. A wire carrying current is not inert: over years, a large current can move the metal itself. What is that effect, which wires does it threaten, how does it make a chip fail, and why is burn-in the way to find a wire that will fail early?
From current to a failed wire (board, 07:07–13:12)
- The effect board (07:07–07:35). A large current, usually a DC current, pushes the metal ions of the wire along with it. This slow transport of the metal is electromigration: a wear-out mechanism.
- DC against AC board (08:06–08:31). In an inverter, the supply connections carry current one way all the time: out of , into ground. That is DC. The output wire carries current one way while it charges the load and back while it discharges it: AC, and the ions are pushed back and forth with almost no net motion. “So power connections are often the biggest source” of electromigration.
- Where it fails board (08:48–09:24; drawn by 12:23). Where current rounds a corner, metal is pulled away from one spot and piled up at another. The depleted spot thins until it becomes a void, an open circuit. The pile becomes a protrusion that can grow into the neighbouring wire and make a short.
- It is a matter of density board (09:27). Electromigration depends on the current density, the current per cross-section area, not on the current alone. Vias squeeze a wire’s current through a small square, so they are frequent culprits.
- It is thermally activated board (09:54–10:22). The rate grows exponentially with temperature. That is why burn-in runs hot: it speeds up electromigration so that a weak wire fails in the factory.
- The defect burn-in catches board (12:39–13:12). A dust particle during fabrication pinches a wire (“this metal”) to a neck. The neck carries the full current through a fraction of the width, so its current density is far higher than designed. Under burn-in it electromigrates open, and the die is rejected before it ships. This is the infant-mortality mechanism that Chapter 22’s burn-in section answers with (FN17-1e).
- An aside (11:49–12:15). The lecturer calls electromigration “a very bizarre effect”: when someone first described it to him, “I thought they were nuts”, until he saw a time-lapse film of a wire’s metal moving.
Which wires carry DC board, redrawn (Lecture22 @ 12:23; drawn 08:06–08:31). The supply connections carry current one way only, out of and into ground (dc); the output wire carries it to the load and back (ac), so its net push on the metal is about zero.
Where electromigration strikes board, redrawn (Lecture22 @ 10:58, 12:23, 13:12). (a) Current rounding a corner. (b) Metal moved from one spot (a void: an open) to another (a protrusion that can short to the neighbour). (c) A via crowds the current into a small area. (d) A particle pinches a wire to a neck, where the current density is far above the design’s: the defect burn-in finds.
The board (Lecture22 @ 13:12)

Fair copy of the board above (Lecture22 @ 13:12), mark for mark in its own layout, all in black: one violet pen wrote the topic (“Lecture 22” is the opening board’s cyan title). Nothing is hidden: the lecturer stands behind the strokes (checked against 12:23), and the two wires with the dust particle, top right, are new at 13:12. A long diagonal and a short stroke cross “150 mA/µm²”. They look like a cross-out, but the speech keeps 150 mA/µm² as copper’s AC limit, “so high as to be not even much of an issue” (11:34–11:43), so they are copied as drawn. The hand writes each unit’s slash as a near-vertical bar with µm² below it, as set here. The stroke under “Cu” and the small mark below it run off the lit area and are copied as strokes.
Which wires are at risk
A walk over the inverter drawing above added, wire by wire.
- The strap feeding the inverter’s PFET carries every charging current, always in the same direction: DC. At risk, and more so the more gates it feeds.
- The ground strap carries every discharging current, always into ground: DC. At risk in the same way.
- The output wire carries the same charge out and back each cycle: AC. Its current can be large, but the ions’ net drift cancels, and AC limits are about ten times higher (Section 4). Safe at the densities chips use.
- A via stack on a strap, where the supply drops from a wide upper layer to a lower one, carries DC through a few small squares: the highest density on the path. The worst spot, and the one checked first.
So electromigration is a supply-network problem first: wide straps, many vias in parallel, and no narrow necks on the way from the pads to the cells.
Traps.
- “An output wire’s current averages to zero, so it carries no current.” Its current is large; only the net push on the metal, one way then the other, cancels.
- Electromigration is not IR drop. IR drop is a loss of voltage along a resistive supply (Chapter 21) that slows gates now; electromigration is the wire’s metal moving, which opens or shorts it after months or years.
- The total current is not what matters. A modest current through a narrow neck or a single via can exceed the limit that a wide wire carrying the same current never approaches.
Check yourself Why is a clock net, which switches every cycle, safer from electromigration than the supply strap that feeds its drivers?
The clock wire charges its load and then discharges it: AC, so the metal is pushed one way and then back, with almost no net motion. The strap delivers the charging current of every one of those cycles in the same direction: DC, so its push accumulates.
Check yourself A strap's current density doubles at a constriction, and burn-in runs the chip 60 °C hotter than normal use. Which effect makes the constriction fail during burn-in, and why does it fail before the rest of the strap?
Both act together. Electromigration is thermally activated, growing exponentially with temperature, so burn-in’s heat speeds it up everywhere and moves a weak wire’s failure from years into the factory’s hours. The constriction fails first because there the current density, the quantity electromigration depends on, is twice the strap’s: it was already the weak spot, and the heat only brings its failure forward.
Check yourself Why does the board list vias with current density?
A via joins two wires through a small square, so the whole current of a wide strap passes through a cross-section much smaller than the strap’s. The current density there is high, and electromigration follows current density.
4. Current-density limits and sizing a wire
You need
Electromigration (Section 3). Metal ions are pushed along by current; DC currents (supply straps, ground straps, vias) accumulate the push, AC currents (signal wires) mostly cancel it. The rate depends on the current density , where is the wire’s width and its thickness, and it grows exponentially with temperature.
Copper and aluminium (Chapter 20). Older processes wired chips in aluminium; modern ones in copper, which also has the lower resistivity.
The question. Electromigration sets a limit on current density. What are the numbers, and how does a designer turn them into a wire’s width or a number of vias?
The limits (board, 10:22–11:49)
- DC limits board (10:40–10:52). Aluminium: 1–2 mA/µm². Copper: about 10 mA/µm², “about a factor of 10” better: another benefit of copper besides its lower resistance.
- AC limits board (11:23). Far higher: about 15 mA/µm² for aluminium and 150 mA/µm² for copper, “so high as to be not even much of an issue”. The board writes the two numbers; that they are the AC limits is said, not written.
- The rule for sizing added. Keep at or below . With the layer’s thickness fixed by the process, that sets a minimum area and a minimum width (the formula below).
- The state of things (11:49). Copper “has really helped to solve this”, but supply straps and their vias are still checked against the DC limit.
Sizing for electromigration added. (a) The current density is the current over the cross-section, . (b) Where a strap changes layer, its current divides among an array of vias, each of which may carry only times its own small area.
Derive it: current density is current over area, and the area is width times thickness. Memorize the limits: Al 1–2, Cu ≈ 10 mA/µm² DC; ≈ 15 and 150 AC.
A worked example: a supply strap and its vias (added; values for example)
- The strap. For example, a supply strap carries 20 mA of DC in a metal layer 0.5 µm thick.
- In copper ( = 10 mA/µm²). The area must be at least 2.0 µm², so the width at least 4.0 µm.
- In aluminium ( = 1–2 mA/µm²). The area must be 10–20 µm², the width 20–40 µm: five to ten times wider. That is the factor of 10 the board gives copper.
- The vias. Where the strap drops to the layer below, take copper vias of 0.2 µm × 0.2 µm. Each may carry 0.40 mA, so the strap needs at least 50 vias in parallel. One via in the wrong place, carrying the whole strap’s current, would be at fifty times its limit.
- A signal wire. A copper signal wire 0.1 µm × 0.2 µm may carry only 0.20 mA of DC, but 3.0 mA of AC. Its real current is AC, so it is the higher number that applies, and it is rarely reached.
Check. The two copper numbers agree: a 4.0 µm × 0.5 µm strap has the same 2.0 µm² as fifty 0.04 µm² vias, so both run at exactly the limit.
Traps.
- mA per µm², not per µm. The limit is per unit of cross-section area; a width-only rule ignores the thickness.
- “Million amps.” The lecture’s captions say “million amps per square micron”; the board and the speech say milliamps.
- The AC limit on a supply strap. A strap’s current is DC; its limit is the DC one, ten times lower.
- One via for a strap. A via’s tiny area carries a tiny current; the strap’s current needs an array.
Check yourself Name the two benefits copper brought to supply straps over aluminium.
Its DC electromigration limit is about ten times aluminium’s (10 against 1–2 mA/µm²), so the same current needs a smaller cross-section. And its lower resistivity gives less IR drop for the same width. The lecture (11:03–11:11) calls the first “another big benefit” of copper, beside “lower resistance”: two separate gains, and a strap must satisfy both its electromigration limit and its drop budget.
Check yourself An aluminium strap 0.6 µm thick carries 6 mA of DC at the 2 mA/µm² limit. Find its minimum area and width, and the width in copper at 10 mA/µm².
Area 3.0 µm²; width 5.0 µm. In copper, area µm², width 1.0 µm: five times narrower.
Check yourself A signal wire's current is AC. Which limit applies, and why is it rarely the binding one?
The AC limit, about 150 mA/µm² in copper: fifteen times the DC limit, because the ions’ push alternates and mostly cancels. A signal wire’s current is set by the load it charges, and long before it nears that density the wire’s RC delay or its driver’s size has become the problem.
5. Synchronous and asynchronous design
You need
The clocked pipeline (Chapter 14). Logic sits between flip-flops on one clock; each stage must finish within one cycle, . Every stage gets the same cycle, so the clock is set by the slowest stage.
Cycle stealing (Chapter 14). With transparent latches instead of flip-flops, a slow stage can borrow time from the next, so the cycle is set closer to the average than to the worst stage.
The question. Every circuit so far has run on a clock. Is there another way to sequence logic, what does it gain, and why does almost every chip still use a clock?
Two ways to sequence logic (board, 14:07–17:21)
- Synchronous board (14:07–14:40). The logic is “sequenced by a special control signal”, the clock, and that signal is global: one clock reaches every flip-flop.
- Asynchronous board (15:00–15:47). There is no clock. The control signals are local: each stage talks only to its neighbours by handshaking, most commonly a “four-phase handshaking protocol” (15:13). added In a four-phase handshake the sender raises request when its data is ready; the receiver takes the data and raises acknowledge; the sender drops request; the receiver drops acknowledge, and the pair is ready for the next item.
- What it costs (15:39). “The control overhead is high”: added two extra wires and four transitions for every transfer, and the circuitry to make them.
- What it gains (15:55–16:24). No global clock to distribute, so none of the problems of Sections 6–10. And each stage proceeds as soon as it is done, so the pipeline runs at the average stage delay rather than the worst case.
- Why the clock wins (16:24–17:19). Synchronous designs recover part of that gain with cycle stealing, and asynchronous techniques (self-timed circuits) are used inside synchronous chips where they pay. Synchronous design “tends to win the day” because it is so much easier to design and verify.
Synchronous against asynchronous sequencing added, after the board (Lecture22 @ 17:21). (a) One global clock sequences every register. (b) A four-phase handshake: (1) req rises with the data, (2) ack rises once the receiver has it, (3) req falls, (4) ack falls; only then can the next item go.
The board (Lecture22 @ 17:21)

Fair copy of the board above (Lecture22 @ 17:21), mark for mark in its own layout, all in black: a pale blue pen wrote the board (“Clocking” is the heading in the pink-violet pen, “Lecture 22” the opening board’s cyan title). The start of “control signals” and the arrow before it, behind the lecturer’s hand, are restored from 17:44. “sequences”† is a slip for “sequenced”: the speech says “sequenced by a special control signal” (14:25).
A worked example: three stages (added; illustrative delays)
- The stages. Three logic stages take 300, 500 and 400 ps. Follow one data item through all three.
- Synchronous. With flip-flops, every stage gets the cycle the slowest needs: 500 ps of logic plus the flip-flop overhead (). With 100 ps of overhead, for example, the clock is 600 ps per stage, and the item takes 1,800 ps to pass the three stages.
- Asynchronous. Each stage hands its result on when it is done. With 150 ps of handshake per stage, for example, the item takes 1,650 ps: on average 400 ps of logic plus 150 ps, 550 ps per stage.
- The comparison. The asynchronous pipeline is faster, but only by 50 ps a stage, and the margin vanishes if the handshake costs a little more or if the stages are better balanced.
- What the average does not set added. With these fixed delays, a simple asynchronous pipeline can accept a new item only as fast as its slowest stage finishes a transfer, 650 ps, against the clock’s 600 ps: its rate is no better. The average-delay gain the lecture names is real when a stage’s delay changes from one data item to the next: each item then takes only as long as it needs, while a clock must always allow for the worst case.
Traps.
- Two meanings of “asynchronous”. Here it is a design style with no clock. Chapter 13’s “asynchronous set and reset” are inputs that act on a flip-flop without waiting for the clock edge.
- “Asynchronous is always faster.” It runs at the average delay plus the handshake; with balanced stages, the clock’s single overhead can win.
Check yourself What does the four-phase handshake's return to zero cost?
Two of its four transitions (req falling, then ack falling) carry no data: they only reset the wires for the next transfer. Each transfer therefore waits for two extra wire delays and two extra logic responses, which is the control overhead the lecture names.
Check yourself In the example, suppose the stages are retimed to 400, 400 and 400 ps. Compare the two pipelines with the same overheads.
Synchronous: 500 ps per stage. Asynchronous: average 550 ps. With balanced stages, the average equals the worst, the asynchronous design loses its only advantage, and the handshake makes it slower.
6. Judging a clock network: skew, jitter, power and latency
You need
What skew costs (Chapter 14). Between a launching and a capturing flip-flop, let the capturing clock arrive later by a signed skew . The long path then needs , and the short path needs . A skew that helps one check hurts the other. Jitter, a clock edge that moves from one cycle to the next, is taken as skew in whichever direction hurts.
The supply sensitivity of delay (Chapter 21; FS1’s FN10-6). Write a gate’s delay as and define , the fractional change of delay per fractional change of supply. (Chapter 21 and FS1 call it ; this chapter writes to keep it apart from the subthreshold slope of Sections 12–16.) For a small change, . With the velocity-saturated delay (Chapter 5), : negative, since a lower supply is slower. Only the gates’ (silicon) delay depends on ; a wire’s RC delay does not.
The question. Chapter 14 took the skew as given. Where does it come from? What should a clock network be judged by, and why does the lecture single out its latency, which affects every flip-flop the same way?
The four metrics (board, 17:55–21:35)
- The ideal (18:03–18:29). Drive the clock from one point and reach every flip-flop at exactly the same instant: zero skew.
- Skew board: “static differences in arrival time”. Two flip-flops’ clocks arrive at different times, by the same amount every cycle.
- Jitter board: “transient differences in arrival time”. The clock edge “can move around”: “one cycle can be shorter, another cycle can be longer”.
- Power board. The clock net switches every cycle and drives every flip-flop, so it is one of the biggest consumers on the chip (Sections 8 and 12).
- Latency board: “the delay of the clock network”, from its root to a leaf flip-flop. Call it added.
- Why latency matters (19:43–20:16). If every flip-flop’s clock arrives late, the edges still arrive together; so why care? Because “if I have a large latency in my clock distribution network, that’s going to translate into skew and jitter.”
- Where the spread comes from (20:16–21:13). Across the die, process, supply and temperature are not uniform. A static difference (a slow region, a lower local supply, a hot spot) makes two nominally equal paths differ by the same amount every cycle: skew. A transient one (supply noise that changes from cycle to cycle) makes the same path differ from one edge to the next: jitter.
- So keep it short (21:13–21:35). “The more latency I have, the more sensitivity I have in my clock network to transient and static variation … process, temperature, and voltage to produce skew and jitter.”
Latency turns variation into skew and jitter added, after the board’s definitions (Lecture22 @ 21:57). (a) Every leaf’s clock comes after the root’s. One buffer on B’s branch sees a lower supply. (b) A static difference delays clkB by the same every cycle: skew. A supply that varies from cycle to cycle moves clkB’s edge within a band: jitter.
The board (Lecture22 @ 21:57)

Fair copy of the board above (Lecture22 @ 21:57), mark for mark in its own layout, all in black: a pale blue pen wrote the list (“Clocking” is the pink-violet heading, “Lecture 22” the opening board’s cyan title). “skew”, washed out behind the lecturer’s head, is restored from 20:41. The four ditto marks after “transient” repeat “differences in arrival time”. “Two strategies ⇒ clock d” is still being written; it becomes “clock distribution” by 22:29 and is copied only as far as written here. This is the only frame with the skew and jitter definitions: they are wiped by 24:48.
How much skew and jitter a latency makes
The lecture argues in words. One added step added puts a size on it, using only Chapter 21’s sensitivity.
From a supply change to a spread in arrival time (added)
- One buffer. A fractional supply change changes a buffer’s delay by the fraction (Chapter 21).
- A whole path. Every buffer on the path from the root to a leaf sees the same change, so the path’s delay changes by the same fraction: . The change is a fixed share of the latency.
- Static: skew. If the change is static and only one branch sees it, that branch’s leaves arrive later by every cycle.
- Transient: jitter. If the change is a droop that comes and goes, the same leaf’s edge moves by between cycles.
- The result. Both are proportional to the latency. Halve and the same variation makes half the skew and half the jitter.
Derive it in three lines: one buffer’s ; every buffer on the path sees it; sum along the path, so . FS1 uses exactly this for FN10-6c (FS1, FN10-6c); that part is solved there and not here.
A worked example: a 1 ns network and a 400 ps one (added; values for example)
- The devices. For example, = 1.0 V and = 0.3 V. Then −0.4286: a 1 % lower supply makes every buffer 0.43 % slower.
- A 1 ns network, static. One side of the die sits at a supply 5 % lower. The leaves there arrive later by ps 21.4 ps: skew.
- A 1 ns network, transient. A droop of 8 % comes and goes with the activity. The edge moves by ps 34.3 ps: jitter. The exact model, evaluated at 0.92 V against 1.0 V, gives 38.7 ps: first order is a little low for an 8 % change.
- A 400 ps network. The same variations give 8.6 ps of skew and 13.7 ps of jitter (exactly 15.5 ps): 0.4 times as much, in proportion to the latency.
Skew and jitter grow in proportion to the latency added, computed from with ( = 1.0 V, = 0.3 V): an 8 % transient droop (solid, jitter) and a 5 % static difference (dashed, skew). The 400 ps network has 0.4 times the 1 ns network’s skew and jitter.
Check. At the 1 ns network, the ratio of jitter to skew is , the ratio of the two variations (): the formula is linear in the variation as well as in the latency.
Why it matters added. Every picosecond of skew and jitter comes off the setup margin of the long path and the hold margin of the short path (Chapter 14). A lower latency also needs fewer buffer stages, which cost clock power.
Memorize the four, with the lecture’s argument in one line: latency turns process, voltage and temperature variation into skew and jitter, so keep it low. That is FN17-1d’s answer.
Traps.
- “Only skew matters.” Jitter cannot be tuned out by design, because it changes every cycle.
- One buffer’s delay. The spread scales with the whole root-to-leaf latency, not with the delay of the last buffer.
- “A latency that is the same everywhere is harmless.” Only while nothing varies; every variation acts on all of it.
- and . The supply sensitivity is a negative number without units; the subthreshold slope is in mV per decade.
Check yourself Name one static and one transient source of variation, and the metric each produces.
Static: a process gradient across the die, a region with a lower average supply (IR drop), or a hot spot; each makes one branch consistently slower: skew. Transient: supply noise from when a block switches on; it slows the same branch on some cycles and not others: jitter.
Check yourself A 1.2 ns clock tree at 1.0 V (VT = 0.3 V) sees a 6 % droop on one branch only, coming and going. Estimate the jitter between leaves on the two branches; then for a 600 ps tree.
. The droop slows the drooping branch by ps 30.9 ps while the other is unchanged, so the edges on the two branches move apart by that much from cycle to cycle. Halving the latency halves it: 15.4 ps.
Check yourself Why does a lower supply, closer to VT, make the same network jitter more?
grows as approaches : at 1.0 V it is 0.43, at 0.6 V it is 1.0. Each buffer’s delay becomes more sensitive to the same fractional droop, so the same latency turns it into more jitter.
7. Two strategies: minimum latency or active deskew
You need
Latency into skew and jitter (Section 6). A variation that changes every buffer’s delay by a fraction moves a leaf’s clock by , where is the root-to-leaf latency; for the supply, with . Static variation gives skew; transient variation gives jitter.
A feedback loop added (circuits background). A loop measures an error (here, the difference between two clocks’ arrival times), and a controller adjusts something (here, a delay) to drive the error toward zero. It can follow changes slower than its own response time, not faster ones.
The question. Given that latency breeds skew and jitter, there are two ways to fight them: build the network so its latency is small, or measure the skew and cancel it. What does each involve, and what can each not do?
Two strategies (board, 21:52–26:48)
- A simple clock network board (21:52–23:47). Only buffers and wires. (The lecturer starts to call it “passive”, then corrects himself: the buffers are active devices, so “let me just call it simple clock network”.) Many levels of buffers are still needed, because the total load of all the flip-flops is enormous.
- Its goal: minimize latency board (24:11–24:38). “The best way to deal with skew and jitter in my clock distribution network is to just minimize the latency … Just keep the latency low.”
- Active deskewing board (23:47–25:36). Build programmable delay lines into the network, measure the skew between regions, and set the delays to cancel it. With a feedback loop running all the time, it can also track some slow, transient variation.
- Its cost (25:41). “The problem with these delay lines, of course, is that they’re adding latency.” The delay lines are themselves buffers whose delay varies, and the loop must correct that too.
- Who did which board (26:00–26:48). As the lecturer recalled it at the recording: IBM used the simple network, Intel active deskewing. Both still build their networks from buffers and wires (Sections 8–10).
- What deskew can and cannot fix added. It removes static skew and slow drift (process, temperature, the average supply). It cannot remove jitter faster than its loop responds, and the latency its delay lines add makes that jitter larger.
The two strategies added, after the board (Lecture22 @ 27:16). (a) A simple network of buffers and wires, designed for the least latency . (b) Active deskew: programmable delay lines () before the leaves, a phase detector (PD) comparing two regions’ clocks, and feedback that sets the delays to cancel the difference.
The board (Lecture22 @ 27:16)

Fair copy of the board above (Lecture22 @ 27:16), mark for mark in its own layout, all in black: one pale blue pen wrote the board. The underline of “Lecture 22” is the cyan title pen, and “minimize latency” is the pink-violet pen, a single note written in the run of the blue writing (24:11–24:38), not a separate layer. The definitions of skew and jitter were wiped earlier; only their arrows remain. The right side of the skew and jitter box and the start of “Clocking”, under the lecturer’s hand, and “Intel”, under his sheet of paper, are restored from 26:48. On the last line “clock network” is set a size smaller so that it stays inside its box.
A worked example: what deskew buys (added; values for example, from Section 6)
- The network. Section 6’s 1 ns network at 1.0 V (): a 5 % static difference gives 21.4 ps of skew, an 8 % droop 34.3 ps of jitter.
- Deskew it. The loop cancels the static 21.4 ps. Suppose its delay lines add 200 ps to every path, for example. The latency is now 1.2 ns.
- The jitter grows. The droop comes and goes faster than the loop follows, so it is not cancelled; it now acts on 1.2 ns: ps 41.1 ps, up from 34.3 ps.
- The simple alternative. A 400 ps network with no loop has 8.6 ps of skew and 13.7 ps of jitter (Section 6). If such a network can be built, it beats the deskewed one on both counts.
Traps.
- “Deskew removes jitter.” It removes what its loop can follow: static skew and slow drift. Fast jitter remains, and grows with the added latency.
- Forgetting the delay line’s own latency. Every programmable delay is a chain of buffers on the clock path.
Check yourself Why do both companies still care about the buffer-and-wire network underneath?
Deskewing only corrects what the network does wrong. The network still carries the clock with all its latency to every flip-flop; its latency still sets the jitter the loop cannot follow, and its power is the same. A deskewed network that starts from a long latency ends with a lot of jitter.
Check yourself A deskew loop's delay lines add 300 ps to a 700 ps network at 1.0 V (VT = 0.3 V). Find the jitter from an 8 % droop before and after.
. Before: ps 24.0 ps. After, with 1000 ps of latency: 34.3 ps. The loop has removed the static skew, at the price of 43 % more jitter.
8. Clock grids
You need
Power grids (Chapter 21). The supply is spread over the chip by a mesh of straps on every metal layer. Many parallel paths between any two points give a low resistance and a low inductance, so the voltage is nearly the same everywhere.
Driving a big load (Chapter 8). A small signal drives an enormous capacitance through a chain of inverters, each a few times (about four times) larger than the one before.
Clock power (Chapter 6). Charging a capacitance to draws from the supply. A clock node rises once every cycle, so a clock network of capacitance at frequency burns .
The question. A supply grid keeps the voltage nearly equal everywhere because it is a mesh with low resistance. Could a clock be distributed the same way, so that it arrives nearly at once everywhere? What does such a clock grid buy, and what does it cost?
The clock grid (board, 27:52–31:57)
- Borrow the power grid’s idea (27:52–28:20). Low resistance and inductance spread the clock uniformly across the chip: a grid.
- The DEC Alpha board (28:28–29:42). The quintessential example, as the lecturer recalled it: the DEC Alpha processor of the early 1990s used one grid for the whole chip. All the buffering sat up front, a chain of inverters growing in size, and the final inverter was “distributed over the entire spine”: one huge driver laid out along a strip across the middle of the chip, with an effective width the lecturer recalls as “like two centimetres or something”.
- Why it has little skew (29:42–30:09). There is little RC or LC delay across the grid, so when the spine switches, “this whole grid would come along with it”: every flip-flop sees nearly the same edge, out to the periphery.
- Its plus board (30:41–31:35). Insensitive to the details of loading: a flip-flop can be added late, anywhere, without retuning anything.
- Its two minuses board. It uses a lot of wiring resources, and it has a lot of capacitance, so it is power-hungry.
- Since then (31:53). As the lecturer told it, pure grids have not been used much since the Alpha.
A clock grid board, redrawn (Lecture22 @ 31:57; begun at 29:04). A chain of growing inverters drives one huge final driver laid along the hatched spine (the DEC Alpha’s, as the lecturer recalls it, “like two centimetres” wide); the spine drives the whole grid; the small marks are flip-flops tapping the grid wherever they sit.
The board (Lecture22 @ 31:57)

Fair copy of the board above (Lecture22 @ 31:57), mark for mark in its own layout, all in black: one pale blue pen wrote the board, and the underline of “Lecture 22” is the cyan title pen. “network”, “Grid” and the left of the list, behind the lecturer’s head and arm, are restored from 37:14, where the left half is unchanged and clear. The hatched strip is the spine, the distributed final inverter; the small marks at the nodes are flip-flops tapping the grid. “wiring resources” starts a little left of the board’s, for the wider typeset words.
A worked example: the price of a grid (added; values for example)
- The chip. A square die = 10 mm on a side, with a clock grid of pitch = 1.25 mm.
- The wire. The grid has lines in each direction, each 10 mm long: 180 mm of clock wire.
- Its capacitance. At 0.2 fF/µm (an illustrative wide clock wire), 36 pF, before a single flip-flop is connected.
- Its power. At 1 V and 2 GHz, 72 mW for the bare grid.
Check. Each line of the grid is a full 10 mm long, and nine lines each way make 18 lines: 180 mm, as counted.
Traps.
- “A grid has no skew.” It has little, because the resistance between its taps is low, not zero; the corners farthest from the spine still lag.
- “Its capacitance is free because it is only wire.” Every millimetre switches every cycle; the wire is a large share of the clock’s power.
Check yourself Why is a grid insensitive to where the loads are?
Between any two points there are many parallel paths with low resistance, so a flip-flop added at one node draws its charge from all around it, and the node’s delay barely moves. In a tree, by contrast, the same load hangs on one branch and slows only that branch.
Check yourself Halve the grid pitch in the example to 0.625 mm. How much clock wire, and how much power for the bare grid?
lines each way: 340 mm, so 68 pF and 136 mW at 1 V and 2 GHz: 1.89 times as much: not quite twice, because the number of lines goes from 9 to 17 each way, not to 18.
9. H-trees, and tuning wire for wire
You need
The delay of a driven load (Chapter 20). A driver of resistance charging a lumped capacitance has an Elmore delay ; add to the load and the delay grows by .
Latency into skew (Section 6). A variation that changes a delay by a fraction acts on the whole delay it touches: for the supply, with .
Only silicon moves with the supply (Chapter 21). A buffer’s delay depends on ; a wire’s RC delay does not, though it does change with the wire’s own process corner and temperature.
The question. Instead of a grid, a clock can be sent along a tree whose every path from the root to a leaf is the same. How is such a tree built, why is it sensitive where the grid was not, how is it tuned, and what does it save?
The H-tree (board, 32:21–36:56)
- Nested H’s board (32:21–33:18). Draw an H across the chip with the clock driven at its centre. At each of its four tips, draw a smaller H, and so on. By symmetry, “the wire length … to any leaf node is always exactly the same”: the ideal of zero skew, built into the geometry.
- Buffers in the tree board (33:18–33:40). The buffers are spread through the tree (the lecturer calls them sector buffers), at the centre of each H, not all at the root.
- Its big minus board (33:52–34:19). High sensitivity to loading. The wires are equal, but the loads at the leaves are not: if one leaf has more flip-flops, its branch is slower. So the tree must be tuned: buffer sizes, wire lengths and widths adjusted until the arrivals match, and retuned after every late change.
- The tuning rule board (34:33–35:28). “Wire delay and silicon delay have very different … PVT tracking properties … when I tune it, I tune wire for wire, silicon for silicon.” Two branches with equal total delay but a different mix of wire and buffer delay drift apart as soon as the voltage, temperature or process moves.
- Its pluses board (35:46–36:16). Stingy in its use of wires, and so lower capacitance.
- The minus is serious (36:16–36:56). Loads change “up until the last minute” of a design, and retuning a tree that is already routed around blockages is hard.
A two-level H-tree board, redrawn (Lecture22 @ 37:14; drawn 32:21–33:40). Buffers sit at the centre of every H. Every path from the root to one of the 16 leaves has the same length: the thick path runs on the first H and on the second (dimensions added).
The board (Lecture22 @ 37:14)

Fair copy of the board above (Lecture22 @ 37:14), mark for mark in its own layout. Black is the pale blue pen: the grid board kept at the left, “Trees”, “H-trees”, the H-tree and its root buffer (the underline of “Lecture 22” is the cyan title pen). Magenta is the pink-violet pen, a second layer: the buffers it drew into the blue tree, drawn here as small filled triangles (one at each second-level node, three in the upper right H and a pair at seven of the lower right H’s eight tips), then “zero skew” and the list of minuses and pluses with its box. The grid’s right half, behind the lecturer’s head, is restored from 31:57; the H-tree’s left half, dimmed by his shirt, is read on 35:49. The buffer chain of 31:57 is wiped by now. The left half repeats the 31:57 copy’s marks one size smaller.
The H-tree’s wire, and the price of a late change
The path and the wire added. Take a square chip of side and a tree of levels. The first H spans the chip: its crossbar and its two uprights are each long, in all, and a path through it runs along the crossbar and up an upright. Each level halves the square, so level has H’s of total length each, and a path through level runs . Summing over the levels:
Derive it from the geometry (two geometric series); it is not worth memorizing.
A worked example: an H-tree against the grid (added; values for example)
- The same chip. = 10 mm, and a tree of = 3 levels: 64 leaves.
- The path. 8.75 mm from the root to every leaf.
- The wire. 105 mm, against the 1.25 mm grid’s 180 mm (Section 8). At the same 0.2 fF/µm that is 21 pF against 36 pF: the “stingy” tree.
- A late change. A design change adds 100 fF of flip-flops at one leaf, whose last buffer has a 500 Ω output resistance. That leaf’s clock is later by 50 ps, until the tree is retuned.
Tune wire for wire, silicon for silicon
A worked example: why the mix matters (added; values for example)
- Two branches, 500 ps each. Branch A: 300 ps of buffer (silicon) delay and 200 ps of wire delay. Branch B: 450 ps of silicon and 50 ps of wire. Nominally the clocks arrive together.
- A 10 % supply droop. Only silicon slows. With (1.0 V, = 0.3 V), silicon delay grows by %. A slows by 12.9 ps, B by 19.3 ps: 6.4 ps of skew appears.
- A slow-wire corner. Suppose the wires come out 10 % slower (a high-RC corner) while the transistors are nominal. A slows by 20 ps, B by 5 ps: 15 ps of skew, in the other direction.
- Matched branches. Tune both to 375 ps of silicon and 125 ps of wire. Under the droop both become 516.1 ps; under the slow wire both become 512.5 ps. The skew stays 0 in both cases.
Why delays are tuned wire for wire and silicon for silicon added, computed with . (a) Two branches equal in total, 500 ps, but not in kind. (b) A 10 % droop slows only the silicon: 6.4 ps of skew. (c) 10 % slower wire: 15 ps. (d)–(e) Branches matched part for part keep zero skew under both changes.
Check. The droop’s skew is the silicon difference times the fractional change: ps; the wire corner’s is the wire difference times 10 %: ps.
Traps.
- Balancing a long wire with an extra buffer. It equalizes the nominal delay and leaves the branches mismatched in kind, so they drift apart with every corner.
- “Equal wire length means equal delay.” The loads at the leaves and the buffers along the way must match too; that is the tree’s sensitivity to loading.
Check yourself Why does the tuning rule follow from Chapter 21's remark that only silicon delay depends on VDD?
A supply change scales only the buffer delays, and a wire corner scales only the wire delays. Two branches with the same silicon delay and the same wire delay change by the same amount under either; two with the same total but a different split change by different amounts, and the difference is skew.
Check yourself Give the same 10 mm chip a four-level H-tree. Find the root-to-leaf path and the total wire, and compare the wire with the grid's.
Path 9.375 mm; wire 225 mm, now more than the 1.25 mm grid’s 180 mm. Each level doubles the wire, while the path only approaches .
Check yourself In the examples, which does the tree more harm: the late 100 fF load or the 10 % droop on unmatched branches?
The late load: 50 ps of skew, against 6.4 ps from the droop. A load change acts on the whole RC of one branch at once, while the droop acts only on the silicon difference between branches. That is why the H-tree’s minus is its “sensitivity to loading”.
10. Tree-driven grids
You need
The grid (Section 8): a low-resistance mesh, insensitive to where the loads are, but heavy in wire and capacitance.
The H-tree (Section 9): equal paths to every leaf and little wire, but sensitive to the loads at the leaves, so it must be tuned and retuned.
The question. Each pure network has one serious minus. “Is there a way I can combine these two?” (36:56)
The tree-driven grid (board, 36:56–39:39)
- Where things have wound up (36:56–37:23). As the lecturer told it at the recording, both Intel and IBM use tree-driven grids, and Intel adds deskewing (Section 7).
- The structure board (37:42–38:48). A tree delivers the clock, with equal paths, to many taps spread over a grid. Because the grid is driven at many points, it can be much lighter than a pure grid.
- Why it works (38:48–39:09). The grid shorts the taps together and averages out the “loading inhomogeneities”: a load added late, between taps, is shared by the taps around it, so the tree need not be retuned.
A tree-driven grid board, redrawn (Lecture22 @ 39:39; begun at 38:36). A two-level H-tree delivers the clock to 16 taps (dots) on a lighter grid, which shorts the taps together. The board draws two of the tap dots; all 16 are drawn here. The grid is drawn with 8 × 8 cells so that the taps fall on its nodes (the board’s has about 7 × 5).
The board (Lecture22 @ 39:39)

Fair copy of the board above (Lecture22 @ 39:39), mark for mark in its own layout. Black is the violet pen: the rounded rectangle, the grid (seven columns, six rows) and “Tree-driven grid”; “Clock network” (pale blue) and “Lecture 22” (its underline the cyan title pen) are kept from the earlier boards. Orange is a pale pink-white pen, a second layer: the tree drawn over the grid, its two tap dots and the underline of “Tree-driven grid”. The tree is copied stroke by stroke as the hand drew it, nested H’s with short ticks at their tips, not tidied into a regular H-tree. Nothing is hidden: the lecturer stands behind the strokes (the grid checked on 38:36). The grid’s second line from the top starts only at its middle, as on the board.
A worked example: a lighter grid (added; values for example, from Sections 8–9)
- The tree. On the same 10 mm chip, a two-level H-tree reaches 16 taps with 45 mm of wire. The taps sit at the centres of a 4 × 4 array of 2.5 mm squares.
- The grid. Run a grid line through each row and each column of taps: 4 lines each way, 10 mm long, pitch 2.5 mm: 80 mm of wire.
- The total. 125 mm: more than the 105 mm three-level tree, but well under the pure 1.25 mm grid’s 180 mm.
- How far from a tap. Along any grid line the taps are 2.5 mm apart and the outermost taps sit 1.25 mm from the edge, so no point of the grid is more than 1.25 mm of wire from a tap. A late load anywhere is close to a driven point and shares its charge with the taps around it.
Traps.
- “The grid removes the need for a balanced tree.” The taps must still receive their clock together; the grid only absorbs the differences the loads make between them.
Check yourself Which minus of each pure network does the tree-driven grid keep, and which does it drop?
From the grid it drops most of the wire and capacitance, because the grid is driven at many points and can be sparse; it keeps a little of both (the 80 mm of grid in the example). From the tree it drops the sensitivity to loading, because the grid averages the loads between taps; it keeps the need to balance the tree itself to the taps.
11. Energy-constrained design and wasted power
You need
Two kinds of power (Chapter 6). Switching a node of capacitance at frequency costs (dynamic power). In either state, one transistor of a static gate is off with across it and leaks a current , which costs all the time (leakage power).
Why power became the limit (Chapter 4). Under Dennard scaling the supply fell with the dimensions and power density stayed constant. The threshold could not keep falling without leakage exploding (tenfold per subthreshold slope , about 60–100 mV), so the supply stopped scaling, and power density rose with every generation.
The question. Once the supply stopped scaling, a chip’s power became a hard limit. What sets the limit, and where does the first, easiest saving come from?
Power as a constraint (board, 40:18–44:43)
- The name board (40:18). “Low-power design”, which the lecturer calls better named energy-constrained design: the goal is not to be slow, but to do each operation with as little energy as the power budget demands.
- What changed (40:32–41:34). Power used to be whatever the design came out at. When supplies stopped scaling, power density and chip power rose, and now packaging sets the limit: how much heat the package and the cooling can carry away.
- The numbers board (41:34–41:51). The lecturer’s “Dell’s law”: spend no more than $25 on packaging and power supply, which puts a desktop processor at about 100 W. Mainframes, with expensive packaging and cooling, go to 300 W and up.
- Useful and wasted power board (42:49–43:30). Some power does useful work; some is wasted. The wasted power has two sources: leakage of blocks that are not being used, and clocking blocks that aren’t being used.
- The lowest hanging fruit (43:38–44:09). Removing wasted power costs no performance, so it comes first: every processor does it (Section 12).
- Leakage in an active block (44:09–44:43). In a block that is working, leakage cannot be avoided: in an optimal design it is, the lecturer says, about 30 % of the block’s power. (Said, not derived. Section 16 finds a different share in a different optimization.)
Where power is wasted added, after the board’s list (Lecture22 @ 47:42). Two blocks are working (shaded) and two are idle. An idle block still leaks ( from ), and if its clock still toggles (clk), it still charges its clock load every cycle. The AND gate at each block’s clock input is where clock gating acts (Section 12).
A worked example: a power budget (added; values for example)
- The budget. A 100 W processor at 1.0 V.
- An active block. Its switching power is 7 W. If leakage is 30 % of its total, as the lecture says of an optimal block, the total is 10 W and the leakage 3 W. That leakage is the price of a fast block, not waste.
- An idle copy. A second copy of the block with nothing to do still leaks its 3 W, and if its clock keeps running it also burns its clock power, every cycle. Both are waste, and both can be removed (Section 12).
Traps.
- “Low-power means slow.” The constraint is energy per operation inside a power budget; the design is still as fast as the budget allows.
- “All leakage is waste.” Leakage in a block that is working is the cost of its speed; only the leakage of idle blocks is wasted.
Check yourself Why does leakage in an idle block count as wasted, while leakage in an active block does not?
An active block’s leakage comes with the low threshold that makes it fast; removing it would cost speed. An idle block does no work at all, so any power it draws, leakage or clocking, buys nothing, and turning it off costs nothing but the time to turn it back on.
Check yourself Why does packaging, not the transistors, set a desktop processor's power near 100 W?
The transistors would happily burn more. What limits a chip’s power is how much heat can be carried away and at what cost: the package, the heat sink and the power supply. The lecturer’s “Dell’s law” caps that cost, and with it the power; a mainframe, which can afford more cooling, goes past 300 W.
12. Power gating and clock gating
You need
Leakage and the threshold (Chapter 4). Below threshold a transistor’s current falls tenfold for every of gate voltage, where is the subthreshold slope (60 mV/decade at best, 80–100 in real devices). A device’s off current scales as , so raising by cuts its leakage by .
On-resistance (Chapter 7). A transistor’s on-resistance falls as its width grows: , with in kΩ·µm.
Local clock generators (Chapter 14). The global clock is one wire; near the flip-flops, local generators make the phases the latches need (, ).
Clock power (Section 8): .
The question. Section 11 named two wastes: an idle block’s leakage and an idle block’s clock. How is each switched off, and what does each switch cost?
Two kinds of gating (board, 44:50–47:42)
- Power-supply gating board (45:06–45:23). Put a switch between and the logic block, driven by a control signal (the board’s “ctl”). When the block is idle, open the switch: the block’s supply collapses and it stops leaking.
- What kind of switch board (45:23–45:48). A high- device, so that the switch itself leaks little when it is off; and a big device, so that it drops little voltage when it is on and the block’s speed does not suffer. Its large gate capacitance does not matter, because it is switched rarely: “not doing this very often”.
- Where the clock ends (46:20–46:51). Clock distribution ends at local clock generators, which make and from the single-wire global clock.
- Clock gating board (46:51–47:22). In the local generator, AND the clock with a gate signal. With gate = 0 the local clock stops: nothing is launched, no logic evaluates, and the clock load stops switching.
Gating board, redrawn (Lecture22 @ 47:42). (a) Power-supply gating: a high-threshold, wide PFET header (the board’s “high VT, big device”), driven by ctl, between and the logic block; the node below it is the block’s virtual supply (label added). (b) Clock gating: clk AND gate drives the local clock generator, which makes and (added, from 46:20).
The board (Lecture22 @ 47:42)

Fair copy of the board above (Lecture22 @ 47:42), mark for mark in its own layout. Black is a pale pink-white pen: the text from “Low-power design” down to the list of wasted power, “non being used” with its arrow to “leakage”, and a first underline under “clocking blocks that aren’t being used” (“Lecture 22“‘s underline is the cyan title pen). Teal is the cyan pen, a second layer: the remedies, drawn from 44:57 on. They are the long arrow from “non being used” to “power supply gating”; the ringed header PFET with “ctl”, “high VT” and “big device”, the logic block and its ground; and the cyan underline traced over the pale one, its double arrow, “clock gating” and the ringed AND of clk and gate. † “non” is the board’s slip for “not”: the speech says “a block that’s not being used” (44:43–44:50). There the hand runs the i and n of “being” together; it is set as “being”. Nothing is hidden: the lecturer stands behind the strokes (the list checked on 45:18 and 46:23). Where the typeset words run wider than the hand’s they are spread a little, and the AND gate sits slightly right of the board’s to clear its labels.
Derive each: Ohm’s law for the header; the subthreshold line for the leakage; for the clock.
A worked example: sizing a header and gating a clock (added; values for example)
- The block. For example, it draws 100 mA at 1.0 V, and the header may drop 2 % of the supply, 20 mV.
- The header’s resistance. 0.20 Ω.
- Its width. With a high- PFET of 2 kΩ·µm (illustrative), 10,000 µm: a centimetre of transistor width, “a very big device”.
- Its own leakage. At = 90 mV/decade, a threshold 100 mV higher than the logic’s cuts the switch’s leakage by 12.9 times; 150 mV higher, by 46.4 times.
- Clock gating. The block’s clock load is 200 pF; at 1 V and 2 GHz it burns 0.40 W. If the block is idle 70 % of the time, gating its clock saves 0.28 W.
Check. The header’s drop at full current is mV, the allowed 2 %; a header half as wide would drop 40 mV and slow the whole block.
Traps.
- A low- switch. It would leak almost as much as the block it is meant to turn off.
- A small switch. Its IR drop lowers the block’s supply, and Section 6’s sensitivity turns that into delay.
- A glitchy gate signal. If gate changes while clk is high, the AND passes a truncated pulse. The gate signal must change only while clk is low added (the same care as Chapter 14’s clock chopper).
Check yourself Why may the header's gate be slow?
The block is put to sleep and woken rarely, on a scale of microseconds or more, so the header’s huge gate capacitance is charged rarely too; its energy and its delay are paid once per sleep, not once per cycle.
Check yourself The block draws 250 mA and may drop only 1 % of 1.0 V. Find Ron and the header width at 2 kΩ·µm.
0.04 Ω; 50,000 µm, 5 cm of width: five times the example’s, because the current is 2.5 times larger and the allowed drop half as big.
Check yourself Which gating saves leakage, and which saves dynamic power?
Power-supply gating removes the idle block’s leakage (and, with its supply gone, everything else it draws). Clock gating removes the idle block’s dynamic power: its clock load and the logic the clock would have made switch. Clock gating does nothing for leakage, because the block is still powered.
13. The energy–delay curve: VDD as the knob
You need
Switching energy (Chapter 6). Each time a node of capacitance rises, the supply delivers (half stored on , half lost in the PFET). So the dynamic energy per operation goes as . Leakage power is , linear in at a fixed leakage current.
The supply and the delay (Chapter 5). A gate’s delay is about the charge it moves over the current that moves it, . With the velocity-saturated current , : the delay rises as falls, without limit as approaches .
The question. A design can be made faster by spending more energy, or frugal by accepting more delay. What does the set of the best possible designs look like, and which knob moves a design along it?
The energy–delay curve (board, 48:13–52:32)
- The axes board (48:13–48:48). Delay on the vertical axis, energy (per operation) on the horizontal one. A task done with little energy takes a long time; done quickly, it takes a lot of energy.
- The Pareto curve board (49:18). The best designs achievable trace a curve: a Pareto curve. No design lies below and to the left of it, and a design above and to the right of it wastes energy or time.
- Two regions of diminishing returns board (49:18–49:51). Near the delay axis the curve is steep: a little less energy costs a lot of delay. Near the energy axis it is flat: a little more speed costs a lot of energy.
- How to use it (49:51–51:00). Know the workload’s deadline, sit on the curve at that delay, and burn no more energy than that point needs. Never sit off the curve.
- The knob board (51:24–51:36). “The best knob that you have to play with is the supply voltage”: “I will save dynamic power as squared, I’ll save leakage power linearly with ”, and the delay rises.
- Parallelism (52:00–52:32). Two units, each at half speed, finish the same work in the same time. Half speed allows a lower supply, so each operation costs less energy: same throughput, less power.
The energy–delay curve board, redrawn (Lecture22 @ 57:49; built 48:38–52:10). Delay up, energy across; the best designs lie on this Pareto curve, with diminishing returns at both ends. The supply voltage moves a design along it (the board’s “supply voltage ⇒ VDD”, then DVFS). The ring marks the low-energy, long-delay end, where the board writes “subthreshold” (Sections 15–16).
The board (Lecture22 @ 57:49)

Fair copy of the board above (Lecture22 @ 57:49), mark for mark in its own layout, all in black: one cyan pen wrote the whole board. Nothing is hidden: the lecturer stands behind the strokes (the axes and the curve checked on 52:10). The curve’s right end is traced twice for a short stretch, and both strokes are copied. The hand writes the two D’s of VDD as open loops that read like “nn”. A faint pale double stroke under “Energy”, left from the erased 47:42 board, is left out. Where the typeset words run wider than the hand’s, “capacitor converters” and the buck’s “converters” are set smaller, and the stroke beside the converters and the foot of the return arrow sit a little right of the board’s.
The curve from the course’s models
Memorize the first two (from Chapters 5–6). Derive the third: set and solve for .
A worked example: moving along the curve (added; V_T = 0.3 V, nominal 1.0 V, for example)
- Up the supply, to 1.2 V. Delay 0.933, energy 1.44: 7 % faster for 44 % more energy, the flat end.
- Down to 0.6 V. Delay 1.40, energy 0.36.
- Down to 0.4 V. Delay 2.80, energy 0.16: now each further saving costs a lot of delay, the steep end.
- Half speed. For : , so 0.4615 V. The energy per operation is 0.213 of nominal: a 79 % saving for twice the delay.
- Two cores at half speed. Together they give the original throughput, each operation at 0.213 of the energy: 0.213 of the dynamic power. Their leakage is another matter: each leaks at 0.4615 of the nominal voltage, but there are two, so 0.923 of one core’s leakage power.
The energy–delay curve computed from the course’s models added: and ( = 0.3 V, nominal 1.0 V), points labelled with . The hollow point is half speed, 0.4615 V, at 0.213 of the energy. The dashed line is the delay floor, 0.7, as grows without bound; the steep end climbs without bound as approaches in this model, and below threshold Sections 15–16 take over.
Check. The half-speed supply satisfies the delay ratio: , twice .
Traps.
- “Energy falls in proportion to speed.” It falls as while the delay rises as : slow by 2 for a factor of 4.7 in energy here, then much less per step near .
- Leakage energy per operation. Leakage power falls linearly with , but each operation takes longer, so the leakage energy per operation, power times time, falls more slowly and can even rise. Section 16 makes this the limit.
Check yourself Which end of the curve does a phone in standby want, and which a server in a burst of requests?
The phone in standby has no deadline worth the name: it wants the steep, low-energy end (low , long delay). The server in a burst must meet latency targets: it moves toward the flat end, buying speed with energy.
Check yourself For 70 % of the nominal speed, find the supply and the energy per operation (VT = 0.3 V, nominal 1.0 V).
70 % of the speed is times the delay. , so 0.588 V, and the energy is 0.346 of nominal: 65 % saved for 30 % less speed.
14. DVFS and on-chip dc–dc converters
You need
The knob (Section 13). Lowering cuts the switching energy per operation as and slows the gates as .
Dynamic power (Chapter 6). Energy per operation times operations per second: , with the fraction of the capacitance that rises each cycle, so power scales as for a given circuit.
The question. A chip’s workload changes from moment to moment. How does it move along the energy–delay curve at run time, and where does the variable supply come from?
DVFS and its converters (board, 52:58–55:40)
- DVFS board (52:58). Dynamic voltage and frequency scaling: set the supply and the clock frequency together, at run time, to suit the workload. A heavy workload raises and ; a light one lowers both.
- The converter board (53:17–53:59). The variable supply comes from a dc–dc converter on the chip, which steps down from the highest supply the chip receives.
- Three kinds board (54:20–55:13), named only: linear regulators (LDO, low dropout); switched-capacitor converters; and buck converters, which use inductors and reach a higher efficiency but are harder to integrate. “We’re not going to talk about these” in detail. (The lecturer’s start-up made on-chip magnetic inductors for such converters.)
- The principle of each added. An LDO is a transistor whose resistance a feedback loop adjusts so that it drops exactly ; the current through it is the load’s, so its efficiency is at most . A switched-capacitor converter shuffles charge between capacitors in two phases, giving fixed ratios such as 2:1 efficiently. A buck converter switches a node between and ground and filters it with an inductor and a capacitor; the inductor moves energy without dropping a voltage across a resistance.
- The order (55:13–55:40). First remove the wasted power (Section 12); then trade energy against delay with DVFS.
Three on-chip dc–dc converters added, after the board’s list (Lecture22 @ 57:49). (a) A linear regulator (LDO): a pass transistor in a feedback loop. (b) A 2:1 switched-capacitor converter, its switches on two phases. (c) A buck converter: a switched node filtered by and .
A worked example: DVFS with an LDO (added; values for example, from Section 13)
- The setting. The workload needs only 0.7 of the nominal clock frequency. At 0.6 V the gates are 1.40 times slower (Section 13), so they can still run at of the frequency: 0.6 V and 0.7 is a valid setting.
- The core’s power. 0.252 of its nominal dynamic power.
- The converter’s cost. An LDO from a 1.0 V input to 0.6 V passes the core’s current and drops 0.4 V across itself: its efficiency is at most 60 %, so at least 40 % of the power drawn from the input is lost.
- Still a saving. Drawn from the 1.0 V input, the core costs at least 0.42 of its nominal power. An efficient buck converter would bring that close to 0.252.
Traps.
- Frequency without voltage. Lowering alone lowers the power, but each operation still costs : the energy per operation, and so the battery’s work per task, is unchanged.
- A setting the gates cannot meet. The frequency must stay below what the gates allow at the chosen supply.
Check yourself When the workload is light, why lower VDD and not only f?
Lowering alone stretches the same energy per operation over more time: power falls, energy per task does not. Lowering as well (as far as the slower frequency allows) cuts each operation’s energy as ; that is what saves the battery.
Check yourself At 0.8 V and 0.85 of the frequency, what is the core's dynamic power relative to 1.0 V and full frequency? Is the setting valid (VT = 0.3 V)?
0.544. At 0.8 V the delay is times nominal, so the gates allow of the frequency: 0.85 is within it, so yes.
15. How low can VDD go? The functional limit
You need
Subthreshold current (Chapter 4; FN2’s conventions). Below threshold, a transistor’s current grows tenfold for every of gate voltage, where is the subthreshold slope (60 mV/decade at best, 80–100 in real devices):
with the current at . If both “on” () and “off” () are below threshold, . This line has no drain voltage in it: it assumes is large.
Where the lecture stops (55:44–56:43). Supplies now often sit “just barely above the threshold voltage”, and below , subthreshold operation is possible. The board rings the low-energy end of the energy–delay curve.
The question. added Below threshold an inverter still switches: it is just slow. But its “on” transistor is only times stronger than its “off” one, a few times rather than a million. As falls, the off device’s leakage pulls the low output up toward the middle. How low can the supply go before the output no longer reaches a valid 0? This is FN10-2c’s question.
The low output of a subthreshold inverter (added)
- Swiss watches (55:44–56:55). Operating just above is common; below it is possible, and “the Swiss have done this in watches”.
- The setting. The input is high, so the NFET is on and pulls the output down, while the PFET is off but leaks current into the output. The output settles where the two currents are equal. Above threshold the NFET wins by orders of magnitude and the output sits at 0. Below threshold it wins only by a small factor.
- Why the course’s line is not enough. In the current does not depend on . Then the NFET’s current would be larger than the PFET’s at every output voltage, even with the output at 0 V and nothing across the NFET, and no balance point would exist. A transistor with no voltage across it carries no current, so the line must be missing a factor that vanishes as .
- The drain factor (background device physics). Below threshold the current is carriers diffusing over a barrier at the source end of the channel. Carriers also diffuse back over the barrier at the drain end, which is higher by , so the back-flow is smaller by . The net current is where = 26 mV is the thermal voltage. The factor uses , not : the drain sets the barrier directly, not through the gate’s imperfect coupling. For above about = 78 mV the factor exceeds 0.95, which is why Chapter 4 and FN2 could leave it out. Near a low output, though, the NFET’s is a few millivolts, and the factor is what lets the output settle.
- The balance. Take the input from an identical stage, so a “high” input is itself only at the limit. The NFET has and ; the PFET has and . With matched devices the cancels: The left side rises from 0 with ; the right side falls to 0; they cross once.
- The limit. Call a low output valid if it is at most . Set and solve for : that supply is the functional limit . The equation has no closed form; try values of (or iterate) until the two sides agree.
- Simplifications an exam may accept; say which you use. (a) Drop the PFET’s drain factor: its is two or three at these supplies, so the factor is about 0.9, and dropping it moves the answer by a few millivolts. That leaves the one-line . (b) If the paper says the input swings rail to rail, take the NFET at and the PFET at instead.
The low output of a subthreshold inverter added, computed from the current balance with both drain factors ( = 90 mV/dec, = 26 mV, input at ). (a) At = 100 mV the NFET’s and the PFET’s currents cross at 3.50 mV. (b) The low output’s share of rises as falls and reaches 10 % at = 67.2 mV.
Derive both: the first from the two barriers (one line), the second by setting the two devices’ currents equal (two lines).
A worked example: S = 90 mV/decade (added; not an exam's numbers)
- The devices. = 90 mV/decade, = 26 mV, matched NFET and PFET.
- One supply first. At = 100 mV the balance (panel a) gives = 3.50 mV, 0.035 of : a comfortable 0.
- The limit. Trying supplies: at 60 mV the low output is 0.127 of (too high); at 80 mV, 0.066 (fine). In between, it is exactly 0.1 at = 67.2 mV.
- The on/off ratio there. 5.59. At the limit the “on” device is less than six times as strong as the “off” one.
- The other readings. Dropping the PFET’s drain factor (simplification a) gives 70.3 mV; a rail-to-rail input (b) gives 57.5 mV. The reading matters by several millivolts, so state it.
- A better device. With an ideal 60 mV/decade slope the limit falls to 50.3 mV.
Check. At the limit both currents should agree: with = 67.2 mV and = 6.72 mV, the NFET side is , and the PFET side .
Traps.
- The drain-independent line. It cannot fix an output level: the NFET always wins and the output would sit at exactly 0, which a device with no voltage across it cannot do.
- Two different ratios. as defined is : one device at against . At the self-consistent operating point the ratio of the on NFET’s current (at ) to the off PFET’s (at ) is , a different number. Say which a question means.
- where belongs. The drain factor uses the thermal voltage, 26 mV; (39 mV at 90 mV/decade) is the gate’s, not the drain’s.
Check yourself Why does the drain factor matter for the low output but hardly for the delay?
While the output is switching, the NFET’s is large: from down to the 50 % point it is at least , several for supplies above about 150 mV, and the factor is close to 1. It only bites in the last few of the swing, which is exactly where the low output settles.
Check yourself At VDD = 80 mV and S = 90 mV/decade, is the 10 % condition met?
The balance gives a low output of 5.27 mV, 0.066 of : below 0.1, so yes. That fits the limit at 67.2 mV: 80 mV is above it.
Check yourself How does a better slope (60 mV/decade) move the limit, and why?
Down, from 67.2 to 50.3 mV. A steeper subthreshold line gives the on device more advantage per millivolt of supply ( grows faster), so the same on/off advantage, and the same 10 % low output, is reached at a lower supply. (At the new limit : not exactly the same ratio, because the drain factor depends on too.)
16. The minimum-energy supply
You need
Switching energy (Chapter 6). A node of capacitance that rises draws from the supply. In one transition through a chain of inverters, every other node rises: half of them.
Leakage energy (Chapter 6). Over a time , a gate whose off device leaks with across it uses . With DIBL ignored, does not depend on .
Subthreshold on-current and delay (Chapter 4; FN2’s FN17-10a–b). Below threshold . A stage driving at constant current takes to reach its 50 % point, and a chain of stages takes .
The functional limit (Section 15). Below (67.2 mV for = 90 mV/decade and = 26 mV) a gate’s low output is no longer a valid 0.
The question. added Lowering always cuts the switching energy. But below threshold every 0.1 V lost makes each operation many times slower, and the whole block leaks for that whole time. At some point the leakage energy must win. When does a lowest-energy supply exist, where is it, and when does the energy simply keep falling down to the functional limit? This is FN17-10c’s question.
Energy per operation, step by step (added)
- The block. gates, each driving . The critical path is gates deep. In one operation, a fraction of the nodes rise. (An inverter chain is the case , .)
- Dynamic energy (Chapter 6): per operation.
- The time of one operation (Chapter 4 and FN2): the critical path’s delay, It grows tenfold for every that falls.
- Leakage energy (Chapter 6): all gates leak at for the whole time : The cancels: only the ratio matters.
- The total. As falls, shrinks while the bracket’s leakage term grows: two opposing trends.
- The stationary condition. Write , so that . Then , and
- When it has a solution. The straight line starts at zero at and rises with slope ; the curve is already 7.4 there and bends up. The line first touches the curve when it is tangent, at , with . So a stationary point exists only if , that is : deep logic with low activity, where many gates leak for every one that switches.
- Which root. With there are two roots. The smaller (between and 3) is a maximum, the larger (above 3) the minimum. Below the smaller root the model’s energy falls again as the supply falls, toward 0 as ; that fall runs down through Section 15’s limit (–1.8 for these slopes, below ), and below the limit the logic no longer works. So the minimum-energy supply is the larger root if it exists, lies above , and gives less energy than does; otherwise it is itself.
- With no root (), everywhere: the energy keeps falling as the supply falls, all the way to . An inverter chain (, ) needs stages before a minimum appears; FN17-10’s chain of eight has , so its model has no stationary point at all. FT1 solves that part.
- Solving for the root. Rewrite the condition as and iterate from ; it converges for any root above 3. Then .
- A by-product. At the minimum , so leakage is the fraction of the total: about a third for . This is a different optimization from the lecture’s “about 30 % in an optimal design”, which is about active blocks above threshold; the two numbers are not the same result.
The pieces of the energy model added. The operation’s time is set by the gates on the critical path, each charging its with ; meanwhile every one of the block’s gates leaks through its off device.
When a minimum-energy supply exists added, on a log scale: the stationary condition , , has two roots when ( = 75: a maximum at = 2.110 and the minimum at 5.598), touches at when , and has none for = 4.
Derive (steps 2–5, three lines) and the condition (step 6, one differentiation). Memorize the existence test , and with it the rule: no root, go to the functional limit.
A worked example: deep logic with low activity (added; not an exam's numbers)
- The block. = 90 mV/decade, logic depth = 30, activity = 0.1.
- The test. 75, above : a minimum exists.
- Iterate. . From : , , , and so on to = 5.598.
- The supply. 218.8 mV.
- The energy around it, as in units of V²: 12.61 at 100 mV, 7.60 at 200 mV, 7.45 at 218.8 mV, 7.81 at 250 mV, 9.63 at 300 mV, 16.09 at 400 mV. A shallow minimum: ±15 % in supply costs a few percent of energy.
- Against the functional limit. At = 67.2 mV (Section 15, the same slope) the energy is 12.59: higher than 7.45, so the stationary point is the answer.
- The leakage share. 35.7 % of the energy at the minimum.
- For contrast: a short, busy block. = 10 and = 0.5 at the same slope give = 5, below : no minimum. The energy falls with the supply, from 8.87 at 100 mV to 6.31 at = 67.2 mV, and the minimum-energy supply is itself.
Energy per operation against added, computed from with = 30, = 0.1, = 90 mV/dec: the minimum is V² at 218.8 mV. Below = 67.2 mV (shaded) the model’s energy falls again, but the logic no longer gives valid levels there.
Check. At the minimum the leakage-to-dynamic ratio should be ; directly, .
Traps.
- Energy written as a charge. and are charges; energy is charge times , so both terms carry a , and the energy carries . Dropping it moves the “minimum” to a different supply.
- A root that is not the answer. Check that the root is the larger one (a minimum), that it lies above the functional limit, and that it beats .
- Two different s. The operation’s time is set by the critical path’s depth ; the leakage comes from all gates of the block.
- Mixing delays. Use the 50 % delay or the full-swing time throughout, not one in each term; with the full swing, .
Check yourself Why does Ioff cancel from the leakage energy per operation?
The leakage current is proportional to , but the operation’s time is inversely proportional to , so it is inversely proportional to too. Their product, the leaked charge per operation, depends only on the ratio .
Check yourself Halve the activity in the example to α = 0.05. Find K, u and Vmin. Why does the minimum move up?
150; the iteration gives = 6.519; 254.8 mV. With half as many nodes switching, the leakage of the whole block weighs twice as much against the switching energy, so it pays to raise the supply and finish each operation sooner.
Check yourself A block with N = 50, α = 0.2 and S = 80 mV/decade: does a minimum exist, where is it, and what share of the energy is leakage there?
62.5, above 20.1: yes. The iteration gives , so 185.6 mV, and leakage is 37.4 %. (At this slope is about 62 mV, where is V² against at the minimum: the minimum stands.)
On the exam
Lecture 22 is examined in two of the four past finals: 18 points of FN10 and about 13 of FN17 come from it, and FN17-1e’s 5-point short answer leans on Section 3. The test-and-energy practice page, FT1 (being written), solves the new parts in full; FN10-6c is solved on FS1. This chapter’s examples use other numbers, so its results are not those parts’ answers.
| Part | Points | What it asks | Sections |
|---|---|---|---|
| FN17-1d | 5 | why reducing the latency of a clock distribution is desirable | §6 (with §7, §9) |
| FN10-6c | 8 | the jitter of a clock tree from a supply droop and the delay’s supply sensitivity | §6 (the formula); solved on FS1 |
| FN10-2c | 10 | the lowest supply at which a subthreshold inverter’s output still swings at least from 0.1 to 0.9 , and there | §15 |
| FN17-10c | ≈ 8 | the switching energy of a subthreshold chain (dynamic plus leakage during its delay) against , and the supply that minimizes it | §16 (with §15) |
| FN17-1e | 5 | one mechanism of infant mortality, and how burn-in finds it | Chapter 22 §10–§11; §3 supports it |
No past final tests LFSRs and signatures (§1–§2), current-density sizing (§4), synchronous against asynchronous design (§5), the grid, tree and tree-driven grid (§8–§10), gating (§11–§12) or DVFS (§13–§14); short-answer parts can draw on any of them.
Notes for the practice page.
- FN17-1d is an argument in three steps. Latency is the clock network’s root-to-leaf delay; process, voltage and temperature variation changes that delay by a fraction of itself, statically (skew) and from cycle to cycle (jitter); so the skew and jitter are proportional to the latency, , and a lower latency loses less timing margin. Five points want the proportionality, not only the words.
- FN10-2c needs the drain factor. Write the current balance with , say which reading of the input you take, and give as defined () at the result.
- FN17-10c: test before you differentiate. Write the energy with in both terms, find , and compare it with ; with no root, the energy falls to the functional limit.
Memorize.
- The four clock metrics with their definitions; latency turns variation into skew and jitter.
- Grid: + insensitive to loading; − wire, − capacitance. H-tree: + stingy, lower capacitance; − sensitive to loading, tuned wire for wire and silicon for silicon. Tree-driven grid: the compromise.
- Electromigration: a DC, current-density, thermally activated wear-out; worst at vias, corners and necks; burn-in runs hot to find it. Limits: Al 1–2, Cu ≈ 10 mA/µm² DC; ≈ 15 and 150 AC.
- Wasted power: idle leakage (power gating, a high-, wide header) and idle clocking (clock gating, an AND in the local generator).
- DVFS: and together; dynamic energy ; the three converters.
- An -flop maximum-length LFSR has period .
- The minimum-energy existence test .
Derive (with the path).
- Skew and jitter from latency (§6): one buffer’s ; every buffer on the path; sum: .
- A wire’s minimum width (§4): .
- H-tree path and wire (§9): sum the levels, and .
- The low output (§15): the drain factor from the two barriers; set the two currents equal at .
- The minimum energy (§16): ; ; ; differentiate in to .
Method cards. The playbook cards for these families (clock-network short answers, the subthreshold limit, minimum energy) come with FT1; until then, Sections 6, 15 and 16 are the method.
The lecture’s boards
The boards of Lecture 22 used in this chapter (34 frames)

































