register file
A small bank of storage entries (registers) inside a processor core that feed inputs to and receive outputs from logic units.
As defined in Dwarkesh Patel Podcast - Reiner Pope – Chip design from the bottom up
Where it comes up · 1
Most important claims · 5 of 5Search all claims for “register file” →
- CPU cores are ~100x bigger than GPU cores largely because of the branch predictor — a large area dedicated to predicting where and when branches occur — which has no equivalent in a GPU; stripping out the branch predictor and tightening the register files drives much of the GPU's density advantage over the CPU.Dwarkesh Patel Podcast - Reiner Pope – Chip design from the bottom up
- A systolic array bakes two levels of the matrix-multiply loop into hardware so that the weight matrix is stored locally in registers and reused across many input vectors; this provides x×y as much compute while keeping input/output communication at only x, solving the data-movement problem that plagued CUDA cores and making it the most efficient known circuit for matrix multiplication.Dwarkesh Patel Podcast - Reiner Pope – Chip design from the bottom up
- Selecting one input out of n in hardware — invisible to the software programmer who just says 'I want register three' — actually requires a mux costing n×p AND gates and (n−1)×p OR gates, built by masking every entry and ORing the results together.Dwarkesh Patel Podcast - Reiner Pope – Chip design from the bottom up
- In a pre-Tensor-Core CUDA/CPU core, the cost of moving data from the register file to the ALU and back vastly exceeds the cost of the logic unit itself: with three muxes (one per multiply-accumulate input) over an 8-entry register file, roughly seven-eighths of the circuit area is spent on reading and writing registers and only a tiny fraction on the actual computation.Dwarkesh Patel Podcast - Reiner Pope – Chip design from the bottom up
- Most chip design decisions are sizing decisions — for example, how big to make the systolic array versus the register file — which are coupled and can be approached by setting a budget for what percentage of chip area is spent on data movement (e.g. 10% register file, 90% systolic array), trading register-file flexibility and application performance against compute area.Dwarkesh Patel Podcast - Reiner Pope – Chip design from the bottom up