Merged
Conversation
Member
Author
|
|
gareth-rees
force-pushed
the
branch/2020-08-29/page-sparering-elim
branch
from
6a3237b to
bd05750
Compare
Member
Author
|
@UNAA008 @NickBarnes Any thoughts on this pull request? It has been open since July 2018. |
…allocation failure from fotest. Copied from Perforce Change: 195988
…d by the spare page land, and free/allocated pages can be distinguished using the pool pointer. Copied from Perforce Change: 195991
…d purging, as suggested by RB in review. Copied from Perforce Change: 195997
gareth-rees
force-pushed
the
branch/2020-08-29/page-sparering-elim
branch
from
bd05750 to
5553763
Compare
jollaitbot
pushed a commit
to sailfishos-mirror/emacs
that referenced
this pull request
Sep 17, 2025
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 change represents the arena's spare memory as a "land" (a tree of address ranges) instead of a ring of tracts.
This is step 4 in the plan to eliminate the tract tables: see job003798.
The work was originally done in 2018 and was partially reviewed at the time 1 2 3 4 5 but never got approval for merge.