summaryrefslogtreecommitdiffstats
path: root/fs/f2fs/gc.c
diff options
context:
space:
mode:
authorChao Yu <yuchao0@huawei.com>2016-11-16 10:41:20 +0800
committerJaegeuk Kim <jaegeuk@kernel.org>2016-11-25 10:15:59 -0800
commit36951b38d13ac7cce9fcf89e0e01c22ed0d05688 (patch)
tree1d04f0c34e4f80b65a1957c6a7ce0e865bc927a3 /fs/f2fs/gc.c
parentc79b7ff1d3c7710c23d8828a69d8cbc5597ad19f (diff)
downloadlinux-36951b38d13ac7cce9fcf89e0e01c22ed0d05688.tar.bz2
f2fs: don't wait writeback for datas during checkpoint
Normally, while committing checkpoint, we will wait on all pages to be writebacked no matter the page is data or metadata, so in scenario where there are lots of data IO being submitted with metadata, we may suffer long latency for waiting writeback during checkpoint. Indeed, we only care about persistence for pages with metadata, but not pages with data, as file system consistent are only related to metadate, so in order to avoid encountering long latency in above scenario, let's recognize and reference metadata in submitted IOs, wait writeback only for metadatas. Signed-off-by: Chao Yu <yuchao0@huawei.com> Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
Diffstat (limited to 'fs/f2fs/gc.c')
-rw-r--r--fs/f2fs/gc.c2
1 files changed, 0 insertions, 2 deletions
diff --git a/fs/f2fs/gc.c b/fs/f2fs/gc.c
index 36f6cfc613d3..5c2fe68be549 100644
--- a/fs/f2fs/gc.c
+++ b/fs/f2fs/gc.c
@@ -693,8 +693,6 @@ retry:
congestion_wait(BLK_RW_ASYNC, HZ/50);
goto retry;
}
-
- clear_cold_data(page);
}
out:
f2fs_put_page(page, 1);