diff options
| author | Jaegeuk Kim <jaegeuk.kim@samsung.com> | 2014-01-08 13:45:08 +0900 |
|---|---|---|
| committer | rogersb11 <brettrogers11@gmail.com> | 2016-02-13 21:16:17 -0500 |
| commit | ea223f7943631e3cda16995db1da0e71fde6eb03 (patch) | |
| tree | a897899c218c37665964ef7013b745a44e439148 /fs/f2fs/inline.c | |
| parent | cc8c6bbf559cd5a87cff8435321877fe5f5266a5 (diff) | |
| download | kernel_samsung_smdk4412-ea223f7943631e3cda16995db1da0e71fde6eb03.zip kernel_samsung_smdk4412-ea223f7943631e3cda16995db1da0e71fde6eb03.tar.gz kernel_samsung_smdk4412-ea223f7943631e3cda16995db1da0e71fde6eb03.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
Change-Id: I0f98609540351fd7451e3c23bc65f8d165ba13b6
Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Diffstat (limited to 'fs/f2fs/inline.c')
0 files changed, 0 insertions, 0 deletions