Chao Yu 7e515b31d4 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>
2017-10-26 10:44:24 +02:00
..
2016-09-14 16:52:36 -07:00
2017-10-26 10:44:21 +02:00
2017-10-10 12:49:53 -07:00
2017-10-10 12:49:53 -07:00
2017-10-26 10:44:16 +02:00
2017-10-26 10:44:21 +02:00
2017-10-26 10:44:21 +02:00
2017-10-10 12:49:53 -07:00
2017-10-26 10:44:08 +02:00