Utility: add a Windows path to the synchronisation support #603
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Use a `SRWLOCK` on Windows to support locking. Slim Reader-Writer locks are lightweight mutexes that closely resemble `pthread_mutex_t` in functionality. While possible to use `WaitOnAddress` to implement `os_unfair_lock`, that would be more complex and a slightly heavier mutex as a starting point seems reasonable. If it turns out that the performance really requires an even lighter weight locking primitive, we can refine this to `WaitOnAddress` subsequently.
|
@swift-ci please test |
daniel-grumberg
approved these changes
May 31, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Use a
SRWLOCKon Windows to support locking. Slim Reader-Writer locks are lightweight mutexes that closely resemblepthread_mutex_tin functionality. While possible to useWaitOnAddressto implementos_unfair_lock, that would be more complex and a slightly heavier mutex as a starting point seems reasonable. If it turns out that the performance really requires an even lighter weight locking primitive, we can refine this toWaitOnAddresssubsequently.