-
Notifications
You must be signed in to change notification settings - Fork 5.6k
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
8324828: Avoid multiple search of reserved regions during splitting #18001
8324828: Avoid multiple search of reserved regions during splitting #18001
Conversation
👋 Welcome back azafari! A progress list of the required criteria for merging this PR into |
@afshin-zafari The following label will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing list. If you would like to change these labels, use the /label pull request command. |
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.
Good. I would have named the flags "flag1" or "flag2" or "flag_rhs", "flag_lhs" or similar, but that is just nitpicking.
@afshin-zafari This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 151 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. ➡️ To integrate this PR with the above commit message to the |
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.
Nice!
Thank you @tstuefe and @jdksjolen for your reviews. |
Going to push as commit 7583419.
Your commit was automatically rebased without conflicts. |
@afshin-zafari Pushed as commit 7583419. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
To reserve two consequent memory regions, developers need to reserve a large region and then split it into two sub parts. To register memory type
(MEMFLAGS) mtXXX
for a region another call to NMT API is needed for every sub part. Since at every NMT call a linked list of reserved regions is searched, therefore for every split operation there are three NMT calls and search in the list.This PR adds the memory flags of the two sub regions to the split API to avoid extra search in the list.
tiers1-5 tests passed
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/18001/head:pull/18001
$ git checkout pull/18001
Update a local copy of the PR:
$ git checkout pull/18001
$ git pull https://git.openjdk.org/jdk.git pull/18001/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 18001
View PR using the GUI difftool:
$ git pr show -t 18001
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/18001.diff
Webrev
Link to Webrev Comment