refactor(ps): Store memory mappings per process#411
Merged
rabbitstack merged 1 commit intomasterfrom Dec 20, 2024
Merged
Conversation
rabbitstack
force-pushed
the
refactor-process-mmaps
branch
2 times, most recently
from
6b12753 to
29437ba
Compare
The process state is refactored to store all the memory mappings created by the process. This effectively eliminates the need to keep the memory mappings in the fs processor hence improving code quality, readability, and performance.
rabbitstack
force-pushed
the
refactor-process-mmaps
branch
from
29437ba to
9f2f130
Compare
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
1 participant
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.
What is the purpose of this PR / why it is needed?
The process state is refactored to store all
the memory mappings created by the process.
This effectively eliminates the need to keep the
memory mappings in the fs processor hence improving code quality, readability, and performance.
What type of change does this PR introduce?
/kind refactor (non-breaking change that restructures the code, while not changing the original functionality)
/kind improvement
Any specific area of the project related to this PR?
/area other
Special notes for the reviewer
Does this PR introduce a user-facing change?