diff options
| author | Jaegeuk Kim <jaegeuk.kim@samsung.com> | 2014-01-08 10:09:51 +0900 |
|---|---|---|
| committer | rogersb11 <brettrogers11@gmail.com> | 2016-02-13 21:06:27 -0500 |
| commit | cc8c6bbf559cd5a87cff8435321877fe5f5266a5 (patch) | |
| tree | ae363179b668eb4f614e0b856a5d6d8a3ef249d4 /Kbuild | |
| parent | d4322cd694ca73be92c2b6f8d96226ba4734bd6a (diff) | |
| download | kernel_samsung_smdk4412-cc8c6bbf559cd5a87cff8435321877fe5f5266a5.zip kernel_samsung_smdk4412-cc8c6bbf559cd5a87cff8435321877fe5f5266a5.tar.gz kernel_samsung_smdk4412-cc8c6bbf559cd5a87cff8435321877fe5f5266a5.tar.bz2 | |
f2fs: improve write performance under frequent fsync calls
When considering a bunch of data writes with very frequent fsync calls, we
are able to think the following performance regression.
N: Node IO, D: Data IO, IO scheduler: cfq
Issue pending IOs
D1 D2 D3 D4
D1 D2 D3 D4 N1
D2 D3 D4 N1 N2
N1 D3 D4 N2 D1
--> N1 can be selected by cfq becase of the same priority of N and D.
Then D3 and D4 would be delayed, resuling in performance degradation.
So, when processing the fsync call, it'd better give higher priority to data IOs
than node IOs by assigning WRITE and WRITE_SYNC respectively.
This patch improves the random wirte performance with frequent fsync calls by up
to 10%.
Change-Id: I4812ac05db179d83914c7bb0942fa6738280e1ea
Signed-off-by: Jaegeuk Kim <jaegeuk.kim@samsung.com>
Diffstat (limited to 'Kbuild')
0 files changed, 0 insertions, 0 deletions