This repository was archived by the owner on Apr 10, 2024. It is now read-only.
f2fs: hardcode cp_interval to 200s after merging rapid GC #13
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.
In ("f2fs: rename /sys/fs/f2fs") mentions:
fsmgr and vold tries to read nodes from here and run GC by itself.
Since it conflicts with rapid GC(not to mention less effective), rename /sys/fs/f2fs to /sys/fs/f2fs_dev to avoid Android reading it entirely.
We could rename gc_urgent and dirty_segments but this approach seems better as it'll still be detected as a f2fs volume and try to run GC.
But also because of sysfs name change, we will lose AOSP F2FS tuning1.
Since our device is using ext4 by default, adding it to the device tree will add another useless warning, so it is hardcoded in the kernel
Change-Id: I747e9e20371719055f5fd6abaf0e47645c99ac64