ocfs2: Abstract ocfs2_extent_tree in b-tree operations.
In the old extent tree operation, we take the hypothesis that we are using the ocfs2_extent_list in ocfs2_dinode as the tree root. As xattr will also use ocfs2_extent_list to store large value for a xattr entry, we refactor the tree operation so that xattr can use it directly. The refactoring includes 4 steps: 1. Abstract set/get of last_eb_blk and update_clusters since they may be stored in different location for dinode and xattr. 2. Add a new structure named ocfs2_extent_tree to indicate the extent tree the operation will work on. 3. Remove all the use of fe_bh and di, use root_bh and root_el in extent tree instead. So now all the fe_bh is replaced with et->root_bh, el with root_el accordingly. 4. Make ocfs2_lock_allocators generic. Now it is limited to be only used in file extend allocation. But the whole function is useful when we want to store large EAs. Note: This patch doesn't touch ocfs2_commit_truncate() since it is not used for anything other than truncate inode data btrees. Signed-off-by:Tao Ma <tao.ma@oracle.com> Signed-off-by:
Mark Fasheh <mfasheh@suse.com>
Showing
- fs/ocfs2/alloc.c 327 additions, 181 deletionsfs/ocfs2/alloc.c
- fs/ocfs2/alloc.h 16 additions, 7 deletionsfs/ocfs2/alloc.h
- fs/ocfs2/aops.c 9 additions, 2 deletionsfs/ocfs2/aops.c
- fs/ocfs2/dir.c 4 additions, 3 deletionsfs/ocfs2/dir.c
- fs/ocfs2/file.c 13 additions, 91 deletionsfs/ocfs2/file.c
- fs/ocfs2/file.h 0 additions, 4 deletionsfs/ocfs2/file.h
- fs/ocfs2/suballoc.c 82 additions, 0 deletionsfs/ocfs2/suballoc.c
- fs/ocfs2/suballoc.h 5 additions, 0 deletionsfs/ocfs2/suballoc.h
Loading
Please register or sign in to comment