diff options
| author | Chao Yu <yuchao0@huawei.com> | 2017-10-18 10:34:14 +0800 |
|---|---|---|
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | 2017-11-15 21:58:07 -0800 |
| commit | 03b1cb0bb4a2f4b1e512aa2b3dcaf22717e7e76e (patch) | |
| tree | 7e19228a8ef1e806e9bd5f3b54de089b265d1309 /tools/perf/scripts/python/netdev-times.py | |
| parent | 5c15033ceaea9900ecd1a5551a8080ee1a4abfdb (diff) | |
f2fs: fix to correct no_fggc_candidate
There may be extreme case as below:
For one section contains one segment, and there are total 100 segments
with 10% over-privision ratio in f2fs partition, fggc_threshold will
be rounded down to 460 instead of 460.8 as below caclulation:
sbi->fggc_threshold = div_u64((u64)(main_count - ovp_count) *
BLKS_PER_SEC(sbi), (main_count - resv_count));
If section usage is as:
60 segments which contain 460 valid blocks
40 segments which contain 462 valid blocks
As valid block number in all sections is large than fggc_threshold, so
none of them will be chosen as candidate due to incorrect fggc_threshold.
Let's just soften the term of choosing foreground GC candidates.
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'tools/perf/scripts/python/netdev-times.py')
0 files changed, 0 insertions, 0 deletions
