Operating Systems - Semaphore vs Mutex - When to Use Which
In a multithreaded application, which synchronization primitive should be used to allow up to N threads to access a shared resource simultaneously?
In a multithreaded application, which synchronization primitive should be used to allow up to N threads to access a shared resource simultaneously?
easy💻 Programming Q1 of Q15
Step-by-Step Solution
Solution:
Step 1: Understand the requirement
Multiple threads can access the resource concurrently but limited to N.Step 2: Identify the primitive
Counting semaphore allows controlling access to a fixed number of identical resources.Final Answer:
Option D -> Option DQuick Check:
Counting semaphore controls multiple concurrent accesses [OK]
Quick Trick: Counting semaphore limits concurrent access by count [OK]
Common Mistakes:
MISTAKES- Choosing mutex which allows only one thread
- Using spinlock which is for busy waiting
- Condition variable is for signaling, not limiting access
Trap Explanation:
PITFALL- Mutex limits to one thread, not multiple concurrent accesses
Interviewer Note:
CONTEXT- Tests understanding of synchronization primitives for resource counting
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