Race conditions ni nini, na mutex na semaphore huzizuiaje?

Question

IT Interview Practice · Accepted Answer

Wakati thread nyingi zinaposhiriki data, operesheni zao zinaweza kuingiliana (interleave) katikati ya usasishaji wa hatua nyingi, zikitokeza race condition — hitilafu ambapo matokeo hutegemea muda usiotabirika. Synchronization ni seti ya zana zinazolazimisha mpangilio salama.

Tatizo: race condition

count++ inaonekana atomic lakini kwa hakika ni read-modify-write:

## Tatizo: race condition

`count++` inaonekana atomic lakini kwa hakika ni read-modify-write:

```c
// two threads, shared int count = 0, each does count++ once
// thread A: read count (0) ─┐           interleaving loses an update:
// thread B: read count (0) ─┤  both read 0, both write 1 → count == 1, not 2
// thread A: write 1         │
// thread B: write 1         ┘
```

Dirisha kati ya kusoma na kuandika ni **critical section** — code inayogusa hali inayoshirikiwa na haipaswi kukimbia kwa wakati mmoja.

## Zana

- **Mutex (lock)** — mutual exclusion: thread moja tu huishikilia kwa wakati mmoja; nyingine huzuiwa hadi itakapoachiliwa. Ifunge critical section:

```c
pthread_mutex_lock(&m);
count++;                 // critical section — exclusive
pthread_mutex_unlock(&m);
```

- **Semaphore** — kihesabu kinachoruhusu hadi washikaji *N* kwa wakati mmoja. Semaphore ya binary (N=1) hufanya kazi kama lock; semaphore ya kuhesabu huweka kikomo, tuseme, connection pool kwa watumiaji N. Pia hutumika kwa **signaling** kati ya thread (producer/consumer).
- **Condition variable** — huruhusu thread kulala hadi predicate iwe kweli (mfano "queue si tupu"), ikiamka bila busy-waiting.
- **Atomic operations** — maagizo ya hardware kama compare-and-swap (CAS) yanayofanya read-modify-write bila kugawanyika, yakiwezesha vihesabu vya lock-free.

## Mitego

Locks hutatua races lakini huleta hatari mpya: **deadlock** (thread zikisubiri locks za kila mmoja), **priority inversion**, na **contention** (thread hufuatana kwa mfululizo, zikiua usambamba). Kanuni ya jumla: weka critical sections **fupi**, na daima chukua locks nyingi kwa **mpangilio wa kimataifa unaolingana**.

## Kwa nini ni muhimu

Hitilafu za concurrency ni miongoni mwa ngumu zaidi kupata — hazina uhakika (nondeterministic) na mara nyingi hutoweka chini ya debugger. Wahoji wanataka kuona kwamba unaweza *kutambua* critical section, kuchagua primitive sahihi (mutex dhidi ya semaphore dhidi ya atomic), na kufikiri kuhusu njia za kushindwa (deadlock, contention). Hii inatumika moja kwa moja kwa server yoyote yenye thread nyingi, cache inayoshirikiwa, au kihesabu.

Tatizo: race condition

Zana

Mitego

Kwa nini ni muhimu

Maswali yanayohusiana