-
Notifications
You must be signed in to change notification settings - Fork 12
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
Remove try-lock-yield in asynchronous methods #49
Milestone
Comments
wvwwvwwv
changed the title
TreeIndex: remove spin mutex
Asynchronous API: remove spin mutex
Apr 9, 2022
wvwwvwwv
changed the title
Asynchronous API: remove spin mutex
Asynchronous API and TreeIndex: remove spin mutex
Apr 9, 2022
wvwwvwwv
added a commit
that referenced
this issue
Apr 11, 2022
replace several places where an operation is retried is replaced with forget-expecting that the lock owner would cleanup things.
wvwwvwwv
added a commit
that referenced
this issue
Apr 26, 2022
wvwwvwwv
added a commit
that referenced
this issue
Apr 26, 2022
wvwwvwwv
added a commit
that referenced
this issue
Apr 26, 2022
wvwwvwwv
added a commit
that referenced
this issue
Apr 27, 2022
wvwwvwwv
added a commit
that referenced
this issue
Apr 27, 2022
wvwwvwwv
changed the title
Asynchronous API and TreeIndex: remove spin mutex
Remove try-lock-yield in asynchronous methods
May 1, 2022
wvwwvwwv
added a commit
that referenced
this issue
May 10, 2022
the functionality is the same as before since AsyncWait is incomplete.
wvwwvwwv
added a commit
that referenced
this issue
May 12, 2022
wvwwvwwv
added a commit
that referenced
this issue
May 12, 2022
… wait for async methods (#75) hashmap, hashset, and hashindex asynchronous methods never spin.
wvwwvwwv
added a commit
that referenced
this issue
May 12, 2022
wvwwvwwv
added a commit
that referenced
this issue
May 13, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Avoid spinning under any circumstances.
HashMap
,HashIndex
, andHashSet
: SCC 0.6.11.TreeIndex
.The text was updated successfully, but these errors were encountered: