LearnViz CompSci
Home / Learn / Operating Systems / Semaphores

Intermediate Topic 21 of 51 Operating Systems

Semaphores

Counters controlling access by multiple units.

How it works

A semaphore is a synchronization counter with two atomic operations: wait, or P, decrements it and blocks if it would go below zero, and signal, or V, increments it and wakes a waiter. A binary semaphore acts like a lock, while a counting semaphore controls access to a pool of N identical resources. Unlike mutexes, any thread can signal, which makes semaphores useful for signaling between threads.

Step-by-step walkthrough

  1. The semaphore is a counter set to 2 free slots.
  2. Thread A calls wait and takes a slot, count is 1.
  3. Thread B takes the last slot, count is 0.
  4. Thread C calls wait and blocks.
  5. When someone calls signal the count rises and C proceeds.

Where it is used

Limiting connections or threads in a pool, solving producer-consumer with empty and full counters, coordinating readers and writers, and ordering events between threads use semaphores.

Common pitfall

Incorrect wait and signal order leads to deadlock or lost wakeups, and forgetting to signal blocks others forever. They are easy to misuse because they have no ownership and no structure. Prefer higher-level constructs such as monitors and condition variables when possible, and document what each count means.

Where it fits in the course

Semaphores is topic 21 of 51 in Operating Systems, rated Intermediate. It follows Mutex. The next topic is Monitors.

Practice and explore

How to study this topic

  1. Read the explanation above and restate the definition in your own words.
  2. Open the interactive lesson and answer its mini quiz.
  3. Read the common pitfall, then write a short example that avoids it.
  4. Check your understanding in the Operating Systems quiz, and revisit the topic if you miss a question.

Frequently asked questions

What is Semaphores?
Counters controlling access by multiple units. It belongs to Operating Systems and is an intermediate-level topic.
Where do people use Semaphores?
Limiting connections or threads in a pool, solving producer-consumer with empty and full counters, coordinating readers and writers, and ordering events between threads use semaphores.
What is the most common mistake with Semaphores?
Incorrect wait and signal order leads to deadlock or lost wakeups, and forgetting to signal blocks others forever.
What should I learn before this topic?
Start with Mutex, the topic just before it in Operating Systems.
How can I practice it?
Answer the mini quiz in the interactive lesson, then take the Operating Systems quiz.
Is Semaphores hard to learn?
It is an Intermediate topic. Be comfortable with the Beginner topics in this area first, then read the common pitfall carefully, since it is where most mistakes happen.
How long does it take to learn Semaphores?
Most learners can read the explanation and finish the interactive lesson in under an hour. Fluency comes from applying the idea, so plan a few short practice sessions with the quiz.
Which topics are related to Semaphores?
Mutex, Monitors, Critical Section are closely connected. The full list is in the related topics section of this page.
What should I study after Semaphores?
Continue with Monitors, the next topic in Operating Systems.

Related topics