Part 1 of 8 · 1 min read
Why this page comes last
In this module you will
- Structure an answer to a systems question: define, explain the mechanism, state the cost, give an example.
- Answer the classic questions on processes, threads, scheduling, synchronisation and deadlock.
- Answer the classic questions on memory, files, security and containers, with numbers.
- Work the three standard calculations: round-robin scheduling, page-table size and effective access time.
- Use the tools of this level to answer a "what do you do when" debugging question.
Levels 0 to 11 taught the ideas, and pages 1 to 5 of this level taught the tools. This page puts both into the form that an interview asks for: short, correct, concrete answers, and a few calculations done by hand. Every answer points to the level where the idea was built, so a weak answer can be traced to its source page and revised. After this page, the operating-systems roadmap is complete.
About this example About this example
Real: The round-robin, page-table and access-time results were computed by a script and checked by hand. The measured numbers quoted in the drills (exit 137, wa 33, 34 system calls, 103 ns against 46,757 ns) come from the Linux test machine (kernel 6.18) used in Levels 10 to 12.
Scripted: The questions are the author's selection of common ones, and the model answers are one reasonable form of each. The process burst times of 10, 5 and 8 and the hit rate of 98 per cent are made up to show the idea.
Not real: An interviewer may ask for more depth on one point or may follow a different order. The model answers are short on purpose, and each should be extended with an example from your own work.