Operating Systems Internals
A compact foundation for tracing how operating systems isolate work, cross kernel boundaries, schedule execution, manage memory pressure, coordinate concurrency, and expose evidence for host-level diagnosis.
TRACKS
A compact foundation for tracing how operating systems isolate work, cross kernel boundaries, schedule execution, manage memory pressure, coordinate concurrency, and expose evidence for host-level diagnosis.
A compact bridge from operating-system foundations to storage design: choose a storage contract, separate metadata from data paths, trace caching and durability boundaries, follow an I/O request, and read operational pressure before entering implementation deep dives.
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.
Caches, pipelines, memory hierarchies, branch behavior, and the hardware performance models that shape software design decisions.
Memory ordering, atomicity, lock-free design, wait-freedom, and the concurrency models behind scalable shared-memory systems.
Interrupts, DMA, drivers, block and network I/O paths, and the kernel-to-device mechanics that shape latency and throughput.
Draft track for kernel datapaths, packet processing, observability, and programmable networking hooks.
Compiler and runtime systems from lexing, parsing, IR, dataflow, optimization, register allocation, and code generation through bytecode VMs, JIT tiering, deoptimization, GC interfaces, and runtime observability.
Memory behavior from virtual memory, page faults, cache locality, and NUMA through arena, stack, pool, free-list, buddy, slab, and general-purpose allocator design.
Journaling, copy-on-write trees, allocators, recovery, metadata engines, and the implementation trade-offs inside storage stacks.
Virtual machines, hypervisors, device emulation, paravirtualization, and the isolation mechanisms underneath cloud compute.
Build a Linux workstation you can inspect, repair, and reproduce by tracing shell, filesystem, package, and service behavior before comparing Arch-style ownership with NixOS-style declaration.
A comparative path through language trade-offs, memory, types, performance, ergonomics, bindings, and API design across Rust, C++, and Python.
Runtime and kernel-level performance for backend services: event loops, syscalls, zero-copy I/O, memory mapping, GC tuning, virtual threads, actors, memory barriers, and lock-free design.