f2fs: fix min_seq_blocks can not make sense in some scenes.
authorLaibin Qiu <qiulaibin@huawei.com>
Sat, 31 Jul 2021 03:26:46 +0000 (11:26 +0800)
committerJaegeuk Kim <jaegeuk@kernel.org>
Mon, 2 Aug 2021 18:24:26 +0000 (11:24 -0700)
commitdc675a97129c4d9d5af55a3d7f23d7e092b8e032
tree52a5b1dfa56d5feda627c4e2989cecf5885a0b48
parent2787991516468bfafafb9bf2b45a848e6b202e7c
f2fs: fix min_seq_blocks can not make sense in some scenes.

F2FS have dirty page count control for batched sequential
write in writepages, and get the value of min_seq_blocks by
blocks_per_seg * segs_per_sec(segs_per_sec defaults to 1).
But in some scenes we set a lager section size, Min_seq_blocks
will become too large to achieve the expected effect(eg. 4thread
sequential write, the number of merge requests will be reduced).

Signed-off-by: Laibin Qiu <qiulaibin@huawei.com>
Reviewed-by: Chao Yu <chao@kernel.org>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
fs/f2fs/segment.c