Re: [PATCH 2/5] xfs: cleanup ->sync

xfs

Re: [PATCH 2/5] xfs: cleanup ->sync_fs

To:	Eric Sandeen <sandeen@xxxxxxxxxxx>
Subject:	Re: [PATCH 2/5] xfs: cleanup ->sync_fs
From:	Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date:	Mon, 11 May 2009 16:11:27 -0400
Cc:	Christoph Hellwig <hch@xxxxxxxxxxxxx>, xfs@xxxxxxxxxxx
In-reply-to:	<4A07141A.5060303@xxxxxxxxxxx>
References:	<20090426140305.113371000@xxxxxxxxxxxxxxxxxxxxxx> <20090426140707.713299000@xxxxxxxxxxxxxxxxxxxxxx> <4A07141A.5060303@xxxxxxxxxxx>
User-agent:	Mutt/1.5.18 (2008-05-17)

On Sun, May 10, 2009 at 12:51:22PM -0500, Eric Sandeen wrote:
> Is it worth keeping a comment about this still being similar to the
> freeze path?  (xfs_quiesce_data)

Don't think so.  The commonality is in xfs_quiesce_data, and both
calling this functions for the majority of the work makes that quite
obvious.

[More with this subject...]

<Prev in Thread]	Current Thread	[Next in Thread>
Re: [PATCH 2/5] xfs: cleanup ->sync_fs, Eric Sandeen Re: [PATCH 2/5] xfs: cleanup ->sync_fs, Christoph Hellwig <=

Previous by Date:	Re: [PATCH] xfs: update max log size, Christoph Hellwig
Next by Date:	Re: [PATCH 5/5] xfs: fix xfs_quiesce_data, Christoph Hellwig
Previous by Thread:	Re: [PATCH 2/5] xfs: cleanup ->sync_fs, Eric Sandeen
Next by Thread:	Re: [PATCH 3/5] xfs: make inodes dirty before issuing I/O, Eric Sandeen
Indexes:	[Date] [Thread] [Top] [All Lists]