Linux Internals — see the kernel and userspace
Linux Internals is a visual, animated guide to the kernel and userspace — from a process opening a file to a packet hitting the NIC.
Linux kernel internals, subsystem by subsystem
The map above is a picture of how a running Linux system is put together: userspace at the top, the kernel in the middle, hardware at the bottom. Every box is listed here with what it does and where its code lives in the kernel tree (paths are for x86_64). Start with the read() syscall walkthrough to see one request cross most of these layers, or the scheduler deep-dive.
Userspace
User applications
Your processes — shells, browsers, servers, daemons. Everything in ring 3.
systemd / init
The first userspace process — supervises services, mounts, sockets, units. systemd is the dominant init today.
glibc / musl
The C library: wraps syscalls (read, write, open…) and exposes a stable userspace ABI. Implements buffering, locale, threading on top.
Dynamic linker
Resolves and maps shared libraries (.so) into a process before main() runs. PLT/GOT, lazy binding, RPATH/RUNPATH.
vDSO
A small shared object the kernel maps into every process — turns frequent calls like gettimeofday/clock_gettime into pure userspace reads.
Kernel entry
Syscall entry
Where ring 3 becomes ring 0. The SYSCALL instruction lands in entry_SYSCALL_64, which switches stacks and saves registers, then do_syscall_64() dispatches on the syscall number to the matching __x64_sys_*() handler.
Kernel: Processes
Scheduler
Picks which task runs next on each CPU. CFS until 6.6, now EEVDF. Also handles RT and SCHED_DEADLINE classes.
Signals & wait/wake
Signal delivery (SIGINT, SIGSEGV…), wake-ups, futex — the primitives that make blocking, mutexes and condition variables possible.
IPC
Pipes, FIFOs, System V & POSIX message queues, shared memory, Unix-domain sockets — how processes talk to each other.
Namespaces & cgroups
The containerization primitives. Namespaces isolate views (pid, mnt, net, user…); cgroup v2 accounts and limits resources.
Kernel: Memory
Virtual memory
Per-process address space: VMAs describing mappings, multi-level page tables, TLB management, copy-on-write.
Page cache
The unified cache of file-backed pages. Reads hit it before any I/O is issued; dirty pages are written back asynchronously.
Allocators
kmalloc/kfree are SLUB on top of the buddy page allocator. vmalloc covers non-contiguous large allocations.
Swap & OOM
Reclaim, swap, zswap and (eventually) the OOM killer — what happens when memory pressure can't be relieved.
Kernel: Storage and filesystems
VFS
Virtual filesystem layer. Generic file/dir operations dispatched to concrete filesystems via f_op->… function pointers.
Filesystems
Concrete on-disk filesystems — ext4, btrfs, xfs, fuse, tmpfs. Each implements VFS hooks plus their own journaling/COW/allocators.
Block layer
bio submission, multi-queue request layer, I/O schedulers (mq-deadline, bfq, kyber, none). The plumbing between filesystems and drivers.
Storage drivers
NVMe, AHCI/SATA, virtio-blk, SCSI — the drivers that talk to actual storage controllers and DMA pages to/from RAM.
Kernel: Networking
Sockets
The socket() syscall family. Glue between the file descriptor world and the protocol stacks below.
TCP / UDP / IP
The protocol stacks. Connection tracking, congestion control, retransmits, fragmentation, routing.
Netfilter · qdisc
Packet filtering and shaping. iptables/nftables hooks, conntrack, traffic-control disciplines (fq_codel, htb, …).
Network drivers
NIC drivers (e1000e, igb, mlx5, virtio-net, …). NAPI poll loops, ring buffers, XDP for the fastest path.
Kernel: Devices and I/O
Char devices
Character-mode devices: /dev/null, /dev/random, ttys, GPIO, watchdogs, virtio-console.
USB subsystem
Host controllers (xhci, ehci), the USB core, class drivers (hid, storage, audio, cdc).
PCI subsystem
PCI/PCIe enumeration, MSI/MSI-X, hotplug, BARs, IOMMU plumbing. The bus most devices live on.
Device model
The kobject / driver model behind sysfs, udev events, probe/remove, power management.
Hardware
CPUs
The silicon the scheduler dispatches onto. Cores, SMT, NUMA nodes.
DRAM
Physical memory that backs the virtual address space.
NVMe / SATA
Persistent storage. NVMe over PCIe is the modern fast path; SATA/AHCI still everywhere.
NIC
The network interface — physical Ethernet, WiFi radios, or paravirtualized virtio-net.
USB / PCI devices
Everything else hanging off USB or PCIe: keyboards, GPUs, sensors, accelerators.