Improve page allocator's efficiency #1418
Draft
Conversation
This file contains 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
|
Since this PR claims performance improvement, I am wondering if you have noticed any performance gains on LMbench? |
Thanks for the heads up. I am also curious about the performance gained. Theoretically, this PR focused on improving efficiency on one core, not importing a fine-grained synchronize mechanism to improve concurrent efficiency. So the PR may behave better on the single-core bench. However, this PR has passed all the debug-built tests while failing at release-built ones. Once I fix all the remaining failures, I will run benchmarks to fully assess the performance improved. |
Tangzh33
force-pushed
the
improve_page_alloc_efficiency
branch
5 times, most recently
from
c2015b9
to
6a56566
Compare
Tangzh33
force-pushed
the
improve_page_alloc_efficiency
branch
from
6a56566
to
9fe6b4f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This is the subsequent pull request of #1137, as the final solution to issue #1044.
In this PR, we refactor the meta-system and import
FreePageas the only handle ofFree Metato enhance concurrency safety. Based on the new context provided byFree Meta, we further implement safe linked list methods forFreePageand transplant the current page allocator to make use of it.With all the aforementioned efforts, the new page allocator can manage pages at
O(1)complexity under most scenarios(e.g., allocate, deallocate), while not depending on the heap allocator.Fix #1044 .