forked from chromium/chromium
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
[PA] Make GigaCage allocation code consistent for direct map & normal…
… buckets In the USE_BRP_POOL_BLOCKLIST case, both AllocNewSuperPage and PartitionDirectMap paths had an almost identical "find range not in the block list" loop. With a little effort, they can be combined together. While at it, fix another inconsistency by not allocating ref-count metadata page when BRP pool isn't used on the AllocNewSuperPage path. Change-Id: I2223450c6dc3e1f3b9994ffb3f0c1ce7ad98456f Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2916297 Reviewed-by: Takashi Sakamoto <tasak@google.com> Commit-Queue: Bartek Nowierski <bartekn@chromium.org> Cr-Commit-Position: refs/heads/master@{#888376}
- Loading branch information
1 parent
b988dc0
commit bab19f6
Showing
1 changed file
with
106 additions
and
130 deletions.
There are no files selected for viewing
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