diff options
author | Tao Ma <tao.ma@oracle.com> | 2007-12-18 15:46:10 +0800 |
---|---|---|
committer | Mark Fasheh <mark.fasheh@oracle.com> | 2008-01-25 14:48:54 -0800 |
commit | e9d578a8f279d5e7d1e903f436aefc76ba330b43 (patch) | |
tree | ac5ee47053d00940d25f6dd9d2b23cb18e587cf0 /fs/jffs2/jffs2_fs_i.h | |
parent | 1252c434e39dc60ca9e8ed682f3e04930e2c08de (diff) |
ocfs2: Initalize bitmap_cpg of ocfs2_super to be the maximum.
This value is initialized from global_bitmap->id2.i_chain.cl_cpg. If there
is only 1 group, it will be equal to the total clusters in the volume. So
as for online resize, it should change for all the nodes in the cluster.
It isn't easy and there is no corresponding lock for it.
bitmap_cpg is only used in 2 areas:
1. Check whether the suballoc is too large for us to allocate from the global
bitmap, so it is little used. And now the suballoc size is 2048, it rarely
meet this situation and the check is almost useless.
2. Calculate which group a cluster belongs to. We use it during truncate to
figure out which cluster group an extent belongs too. But we should be OK
if we increase it though as the cluster group calculated shouldn't change
and we only ever have a small bitmap_cpg on file systems with a single
cluster group.
Signed-off-by: Tao Ma <tao.ma@oracle.com>
Signed-off-by: Mark Fasheh <mark.fasheh@oracle.com>
Diffstat (limited to 'fs/jffs2/jffs2_fs_i.h')
0 files changed, 0 insertions, 0 deletions