4.1.10 · D4Memory Technologies

Exercises — Multi-level cell (MLC - TLC - QLC) flash

2,349 words11 min readBack to topic

Below each formula symbol is plain: is "how many bits we cram in one cell", is "how many charge buckets that needs", and is "how far apart those buckets sit". Keep the picture of a bar of voltage sliced into slots in your head — figure s01 draws exactly that.

Figure — Multi-level cell (MLC - TLC - QLC) flash

Level 1 — Recognition

Recall Solution L1.1

WHAT: convert levels → bits with . WHY that tool: is the exact question "2 to the what power gives 8?" — it undoes the exponent in . Three bits per cell is called TLC (Triple-Level Cell).

Recall Solution L1.2

WHY : the guard bands are the gaps between the buckets. With 16 fence posts you get 15 gaps (fencepost rule) — the same reason a 4-rung ladder has 3 spaces between rungs.


Level 2 — Application

Recall Solution L2.1

WHAT: split the window evenly across the gaps. WHY divide by 7 not 8: the level centres span the window; between 8 centres there are 7 intervals. Look at s01 — count the gaps, not the bars.

Recall Solution L2.2

Shrink factor vs TLC: Meaning: the same charge-leakage smear now eats more than double the fraction of each gap. See s02 — the QLC point sits far below the TLC point, showing how fast the spacing collapses.

Recall Solution L2.3

Capacity . WHY linear: each cell independently holds bits, and there are of them — multiply. QLC gives 4× the data on the same silicon, the entire commercial reason it exists. (See SLC Cache and SSD Write Amplification.)


Level 3 — Analysis

Recall Solution L3.1

WHAT: take the ratio of the two margins. WHY the window cancels: both cells share the same physical window, so appears in numerator and denominator and drops out. The crowding is purely about how many gaps you carve — a geometric fact, independent of the voltage value. QLC has 15 gaps where SLC has 1, so each gap is as wide.

Recall Solution L3.2

Relative margin .

relative margin
1 1
2 3
3 7
4 15

The claim is false. Halving would give . Reality falls faster than that early on ( is worse than halving) because the denominator grows exponentially, not by a fixed factor. The loss is not a subtraction and not a clean halving — it is governed by .

Recall Solution L3.3

One-level slip (110010): compare bit by bit — only the leftmost bit changes (). 1 bit flips. WHY that is the whole point of Gray code: adjacent levels are the ones whose voltage smears touch and get confused, so we designed them to differ in exactly one bit — the minimum possible, easiest for ECC to repair. (See Gray Code and Error Correction Codes (LDPC/BCH).)

Two-level jump (110011): compare — bits change at position 1 () and position 3 (). 2 bits flip. Gray code only guarantees single-bit difference for neighbours; a two-level jump can flip more. That is why keeping the physical smear inside one gap (good margin) matters even with Gray coding.


Level 4 — Synthesis

Recall Solution L4.1

Lifetime (days) ≈ endurance cycles, so divide by 365 for years. Ratio: longer for SLC. Physical reason: every erase tunnels electrons through the oxide, slowly damaging it and widening the smear. QLC starts with almost no margin ( is of SLC's), so tiny oxide wear pushes smears into overlap far sooner → far fewer safe cycles. (See Wear Leveling and Flash Endurance.)

Recall Solution L4.2

WHAT: time = data ÷ rate. Speedup: faster to accept the burst. WHY this works: SLC mode has only 2 levels, so its target distributions are wide — ISPP needs far fewer verify pulses (see Threshold Voltage and ISPP Programming). The drive absorbs the burst fast, then migrates the data to dense QLC later while idle. The cost is later write-amplification when migrating. (See SLC Cache and SSD Write Amplification.)


Level 5 — Mastery

Recall Solution L5.1

WHAT: the margin must satisfy . Solve for the largest whose spacing still meets it: Now must be a power of two, . The largest power of two is . Check (PLC): , , → fails. So this process cannot safely do PLC. WHY this is the whole game: cell design is a fight between the fixed window, the fixed smear width , and how greedily you slice. Every extra bit doubles , and falls off a cliff — eventually crossing below the smear-driven floor. See s02 for the visual crossover.

Recall Solution L5.2

Usable bits per cell (raw bits per cell) × (1 − ECC overhead). QLC still wins with 3.00 vs 2.70 usable bits/cell — but the gap (, only ) is far smaller than the raw headline. Insight: the reliability tax (bigger ECC, from Error Correction Codes (LDPC/BCH)) quietly erodes much of QLC's density advantage. If QLC's overhead ever exceeded , TLC would win — solve .


Connections

  • Parent topic — the derivations these problems drill.
  • NAND Flash Architecture — the physical cells being counted.
  • Threshold Voltage and ISPP Programming — why tighter levels write slower.
  • Error Correction Codes (LDPC/BCH) — the parity overhead in L5.2.
  • Wear Leveling and Flash Endurance — endurance in L4.1.
  • SLC Cache and SSD Write Amplification — the burst mitigation in L4.2.
  • Gray Code — the single-bit-flip encoding in L3.3.