linux.git/fs/f2fs/extent_cache.c, branch v4.5

f2fs: skip releasing nodes in chindless extent tree

2016-01-08T19:57:18+00:00

If there are no nodes in extent tree, let's skip releasing step to avoid
any overhead of grabbing/releasing extent tree lock.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: use atomic type for node count in extent tree

2016-01-08T19:57:11+00:00

1. rename field in struct extent_tree from count to node_cnt for
   readability.
2. alter to use atomic type for node_cnt.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: introduce zombie list for fast shrinking extent trees

2015-12-31T23:39:22+00:00

This patch removes refcount, and instead, adds zombie_list to shrink directly
without radix tree traverse.

Signed-off-by: Jaegeuk Kim

f2fs: load largest extent all the time

2015-12-30T18:14:20+00:00

Otherwise, we can get mismatched largest extent information.

One example is:
1. mount f2fs w/ extent_cache
2. make a small extent
3. umount
4. mount f2fs w/o extent_cache
5. update the largest extent
6. umount
7. mount f2fs w/ extent_cache
8. get the old extent made by #2

Signed-off-by: Jaegeuk Kim

f2fs: speed up shrinking extent tree entries

2015-12-30T18:13:00+00:00

If there is no candidates for shrinking slab entries, we don't need to traverse
any trees at all.

Reviewed-by: Chao Yu 
[Jaegeuk Kim: fix missing initialization reported by Yunlei He]
Signed-off-by: Jaegeuk Kim

f2fs: use atomic variable for total_extent_tree

2015-12-22T18:31:41+00:00

It would be better to use atomic variable for total_extent_tree.

Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: kill f2fs_drop_largest_extent

2015-12-04T20:07:57+00:00

For direct IO, f2fs only allocate new address for the block which is not
exist in the disk before, its mapping info should not exist in extent
cache previously, so here we do not need to call f2fs_drop_largest_extent
to drop related cache.

Due to no more callers for f2fs_drop_largest_extent now, kill it.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: avoid deadlock in f2fs_shrink_extent_tree

2015-12-04T19:52:36+00:00

While handling extent trees, we can enter into a reclaiming path anytime.
If it tries to release some extent nodes in the same extent tree,
write_lock(&et->lock) would be hanged.
In order to avoid the deadlock, we can just skip it.

Note that, if it is an unreferenced tree, we should get write_lock(&et->lock)
successfully and release all of therein nodes.

Reviewed-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: fix to skip shrinking extent nodes

2015-10-22T16:39:35+00:00

In f2fs_shrink_extent_tree we should stop shrink flow if we have already
shrunk enough nodes in extent cache.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim

f2fs: introduce __try_update_largest_extent

2015-10-09T23:20:53+00:00

This patch adds a new helper __try_update_largest_extent for cleanup.

Signed-off-by: Chao Yu 
Signed-off-by: Jaegeuk Kim