Operating Systems - Semaphore vs Mutex - When to Use Which
Why is it generally not advisable to use a counting semaphore as a mutex replacement for protecting a critical section?
Why is it generally not advisable to use a counting semaphore as a mutex replacement for protecting a critical section?
medium🪤 Complexity Trap Q13 of Q15
Step-by-Step Solution
Step 1: Understand mutex ownership
Mutex enforces strict ownership; only the locking thread can unlock.Step 2: Counting semaphore behavior
Counting semaphores track resource count but do not enforce ownership.Step 3: Consequences of no ownership
Any thread can signal (release) the semaphore, risking synchronization errors.Step 4: Why other options are incorrect
B is true but not the main reason; C is false--semaphores do block; D is false--counting semaphores allow multiple threads.Final Answer:
Option A -> Option AQuick Check:
Ownership enforcement is key difference; counting semaphores lack it.
Quick Trick: Mutex ownership vs semaphore count: ownership prevents misuse.
Common Mistakes:
MISTAKES- Confusing blocking behavior of semaphores
- Assuming counting semaphore overhead is prohibitive
- Believing counting semaphore is equivalent to mutex
Trap Explanation:
PITFALL- Candidates often focus on performance or blocking behavior, missing the critical ownership enforcement difference.
Interviewer Note:
CONTEXT- Tests understanding of ownership semantics and why mutexes are preferred for critical sections.
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