feat(fs) support dynamic page size for page cache #40
Conversation
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
Author
|
sorry I need to rebase |
zhangyx827
force-pushed
the
feat/pagecache
branch
from
695d444 to
23e1f9a
Compare
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.
The size of a page in the page cache is no longer fixed to
PAGE_SIZE_4KHowever, the indexing logic remains unchanged: the start offset is calculated as
page_num * PAGE_SIZE_4K(where page_num is the cache key). Consequently, a larger page entry effectively spans size / PAGE_SIZE_4K index slots.