Skip to content
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

[mono] Switch to shared implementation of LowLevelLock #48031

Closed
CoffeeFlux opened this issue Feb 9, 2021 · 0 comments · Fixed by #48928
Closed

[mono] Switch to shared implementation of LowLevelLock #48031

CoffeeFlux opened this issue Feb 9, 2021 · 0 comments · Fixed by #48928
Milestone

Comments

@CoffeeFlux
Copy link
Contributor

We seem to have a separate one in our CoreLib for some reason, introduced as part of mono/mono#17387. Ideally we would get rid of that and just set FeatureSharedLowLevelLock, but is used by the threadpool so it's possible it will impact TE perf numbers.

@CoffeeFlux CoffeeFlux added this to the 6.0.0 milestone Feb 9, 2021
@dotnet-issue-labeler dotnet-issue-labeler bot added the untriaged New issue has not been triaged by the area owner label Feb 9, 2021
@CoffeeFlux CoffeeFlux removed the untriaged New issue has not been triaged by the area owner label Feb 9, 2021
@CoffeeFlux CoffeeFlux assigned CoffeeFlux and unassigned CoffeeFlux Mar 1, 2021
@ghost ghost added in-pr There is an active PR which will close this issue when it is merged and removed in-pr There is an active PR which will close this issue when it is merged labels Mar 1, 2021
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Mar 2, 2021
@ghost ghost locked as resolved and limited conversation to collaborators Apr 1, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant