summaryrefslogtreecommitdiffstats
path: root/fs/f2fs/segment.c
diff options
context:
space:
mode:
authorJaegeuk Kim <jaegeuk.kim@samsung.com>2013-01-03 17:55:52 +0900
committerJaegeuk Kim <jaegeuk.kim@samsung.com>2013-01-10 07:42:59 +0900
commit408e9375610cca6d54e9c654cbe05a647687e12e (patch)
tree8bee0c5d2c8579721e81ba3d5689837a3d12be46 /fs/f2fs/segment.c
parentc335a86930b4841c11df12e1fdfd8345e0ebce84 (diff)
downloadblackbird-op-linux-408e9375610cca6d54e9c654cbe05a647687e12e.tar.gz
blackbird-op-linux-408e9375610cca6d54e9c654cbe05a647687e12e.zip
f2fs: revisit the f2fs_gc flow
I'd like to revisit the f2fs_gc flow and rewrite as follows. 1. In practical, the nGC parameter of f2fs_gc is meaningless. So, let's remove it. 2. Background GC marks victim blocks as dirty one at a time. 3. Foreground GC should do cleaning job until acquiring enough free sections. Afterwards, it needs to do checkpoint. Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Diffstat (limited to 'fs/f2fs/segment.c')
-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 de6240922b0a..4b0099066582 100644
--- a/fs/f2fs/segment.c
+++ b/fs/f2fs/segment.c
@@ -31,7 +31,7 @@ void f2fs_balance_fs(struct f2fs_sb_info *sbi)
*/
if (has_not_enough_free_secs(sbi)) {
mutex_lock(&sbi->gc_mutex);
- f2fs_gc(sbi, 1);
+ f2fs_gc(sbi);
}
}
OpenPOWER on IntegriCloud