xfs: Don't directly reference m_perag in allocation code
authorDave Chinner <david@fromorbit.com>
Mon, 11 Jan 2010 11:47:41 +0000 (11:47 +0000)
committerAlex Elder <aelder@sgi.com>
Fri, 15 Jan 2010 21:33:12 +0000 (15:33 -0600)
commita862e0fdcb8862aab2538ec2fc2f0dc07a625c59
tree41e83f478c9414e3376e99aa8565c67cc9930764
parent5017e97d52628fb8ae56e434e86ac2e72ddaac2b
xfs: Don't directly reference m_perag in allocation code

Start abstracting the perag references so that the indexing of the
structures is not directly coded into all the places that uses the
perag structures. This will allow us to separate the use of the
perag structure and the way it is indexed and hence avoid the known
deadlocks related to growing a busy filesystem.

Signed-off-by: Dave Chinner <david@fromorbit.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Alex Elder <aelder@sgi.com>
fs/xfs/xfs_alloc.c
fs/xfs/xfs_alloc_btree.c