Searched hist:da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f (Results 1 – 3 of 3) sorted by relevance
| /openbmc/linux/fs/f2fs/ |
| H A D | gc.c | diff da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f Wed Apr 27 08:40:15 CDT 2016 Chao Yu <yuchao0@huawei.com> f2fs: move node pages only in victim section during GC
For foreground GC, we cache node blocks in victim section and set them
dirty, then we call sync_node_pages to flush these node pages, but
meanwhile, those node pages which does not locate in victim section
will be flushed together, so more bandwidth and continuous free space
would be occupied.
So for this condition, it's better to leave those unrelated node page
in cache for further write hit, and let CP or VM to flush them afterward.
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | node.c | diff da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f Wed Apr 27 08:40:15 CDT 2016 Chao Yu <yuchao0@huawei.com> f2fs: move node pages only in victim section during GC
For foreground GC, we cache node blocks in victim section and set them
dirty, then we call sync_node_pages to flush these node pages, but
meanwhile, those node pages which does not locate in victim section
will be flushed together, so more bandwidth and continuous free space
would be occupied.
So for this condition, it's better to leave those unrelated node page
in cache for further write hit, and let CP or VM to flush them afterward.
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|
| H A D | f2fs.h | diff da011cc0da8cf4a60ddf4d2ae8b42902a3d71e5f Wed Apr 27 08:40:15 CDT 2016 Chao Yu <yuchao0@huawei.com> f2fs: move node pages only in victim section during GC
For foreground GC, we cache node blocks in victim section and set them
dirty, then we call sync_node_pages to flush these node pages, but
meanwhile, those node pages which does not locate in victim section
will be flushed together, so more bandwidth and continuous free space
would be occupied.
So for this condition, it's better to leave those unrelated node page
in cache for further write hit, and let CP or VM to flush them afterward.
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
|