Searched hist:"408 e9375610cca6d54e9c654cbe05a647687e12e" (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/fs/f2fs/ |
| H A D | gc.c | diff 408e9375610cca6d54e9c654cbe05a647687e12e Thu Jan 03 02:55:52 CST 2013 Jaegeuk Kim <jaegeuk.kim@samsung.com> 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>
|
| H A D | segment.c | diff 408e9375610cca6d54e9c654cbe05a647687e12e Thu Jan 03 02:55:52 CST 2013 Jaegeuk Kim <jaegeuk.kim@samsung.com> 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>
|
| H A D | f2fs.h | diff 408e9375610cca6d54e9c654cbe05a647687e12e Thu Jan 03 02:55:52 CST 2013 Jaegeuk Kim <jaegeuk.kim@samsung.com> 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>
|