How Computers Work
I/O-bound vs CPU-bound
waiting on devices vs on compute
Source board
This definition comes from the board below. Open it to see the term in context.
IO Interrupts and the BusHow Computers WorkMore terms from this board
- blocking I/Othread parked until data arrives
- bootloader (GRUB)loads the kernel
- busshared wiring (memory bus, PCIe)
- device driverkernel code speaking one device's protocol
- DMAdevice moves data to/from RAM itself, CPU freed
- event loopone thread servicing many sockets
- firmware (BIOS/UEFI)first code at power-on
- init / systemdPID 1, starts everything
- interrupta device signal that yanks the CPU to a handler
- ISR / interrupt handlerthe code that runs on an interrupt
- memory-mapped I/Odevice registers appear as memory addresses
- non-blocking / async I/Ofire many, poll readiness (epoll/io_uring)
- pollingbusy-asking if a device is ready (wasteful)
- timer interruptthe tick that preempts