Direct-mapped cache: hits, misses and conflicts, live
In a direct-mapped cache every memory address has exactly one line it can live in: the low address bits (the index) pick the line, and the high bits (the tag) are stored with it, so a lookup is a hit only if that line is valid and holds the same tag. This live 4-line cache splits a 4-bit address A3..A0 into tag A3 A2 and index A1 A0.
Each line here holds a valid bit, a 2-bit tag and 2 bits of data. The index A1 A0 selects one line through 4:1 multiplexers, and two XNOR gates compare its stored tag with A3 A2: HIT = valid AND (tag matches), MISS is the opposite, and D1 D0 show the selected line's data. On a miss, the data would come from main memory; here you play memory by setting DIN1 DIN0 and pressing FILL, and the next clock edge writes the tag and data into the line and sets its valid bit. The interesting case is the conflict miss: addresses 0101 and 1101 have the same index (01) and different tags, so they fight over line 1, and filling one evicts the other, even while lines 0, 2 and 3 sit empty. That is the price of direct mapping, and the reason caches add associativity (the cache lesson covers both). Each line's tag and data are a 4-bit register with load, written through a decoder as in the register file, and the valid bits are D flip-flops that set on a fill and clear on a clock edge with CLR high. Real caches are bigger in every direction (a line holds 32 or 64 bytes, and there are hundreds of lines), but the lookup is the same. The live circuit opens with CLR high and address 0101: turn CLK on and off once to invalidate every line (MISS lights), set CLR to 0, then FILL and pulse CLK to load line 1. Before the page is built, a 23-step sequence is checked on HIT, MISS, V and the selected line's tag and data: misses, fills, a conflict miss and eviction, an untouched line, and invalidating everything.
Open this circuit in the lab →
What you need
- 4× 4-bit register with load: the lines: tag (A3 A2) and data (DIN1 DIN0)
- 4× D flip-flop + 4 OR + 4 AND: the valid bits: set by a fill, cleared on a clock edge with CLR high
- 8× AND + 3 NOT: decoding the index into the fill enables, gated by FILL
- 5× 4:1 multiplexer: the selected line's tag, data and valid bit
- 2× XNOR + 2 AND + 1 NOT: HIT = valid AND tag match, and MISS
Step by step
- Place inputs
A3toA0,DIN1,DIN0,FILL,CLKandCLR, and probesHIT,MISS,D1,D0,V,TAG1andTAG0. - Give each of four lines a register for tag and data and a valid flip-flop, all written on a clock edge when FILL is high and the index A1 A0 selects that line.
- Read the selected line through 4:1 multiplexers on A1 A0, and compare its tag with A3 A2 using two XNORs.
- HIT = valid AND both tag bits equal. Look up 0101 (miss), fill it, look it up again (hit), then try 1101 (a conflict miss).
A short run
| Address | Line (A1 A0) | Tag (A3 A2) | Result | Why |
|---|---|---|---|---|
| 0101 | 01 | 01 | miss | line 01 is empty |
| 0101 after a fill | 01 | 01 | hit | line 01 holds tag 01 |
| 1101 | 01 | 11 | miss | same line, different tag (conflict) |
| 1101 after a fill | 01 | 11 | hit | line 01 now holds tag 11 |
| 0101 | 01 | 01 | miss | evicted by 1101 |
| 0010 | 10 | 00 | miss | line 10 is empty |
Address = tag (2 bits) then index (2 bits). With 4 lines and 2 tag bits, this cache holds 4 of the 16 addresses at a time. A real cache line holds a block of bytes, and the lowest address bits pick a byte within it (the offset); with one data word per line, this one has no offset bits.
You can also read the full theory in the lesson on caches. Prefer to build it yourself from scratch? Open the digiwleea lab and place the gates on the canvas, or start from the logic gate simulator.
Build more parts from gates
Each of these is one step from a transistor to a working CPU. Build every gate from CMOS transistors and work all the way up in the free digiwleea lab, with the free theory reference alongside.
Open the direct-mapped cache in the lab →Frequently asked
How does a direct-mapped cache work?
The address is split into a tag and an index. The index selects exactly one cache line, and the cache compares that line's stored tag with the address's tag: if the line is valid and the tags match it is a hit, otherwise a miss, and the block is fetched from memory into that line, replacing whatever was there.
What is a conflict miss?
A miss caused by two addresses that map to the same line. In a direct-mapped cache they keep evicting each other even if the rest of the cache is empty. Associative caches reduce conflict misses by letting a block sit in any of several lines.
What are the tag, index and offset?
The offset (lowest bits) picks a byte within a cache line, the index (middle bits) picks the line, and the tag (highest bits) is stored in the line to tell which of the many addresses with that index is there now.
What is the valid bit for?
It says whether a line holds real data. At power-on, or after the cache is flushed, every valid bit is 0, so every lookup misses even if a stored tag happens to match.