Index

Module 03 · How Computers WorkMany programs, one machine

I/O, Interrupts & the Bus

IO Interrupts and the Bus
IO Interrupts and the Bus · Open board

A device ringing for the CPU’s attention instead of being checked on, and the shared wiring that carries the answer.

Before you start. You already know a CPU can be structured to juggle many tasks at once without finishing any of them first - that’s concurrency, and it’s what lets one core serve a busy server instead of handling one thing start-to-finish (Concurrency & the Hardware). This lesson is about the one event that makes that possible: the moment a slow device actually has something ready. If a network connection is new, TCP vs UDP, and the 3-way handshake in Networking shows it in one read.

Continue reading with a plan

The first three lessons of every track are free. This lesson is included with a plan, which unlocks every lesson, board, video, lab and paper for one price.

View plans →Already a member? Sign in

Lab

The device taps the CPU on every event. What happens when it taps a million times a second?

Open Let the device tap you every time, push Events a second arriving to the top, and watch What got done.

Open The interrupt storm →

Your write returned and the power cut a moment later. Is the record on the disk?

Click After every record, then Every 1,000 records, drag Where the power cuts, and watch Lost on the crash.

Open The fsync interval →

Review How Computers Work →

Saved in this browser, and to your account when you sign in.