Operating Systems - Context Switch - Cost & Causes
In a multi-core system, how does the context switch overhead per core compare to a single-core system, assuming the same workload per core?
In a multi-core system, how does the context switch overhead per core compare to a single-core system, assuming the same workload per core?
medium🪤 Complexity Trap Q6 of Q15
Step-by-Step Solution
Solution:
Step 1: Analyze context switch locality
Context switches happen independently on each core; overhead per core remains similar to single-core.Step 2: Evaluate other options
Synchronization overhead is not typically incurred per context switch. Workload sharing does not reduce per-core switches if workload per core is constant. Multi-core systems still perform context switches on each core.Final Answer:
Option B -> Option BQuick Check:
Context switch overhead is per core, similar to single-core [OK]
Quick Trick: Context switch overhead is local per core [OK]
Common Mistakes:
MISTAKES- Assuming cross-core synchronization adds overhead per switch
- Believing workload sharing reduces per-core overhead
- Thinking multi-core eliminates context switches
Trap Explanation:
PITFALL- Candidates confuse multi-core synchronization with context switch overhead per core.
Interviewer Note:
CONTEXT- Checks understanding of context switch overhead scaling in multi-core systems.
Master "Context Switch - Cost & Causes" in Operating Systems
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Operating Systems Quizzes