The last chapter compared processes, threads, and events as ways to run work at the same time. This chapter covers the structures that connect those workers. It also covers the rules that keep thos...
Stage 4 ended with the kernel mapping an executable and jumping to its entry point. This chapter is the first part of Stage 5. Stage 5 is about how concurrent work is structured. It starts with the...
The previous chapter showed how a call turns into registers and a stack frame. This chapter shows where those instructions live after the compiler makes code. This is the third article in Stage 4. ...
Earlier we explained caches and how cores keep their copies in sync. This chapter gives the rules. The rules say what one thread can trust when it reads memory written by another thread. This is th...
The last chapter looked inside one object file. We saw sections, symbols, and relocations. This chapter follows those files to the next stage, where they join. It is the fourth article in Stage 4. ...
The last chapter showed how linking collects object files, resolves symbols, and patches relocations. This chapter shows what linking produces. It shows how the kernel and the runtime turn that fil...
The previous chapter followed your source text as it became object files. This chapter opens up one step: code generation. This is the step where a call stops being a name and becomes registers, a ...
The last chapter showed how cores share memory. It showed how ordering rules decide what a thread can trust. This chapter shows how the CPU talks to devices. It shows how user code enters the kerne...
The previous chapter described how control moves to the kernel through interrupts and traps. This chapter explains why that move is safe. It is the sixth and final chapter of Stage 3. A modern CPU...
Stage 2 : Linux and Operating System Internals Subject area 2.2 : Scheduling and Resource Control Article 8 The short version Every resource on a Linux machine runs out at some point. A progra...