| commit | 4b270a8cc5047682f0a3f3f9af3b498408dbd2bc | |
| author | Chao Yu <yuchao0@huawei.com> | |
| Wed, 4 Jul 2018 10:04:10 +0000 (4 18:04 +0800) | ||
| committer | Jaegeuk Kim <jaegeuk@kernel.org> | |
| Sun, 29 Jul 2018 01:26:08 +0000 (28 18:26 -0700) | ||
| tree | 134cb65533577abc680ad9e97383232678664c7a | treesnapshot (tar.gz zip) |
| parent | dc1328027b53586cc6b668c6654f9482e505699c | commitdiff |
f2fs: try grabbing node page lock aggressively in sync scenario
In synchronous scenario, like in checkpoint(), we are going to flush
dirty node pages to device synchronously, we can easily failed
writebacking node page due to trylock_page() failure, especially in
condition of intensive lock competition, which can cause long latency
of checkpoint(). So let's use lock_page() in synchronous scenario to
avoid this issue.
Signed-off-by: Yunlei He <heyunlei@huawei.com>
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
In synchronous scenario, like in checkpoint(), we are going to flush
dirty node pages to device synchronously, we can easily failed
writebacking node page due to trylock_page() failure, especially in
condition of intensive lock competition, which can cause long latency
of checkpoint(). So let's use lock_page() in synchronous scenario to
avoid this issue.
Signed-off-by: Yunlei He <heyunlei@huawei.com>
Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
| fs/f2fs/node.c | diffblobblamehistory |