linux-toradex.git/fs/xfs/xfs_ialloc_btree.c, branch v3.2.37

xfs: remove leftovers of the old btree tracing code

2011-07-13T11:43:50+00:00

Remove various bits left over from the old kdb-only btree tracing code, but
leave the actual trace point stubs in place to ease adding new event based
btree tracing.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Alex Elder 
Reviewed-by: Dave Chinner

xfs: remove the ->kill_root btree operation

2010-10-18T20:07:38+00:00

The implementation os ->kill_root only differ by either simply
zeroing out the now unused buffer in the btree cursor in the inode
allocation btree or using xfs_btree_setbuf in the allocation btree.

Initially both of them used xfs_btree_setbuf, but the use in the
ialloc btree was removed early on because it interacted badly with
xfs_trans_binval.

In addition to zeroing out the buffer in the cursor xfs_btree_setbuf
updates the bc_ra array in the btree cursor, and calls
xfs_trans_brelse on the buffer previous occupying the slot.

The bc_ra update should be done for the alloc btree updated too,
although the lack of it does not cause serious problems.  The
xfs_trans_brelse call on the other hand is effectively a no-op in
the end - it keeps decrementing the bli_recur refcount until it hits
zero, and then just skips out because the buffer will always be
dirty at this point.  So removing it for the allocation btree is
just fine.

So unify the code and move it to xfs_btree.c.  While we're at it
also replace the call to xfs_btree_setbuf with a NULL bp argument in
xfs_btree_del_cursor with a direct call to xfs_trans_brelse given
that the cursor is beeing freed just after this and the state
updates are superflous.  After this xfs_btree_setbuf is only used
with a non-NULL bp argument and can thus be simplified.

Signed-off-by: Christoph Hellwig 
Signed-off-by: Alex Elder

xfs: remove unneeded #include statements

2010-07-26T18:16:33+00:00

Signed-off-by: Christoph Hellwig 
Reviewed-by: Dave Chinner

xfs: drop dmapi hooks

2010-07-26T18:16:33+00:00

Dmapi support was never merged upstream, but we still have a lot of hooks
bloating XFS for it, all over the fast pathes of the filesystem.

This patch drops over 700 lines of dmapi overhead.  If we'll ever get HSM
support in mainline at least the namespace events can be done much saner
in the VFS instead of the individual filesystem, so it's not like this
is much help for future work.

Signed-off-by: Christoph Hellwig 
Reviewed-by: Dave Chinner

xfs: fix various typos

2009-03-29T07:55:42+00:00

Signed-off-by: Malcolm Parsons 
Reviewed-by: Christoph Hellwig

[XFS] Always use struct xfs_btree_block instead of short / longform

2008-10-30T06:14:34+00:00

structures.

Always use the generic xfs_btree_block type instead of the short / long
structures. Add XFS_BTREE_SBLOCK_LEN / XFS_BTREE_LBLOCK_LEN defines for
the length of a short / long form block. The rationale for this is that we
will grow more btree block header variants to support CRCs and other RAS
information, and always accessing them through the same datatype with
unions for the short / long form pointers makes implementing this much
easier.

SGI-PV: 988146

SGI-Modid: xfs-linux-melb:xfs-kern:32300a

Signed-off-by: Christoph Hellwig 
Signed-off-by: Donald Douwsma 
Signed-off-by: David Chinner 
Signed-off-by: Lachlan McIlroy

[XFS] Cleanup maxrecs calculation.

2008-10-30T06:11:19+00:00

Clean up the way the maximum and minimum records for the btree blocks are
calculated. For the alloc and inobt btrees all the values are
pre-calculated in xfs_mount_common, and we switch the current loop around
the ugly generic macros that use cpp token pasting to generate type names
to two small helpers in normal C code. For the bmbt and bmdr trees these
helpers also exist, but can be called during runtime, too. Here we also
kill various macros dealing with them and inline the logic into the
get_minrecs / get_maxrecs / get_dmaxrecs methods in xfs_bmap_btree.c.

Note that all these new helpers take an xfs_mount * argument which will be
needed to determine the size of a btree block once we add support for
extended btree blocks with CRCs and other RAS information.

SGI-PV: 988146

SGI-Modid: xfs-linux-melb:xfs-kern:32292a

Signed-off-by: Christoph Hellwig 
Signed-off-by: Donald Douwsma 
Signed-off-by: Lachlan McIlroy

[XFS] add keys_inorder and recs_inorder btree methods

2008-10-30T05:58:32+00:00

Add methods to check whether two keys/records are in the righ order. This
replaces the xfs_btree_check_key and xfs_btree_check_rec methods. For the
callers from xfs_bmap.c just opencode the bmbt-specific asserts.

SGI-PV: 985583

SGI-Modid: xfs-linux-melb:xfs-kern:32208a

Signed-off-by: Christoph Hellwig 
Signed-off-by: Lachlan McIlroy 
Signed-off-by: Bill O'Donnell 
Signed-off-by: David Chinner

[XFS] implement generic xfs_btree_get_rec

2008-10-30T05:58:11+00:00

Not really much reason to make it generic given that it's so small, but
this is the last non-method in xfs_alloc_btree.c and xfs_ialloc_btree.c,
so it makes the whole btree implementation more structured.

SGI-PV: 985583

SGI-Modid: xfs-linux-melb:xfs-kern:32206a

Signed-off-by: Christoph Hellwig 
Signed-off-by: Lachlan McIlroy 
Signed-off-by: Bill O'Donnell 
Signed-off-by: David Chinner

[XFS] implement generic xfs_btree_delete/delrec

2008-10-30T05:58:01+00:00

Make the btree delete code generic. Based on a patch from David Chinner
with lots of changes to follow the original btree implementations more
closely. While this loses some of the generic helper routines for
inserting/moving/removing records it also solves some of the one off bugs
in the original code and makes it easier to verify.

SGI-PV: 985583

SGI-Modid: xfs-linux-melb:xfs-kern:32205a

Signed-off-by: Christoph Hellwig 
Signed-off-by: Lachlan McIlroy 
Signed-off-by: Bill O'Donnell 
Signed-off-by: David Chinner