linux-toradex.git/fs/xfs/xfs_rtalloc.c, branch v3.0.74

xfs: Convert remaining cmn_err() callers to new API

2011-03-06T23:08:35+00:00

Once converted, kill the remainder of the cmn_err() interface.

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

xfs: stop using xfs_trans_iget in the RT allocator

2011-02-23T02:30:21+00:00

During mount we establish references to the RT inodes, which we keep for
the lifetime of the filesystem.  Instead of using xfs_trans_iget to grab
additional references when adding RT inodes to transactions use the
combination of xfs_ilock and xfs_trans_ijoin_ref, which archives the same
end result with less overhead.

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

xfs: add lockdep annotations for the rt inodes

2011-02-07T19:29:18+00:00

The rt bitmap and summary inodes do not participate in the normal inode
locking protocol.  Instead the rt bitmap inode can be locked in any
transaction involving rt allocations, and the both of the rt inodes can
be locked at the same time.  Add specific lockdep subclasses for the rt
inodes to prevent lockdep from blowing up.

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

xfs: only lock the rt bitmap inode once per allocation

2011-02-07T19:29:06+00:00

Currently both xfs_rtpick_extent and xfs_rtallocate_extent call
xfs_trans_iget to grab and lock the rt bitmap inode, which results in a
deadlock since the removal of the lock recursion counters in commit

	"xfs: simplify inode to transaction joining"

Fix this by acquiring and locking the inode in xfs_bmap_rtalloc before
calling into xfs_rtpick_extent and xfs_rtallocate_extent.

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

xfs: use unhashed buffers for size checks

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

When we are checking we can access the last block of each device, we
do not need to use cached buffers as they will be tossed away
immediately. Use uncached buffers for size checks so that all IO
prior to full in-memory structure initialisation does not use the
buffer cache.

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

xfs: remove unused delta tracking code in xfs_bmapi

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

This code was introduced four years ago in commit
3e57ecf640428c01ba1ed8c8fc538447ada1715b without any review and has
been unused since.  Remove it just as the rest of the code introduced
in that commit to reduce that stack usage and complexity in this central
piece of code.

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

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: remove block number from inode lookup code

2010-06-24T01:35:17+00:00

The block number comes from bulkstat based inode lookups to shortcut
the mapping calculations. We ar enot able to trust anything from
bulkstat, so drop the block number as well so that the correct
lookups and mappings are always done.

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

xfs: replace E2BIG with EFBIG where appropriate

2010-05-28T19:58:16+00:00

Many places in the xfs code return E2BIG when they really mean
EFBIG; trying to grow past 16T on a 32 bit machine, for example,
says "Argument list too long" rather than "File too large" which is
not particularly helpful.

Some of these don't make perfect sense as EFBIG either, but still
better than E2BIG IMHO.

Signed-off-by: Eric Sandeen 
Reviewed-by: Christoph Hellwig 
Signed-off-by: Alex Elder