-
Notifications
You must be signed in to change notification settings - Fork 131
feat: bucketized futexes #2469
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
Open
zyuiop
wants to merge
5
commits into
hermit-os:main
Choose a base branch
from
zyuiop:feat/bucketized-futexes
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+124
−67
Open
feat: bucketized futexes #2469
Changes from all commits
Commits
Show all changes
5 commits
Select commit
Hold shift + click to select a range
d9e24f9
feat(futex): multiple locks to reduce lock contention
zyuiop 902bbad
feat(futex): if SMP is disabled, we normally only need one bucket
zyuiop 5b80555
Fix formatting
zyuiop 9eef574
fix: new futex lock was not interrupt safe
zyuiop 49d45ab
futexes: change data structure
zyuiop File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains hidden or 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
This file contains hidden or 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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If you're trying to remove the zero bits resulting from
AtomicU32's alignment, then you have to shift by 2, not 3. Since you're hashing anyway, I don't think this is necessary anyway.There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was trying to remove the last 3 bits from the address, which for some reason I believed to always be 0
But you are correct that this is in any case not needed since we hash. It may be the remain of an attempt to not use a hash function at all for better performance.
If it produced a more or less uniformly distributed distribution,
(addr >> 3) % Nwould likely be better as it is less intensive than computing a hash.Let me know what you think :)