IT, operating systems, maths, and more.
This is the tenth part of the Concurrency series. For your convenience you can find other parts in the table of contents in Part 1 – Mutex performance in .NET We have already seen how to implement custom mutex using memory mapped files and CAS operation. It has one drawback — it is not reentrant. … Continue reading Concurrency Part 10 — Reentrant mutex
This is the ninth part of the Concurrency series. For your convenience you can find other parts in the table of contents in Part 1 – Mutex performance in .NET Last time we implemented custom mutex based on memory mapped files. We can use it to track who owns the lock in much simpler way. … Continue reading Concurrency Part 9 — Semaphores with custom locks
This is the eighth part of the Concurrency series. For your convenience you can find other parts in the table of contents in Part 1 – Mutex performance in .NET We know how to use global mutexes to synchronize processes. However, there is a big drawback — we don’t know who owns the mutex and … Continue reading Concurrency Part 8 — Tracking mutex owner
This is the seventh part of the Concurrency series. For your convenience you can find other parts in the table of contents in Part 1 – Mutex performance in .NET Last time we examined an interesting behavior of Mutex when it is abandoned. Today we will look into Semaphore. Typical interview question is: what is … Continue reading Concurrency Part 7 — Semaphores trickery