Systems Foundations · core
Operating System Mechanics
Processes, threads, virtual memory, scheduling, filesystems, syscalls, and kernel boundaries.
Mental model
An operating system multiplexes hardware while enforcing isolation. Processes, virtual memory, schedulers, and filesystems are policies built on CPU, memory, and device mechanisms.
How to study Operating System Mechanics
Begin by restating the mental model in your own words, then connect it to a concrete system you have built or operated. Name the mechanism, the constraint it addresses, and the trade-off it introduces. Use Operating Systems: Three Easy Pieces to check details, but close the source before writing your explanation. Retrieval is the learning step; rereading is only preparation.
Next, compare Operating System Mechanics with Compute, Memory & Storage Hierarchy. Ask what changes in correctness, latency, resource use, operability, and failure recovery. Complete Design exercise: Operating System Mechanics and preserve the command, input, output, and one failed attempt as evidence. Finish by explaining the idea without jargon to someone who has not studied the track.
Proof of understanding
- Explain the mechanism from first principles and identify the state it reads or changes.
- Give one situation where the concept is the right choice and one where it is not.
- Predict a realistic failure mode before running the drill, then compare the prediction with evidence.
- Connect the result to a roadmap or build artifact instead of treating the concept as isolated trivia.
Learn from primary sources
Practice and explain it back
Design exercise: Operating System Mechanics
Processes, threads, virtual memory, scheduling, filesystems, syscalls, and kernel boundaries. Implement designOutline() returning non-empty values for: processModel, memoryModel, ioPath. Each value must name a concrete mechanism or decision.
Expected evidence: A design outline with processModel, memoryModel, ioPath plus an explicit failure mode or trade-off.
Open the interactive drill →Review prompts
- What does virtual memory actually buy beyond "more memory than you have"?
Build evidence
Synthesize: Systems Foundations
Build a tiny HTTP/1.1 static-file server on raw TCP sockets without a framework or high-level HTTP server library. Parse requests, serve bounded files, handle partial I/O, inject failures, measure the result, and explain how the operating system, network, memory, concurrency, and storage paths interact.
- Accepts TCP connections, parses a bounded HTTP GET request, serves fixture files, and returns explicit errors for malformed requests, missing files, and path traversal attempts
- Names and implements a concurrency model with connection, request-size, timeout, and resource limits, including correct handling of partial reads and writes
- Injects at least a slow client, malformed request, or interrupted transfer and demonstrates bounded failure and recovery
- Reports a reproducible workload with throughput, p50/p95 latency, peak memory, and open-connection observations
- Explains the loader, process, syscall, buffer, filesystem, TCP, and scheduling path in a concise architecture note