-
Notifications
You must be signed in to change notification settings - Fork 1.9k
Semaphore #1088
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
Comments
Merged
ndkoval
added a commit
that referenced
this issue
Apr 24, 2019
In addition, a `SegmentQueue` data structure, which emulates an infinite array with fast removing from the middle, is introduced for storing suspended acquirers in the semaphore algorithm. Fixes #1088
elizarov
pushed a commit
that referenced
this issue
Apr 26, 2019
In addition, a `SegmentQueue` data structure, which emulates an infinite array with fast removing from the middle, is introduced for storing suspended acquirers in the semaphore algorithm. Fixes #1088
ndkoval
added a commit
that referenced
this issue
Apr 29, 2019
In addition, a `SegmentQueue` data structure, which emulates an infinite array with fast removing from the middle, is introduced for storing suspended acquirers in the semaphore algorithm. Fixes #1088
ndkoval
added a commit
that referenced
this issue
Jun 4, 2019
In addition, the `SegmentQueue` data structure, which emulates an infinite array with fast removing from the middle, is introduced for storing suspended acquirers in semaphore/mutex/channel algorithms. Fixes #1088
elizarov
pushed a commit
that referenced
this issue
Jun 6, 2019
In addition, the `SegmentQueue` data structure, which emulates an infinite array with fast removing from the middle, is introduced for storing suspended acquirers in semaphore/mutex/channel algorithms. Fixes #1088
elizarov
pushed a commit
that referenced
this issue
Jun 6, 2019
In addition, the `SegmentQueue` data structure, which emulates an infinite array with fast removing from the middle, is introduced for storing suspended acquirers in semaphore/mutex/channel algorithms. Fixes #1088
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It is occasionally useful to have semaphore to limit concurrency. This is related to #172 as it serve as an alternative (more low-level) way and is also mentioned in discussion on RW mutex in #94
The text was updated successfully, but these errors were encountered: