Operating Systems - Semaphore vs Mutex - When to Use Which
In which scenario is a mutex preferred over a binary semaphore for protecting a critical section?
In which scenario is a mutex preferred over a binary semaphore for protecting a critical section?
easy🔍 Pattern Recognition Q2 of Q15
Step-by-Step Solution
Solution:
Step 1: Identify ownership semantics
Mutex enforces ownership: only the thread that locks it can unlock it. Binary semaphores do not enforce ownership.Step 2: Analyze options
Allowing multiple threads simultaneously (B) contradicts mutex purpose. Tracking resource count (C) is counting semaphore's role. Releasing lock by different thread (D) is allowed by semaphores but not mutexes.Final Answer:
Option A -> Option AQuick Check:
Mutex enforces ownership semantics strictly [OK]
Quick Trick: Mutex enforces ownership; binary semaphore does not [OK]
Common Mistakes:
MISTAKES- Assuming binary semaphore enforces ownership
- Confusing mutex with counting semaphore for resource counts
- Believing mutex allows unlocking by different threads
Trap Explanation:
PITFALL- Candidates often overlook ownership enforcement and think binary semaphores behave like mutexes in this regard.
Interviewer Note:
CONTEXT- Reveals understanding of ownership and release semantics in synchronization primitives.
Master "Semaphore vs Mutex - When to Use Which" in Operating Systems
Want More Practice?
15+ quiz questions · All difficulty levels · Free
Free Signup - Practice All QuestionsMore Operating Systems Quizzes