Fix failure of block bitmap allocation on large NVM in failure recovery.#98
Merged
Andiry merged 1 commit intoNVSL:masterfrom Mar 28, 2021
Merged
Conversation
Contributor
|
Thanks for fixing this! |
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.
Currently, the block bitmaps are allocated by
kzalloc. However, the maximum size of space it can allocate is finite(typically 4MiB). So if the size of NVM is big enough(>128GiB), the size of block bitmap will exceed the maximum size of spacekzalloccan allocate, which will cause the failure of block bitmap allocation.This PR fixes it by allocating block bitmaps with
kvzalloc.