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

use a new mutex wrapper API #27

Merged
merged 4 commits into from
Sep 17, 2024
Merged

use a new mutex wrapper API #27

merged 4 commits into from
Sep 17, 2024

Conversation

facontidavide
Copy link
Collaborator

Solve #25

PROS:

  • Now we have read/write locks and read-only locks. This should reduce the potential mutex contention.

CONS

  • we have loct priority inversion 😢

In practice, I don't know what is better/worse.

@facontidavide facontidavide changed the title use a new mutx wrapper API use a new mutex wrapper API Sep 15, 2024
Copy link
Collaborator

@henrygerardmoore henrygerardmoore left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I pushed commits that should hopefully fix CI.

Regarding the priority inversion problem, should we maybe just mention this in the example or documentation so unfamiliar users are aware of the possibility? I think this PR is a good change anyway, and won't block on that

If you think adding to the documentation or examples is a good idea, I wanted to let you do that since I think you'd explain it better, but let me know if you don't have time and I can take a pass at it.

@facontidavide facontidavide merged commit a47f40d into main Sep 17, 2024
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants