Refactor filesystem #225
Merged
Refactor filesystem #225
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 filesystem code was in one big file with tight coupling. This PR is splitting it into smaller files and refactoring everything to move toward multiple independent layers, with the VFS at the top, a block layer the middle, and physical devices at the bottom.
There is still a lot of work to be done but we can now support a filesystem on a disk or in memory. One issue is that the frame allocator is slow for a heap larger than a few megabytes, and another one is that neither the ram nor the disk is dynamically allocated using their full sizes. This will need to be addressed soon.
This PR also introduce some tests now that we can use a filesystem in memory. It was about time!