diff options
| author | Jaegeuk Kim <jaegeuk.kim@samsung.com> | 2014-01-08 13:45:08 +0900 |
|---|---|---|
| committer | Ziyan <jaraidaniel@gmail.com> | 2015-05-02 14:36:06 +0200 |
| commit | 34fb847ddb689c459e2f3ff494c03471d9d9a547 (patch) | |
| tree | 9432db047b09a443b7f2071a5ec8a2d5a3a74fcf /fs/f2fs/segment.c | |
| parent | 1d6f03f2684700541bbb990924b0f26441b18eb2 (diff) | |
| download | kernel_samsung_tuna-34fb847ddb689c459e2f3ff494c03471d9d9a547.zip kernel_samsung_tuna-34fb847ddb689c459e2f3ff494c03471d9d9a547.tar.gz kernel_samsung_tuna-34fb847ddb689c459e2f3ff494c03471d9d9a547.tar.bz2 | |
f2fs: add a sysfs entry to control max_victim_search
Previously during SSR and GC, the maximum number of retrials to find a victim
segment was hard-coded by MAX_VICTIM_SEARCH, 4096 by default.
This number makes an effect on IO locality, when SSR mode is activated, which
results in performance fluctuation on some low-end devices.
If max_victim_search = 4, the victim will be searched like below.
("D" represents a dirty segment, and "*" indicates a selected victim segment.)
D1 D2 D3 D4 D5 D6 D7 D8 D9
[ * ]
[ * ]
[ * ]
[ ....]
This patch adds a sysfs entry to control the number dynamically through:
/sys/fs/f2fs/$dev/max_victim_search
Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Diffstat (limited to 'fs/f2fs/segment.c')
0 files changed, 0 insertions, 0 deletions