Practice
Solution
Step 1: Understand the role of PCB
The PCB stores the CPU register states and other process information needed to resume execution later.Step 2: Differentiate from scheduler and interrupt handler
The scheduler decides which process runs next but does not save registers; the interrupt handler triggers context switches but does not save registers itself.Step 3: MMU role
The MMU handles memory address translation, unrelated to register saving.Final Answer:
Option D -> Option DQuick Check:
PCB contains saved CPU state -> correct component for saving/restoring registers.
- Confusing scheduler with register saving
- Assuming interrupt handler saves registers
- Thinking MMU handles CPU state
Solution
Step 1: Understand the working set model purpose
The working set model tracks the set of pages a process actively uses to allocate enough frames to avoid thrashing.Step 2: Analyze each option
A is incorrect because unpredictable access patterns reduce the effectiveness of working set tracking.
B is correct because allocating frames based on the active working set directly prevents thrashing.
C is incorrect because fixed allocation ignores dynamic working set size, risking thrashing.
D is incorrect because page-fault frequency alone does not capture locality as precisely as working set.Final Answer:
Option B -> Option BQuick Check:
Working set model adapts allocation to active pages, preventing thrashing effectively.
- Assuming fixed frame allocation prevents thrashing
- Believing page-fault frequency alone suffices
- Ignoring locality in memory allocation
Solution
Step 1: Analyze each statement
A is correct: thrashing happens when total working sets exceed memory.
B is correct: working set model adjusts frames dynamically.
C is incorrect: increasing processes usually increases memory pressure, worsening thrashing.
D is correct: load control limits active processes to prevent thrashing.Final Answer:
Option C -> Option CQuick Check:
More processes usually increase thrashing risk, not reduce it.
- Believing more processes reduce thrashing
- Confusing load control with working set adjustments
- Ignoring total memory constraints
Solution
Step 1: Understand why thrashing persists despite working set model
Even with working set allocation, total demand may exceed physical memory.Step 2: Analyze options
A is incorrect because increasing window size may increase working set size, worsening thrashing.
B is correct because load control reduces active processes, lowering total memory demand.
C is incorrect because disabling page replacement is not feasible and increases faults.
D is incorrect because fixed allocation ignores dynamic working sets, risking thrashing.Final Answer:
Option B -> Option BQuick Check:
Load control is the next step after working set model to prevent thrashing under overload.
- Thinking increasing working set window helps
- Believing disabling page replacement reduces faults
- Assuming fixed frame allocation solves thrashing
Solution
Step 1: Understand multi-level page tables
Multi-level page tables require multiple memory accesses per lookup, increasing page table access time.Step 2: Impact on EAT
On TLB miss, page table lookup is longer, so miss penalty increases, raising EAT.Step 3: Analyze options
A: Incorrect, TLB does not hide all page table lookup costs.
B: Incorrect, multi-level page tables do not reduce page faults.
C: Correct, longer page table lookup time increases EAT on misses.
D: Incorrect, page table structure affects miss penalty and thus EAT.Final Answer:
Option C -> Option CQuick Check:
Longer page table lookup -> higher miss penalty -> higher EAT.
- Assuming TLB hides all page table lookup costs
- Confusing page fault rate with page table lookup time
