The Layer Stack — Part 6 of 9

The Core Idea

Abstraction

Each layer exposes a clean interface and hides its mess. A Python programmer never thinks about voltage levels; a transistor never knows about Python.

The Treaty

The ISA Contract

The Instruction Set Architecture (x86-64, ARM) is the treaty between hardware and software: any chip that speaks the ISA runs the same binaries.

The Boundary

Two Worlds: User & Kernel

The CPU itself enforces a privilege boundary. Applications live in user mode; only the OS kernel touches hardware. Crossing costs a syscall.

The Trade-off

Layers Have a Price

Every boundary adds overhead. Most software happily pays it; Part 9 (HFT) shows what it takes to refuse.

The Abstraction Stack

Click a layer

Top = human intent, bottom = physics. Each block only talks to its immediate neighbours, through a fixed interface.

▲ Human / intent

▼ Physics / silicon

Warm colours = software you can change Cool colours = hardware you cannot - - - privilege boundary - - - the ISA line

The journey of `print("hello")`

One line of Python, all the way down the stack and back up again. Watch the tower on the left: the glowing block is the layer currently doing the work.

Descend

app → libc

Kernel

the gate & the driver

Return

sysret & switch

Render

glyphs & GPU

Silicon

pixels → photons

CPU privilege mode

USER

Ring 3 · no hardware access

Layer crossings

boundaries traversed

Privilege crossings

user ↔ kernel

Elapsed

0 ns

waiting to start

· idle

Trace · 14 steps

⚡ Every layer crossing costs time

Function call

~1 ns

Syscall

~200 ns

Context switch

~2 µs

GPU round trip

µs–ms

A function call ~1 ns · a syscall ~200 ns · a context switch ~2 µs · a GPU round trip ~µs–ms. Most software gladly pays for the convenience. Part 9 shows an industry that profiles every one of these.

Step 0 / 14

The Abstraction Stack

The journey of print("hello")

Trace · 14 steps

The journey of `print("hello")`