f2fs: don't track newly allocated nat entry in list
authorChao Yu <yuchao0@huawei.com>
Mon, 5 Jun 2017 10:29:08 +0000 (18:29 +0800)
committerJaegeuk Kim <jaegeuk@kernel.org>
Tue, 4 Jul 2017 09:11:38 +0000 (02:11 -0700)
commitfebeca6d375531f2d3244b47bf0eb396180689e0
tree5f98dcd0589d0b465726f46cc32d51c3a719e9e5
parentd9703d9097d7c97f735a3b7870c52735a4dfa051
f2fs: don't track newly allocated nat entry in list

We will never persist newly allocated nat entries during checkpoint(), so
we don't need to track such nat entries in nat dirty list in order to
avoid:
- more latency during traversing dirty list;
- sorting nat sets incorrectly due to recording wrong entry_cnt in nat
entry set.

Signed-off-by: Chao Yu <yuchao0@huawei.com>
Signed-off-by: Jaegeuk Kim <jaegeuk@kernel.org>
fs/f2fs/node.c