xfs: rationalise xfs_mount_wq users
authorDave Chinner <dchinner@redhat.com>
Mon, 8 Oct 2012 10:56:00 +0000 (21:56 +1100)
committerBen Myers <bpm@sgi.com>
Wed, 17 Oct 2012 16:25:06 +0000 (11:25 -0500)
commit7e18530bef6a18a5479690ae7e8256319ecf1300
tree01b336aed89889bf654327346742956abe0a5d45
parent33c7a2bc48a81fa714572f8ce29f29bc17e6faf0
xfs: rationalise xfs_mount_wq users

Instead of starting and stopping background work on the xfs_mount_wq
all at the same time, separate them to where they really are needed
to start and stop.

The xfs_sync_worker, only needs to be started after all the mount
processing has completed successfully, while it needs to be stopped
before the log is unmounted.

The xfs_reclaim_worker is started on demand, and can be
stopped before the unmount process does it's own inode reclaim pass.

The xfs_flush_inodes work is run on demand, and so we really only
need to ensure that it has stopped running before we start
processing an unmount, freeze or remount,ro.

Signed-off-by: Dave Chinner <dchinner@redhat.com>
Reviewed-by: Mark Tinguely <tinguely@sgi.com>
Reviewed-by: Christoph Hellwig <hch@lst.de>
Signed-off-by: Ben Myers <bpm@sgi.com>
fs/xfs/xfs_mount.c
fs/xfs/xfs_super.c
fs/xfs/xfs_sync.c