ocfs2: Store the ocfs2_caching_info on ocfs2_extent_tree.

Browse source

What do we cache?  Metadata blocks.  What are most of our non-inode metadata
blocks?  Extent blocks for our btrees.  struct ocfs2_extent_tree is the
main structure for managing those.  So let's store the associated
ocfs2_caching_info there.

This means that ocfs2_et_root_journal_access() doesn't need struct inode
anymore, and any place that has an et can refer to et->et_ci instead of
INODE_CACHE(inode).

Signed-off-by: Joel Becker <joel.becker@oracle.com>

...

This commit is contained in:

Joel Becker 2009-02-12 17:32:34 -08:00

parent 0cf2f7632b

commit d9a0a1f83b

2 changed files with 16 additions and 14 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

26

fs/ocfs2/alloc.c

View file

4

fs/ocfs2/alloc.h

View file