Commit 74fa5f3d authored Aug 21, 2016 by Chao Yu Committed by Jaegeuk Kim Sep 07, 2016

f2fs: schedule in between two continous batch discards



In batch discard approach of fstrim will grab/release gc_mutex lock
repeatly, it makes contention of the lock becoming more intensive.

So after one batch discards were issued in checkpoint and the lock
was released, it's better to do schedule() to increase opportunity
of grabbing gc_mutex lock for other competitors.

Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>

parent 97c1794a

fs/f2fs/segment.c

+2 −0

Original line number	Diff line number	Diff line
		@@ -1305,6 +1305,8 @@ int f2fs_trim_fs(struct f2fs_sb_info sbi, struct fstrim_range range)
		mutex_unlock(&sbi->gc_mutex);
		if (err)
		break;

		schedule();
		}
		out:
		range->len = F2FS_BLK_TO_BYTES(cpc.trimmed);