Operating Systems Implementation

TRACK

A project-oriented bridge that turns operating-system mental models into traceable implementation decisions for a small kernel, from boot and privilege transitions through memory, scheduling, syscalls, I/O, isolation, and debugging.

How can I trace a small kernel from boot to user-visible behavior, preserve invariants across traps, memory, scheduling, I/O, and isolation, and explain the implementation trade-offs?

16 lessons

Continues to Backend Runtime, I/O, and Performance/ Cloud, Container, and Supply Chain Security/ Compiler Construction, Runtimes, and Virtual Machines/ Concurrency, Memory Models, and Lock-Free Systems/ Containers, Kubernetes, and Platform Runtime/ Database Engine Internals and Implementation/ Engine Systems, Tooling, and Performance/ Filesystem and Storage Implementation/ Game Engine Runtime Patterns/ GPU Systems and Accelerators/ I/O Stacks, Device Drivers, and Storage Paths/ Kernel Networking and eBPF/ Memory Systems and Allocators/ Network Protocols and Transport Systems/ Transaction Manager Implementation/ Virtualization and Hypervisor Systems

LESSONS

  1. 001
    [TODO]
  2. 002
    [TODO]
  3. 003
    [TODO]
  4. 004
    [TODO]
  5. 005
    [TODO]
  6. 006
    [TODO]
  7. 007
    [TODO]
  8. 008
    [TODO]
  9. 009
    [TODO]
  10. 010
    [TODO]
  11. 011
    [TODO]
  12. 012
    [TODO]
  13. 013
    [TODO]
  14. 014
    [TODO]
  15. 015
    [TODO]
  16. 016
    [TODO]

← Back to Systems Internals