summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorLaibin Qiu <qiulaibin@huawei.com>2021-07-31 11:26:46 +0800
committerJaegeuk Kim <jaegeuk@kernel.org>2021-08-02 11:24:26 -0700
commitdc675a97129c4d9d5af55a3d7f23d7e092b8e032 (patch)
tree52a5b1dfa56d5feda627c4e2989cecf5885a0b48
parent2787991516468bfafafb9bf2b45a848e6b202e7c (diff)
downloadlinux-dc675a97129c4d9d5af55a3d7f23d7e092b8e032.tar.bz2
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>
-rw-r--r--fs/f2fs/segment.c2
1 files changed, 1 insertions, 1 deletions
diff --git a/fs/f2fs/segment.c b/fs/f2fs/segment.c
index f9b7fb785e1d..0f976cefe425 100644
--- a/fs/f2fs/segment.c
+++ b/fs/f2fs/segment.c
@@ -5159,7 +5159,7 @@ int f2fs_build_segment_manager(struct f2fs_sb_info *sbi)
sm_info->ipu_policy = 1 << F2FS_IPU_FSYNC;
sm_info->min_ipu_util = DEF_MIN_IPU_UTIL;
sm_info->min_fsync_blocks = DEF_MIN_FSYNC_BLOCKS;
- sm_info->min_seq_blocks = sbi->blocks_per_seg * sbi->segs_per_sec;
+ sm_info->min_seq_blocks = sbi->blocks_per_seg;
sm_info->min_hot_blocks = DEF_MIN_HOT_BLOCKS;
sm_info->min_ssr_sections = reserved_sections(sbi);