From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 01/17] writeback: introduce .tagged_sync for the WB_SYNC_NONE sync stage Date: Fri, 13 May 2011 06:17:07 -0400 Message-ID: <20110513101707.GA17434@infradead.org> References: <20110512135706.937596128@intel.com> <20110512140030.759385136@intel.com> <20110512224013.GH19446@dastard> <20110513025607.GA8016@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Dave Chinner , Andrew Morton , Jan Kara , Christoph Hellwig , "linux-fsdevel@vger.kernel.org" , LKML To: Wu Fengguang Return-path: Content-Disposition: inline In-Reply-To: <20110513025607.GA8016@localhost> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org On Fri, May 13, 2011 at 10:56:08AM +0800, Wu Fengguang wrote: > > What about all the filesystems that implement their own > > .writepages()/write_cache_pages() functions or have > > have special code that checks WB_SYNC_ALL in .writepages (e.g. gfs2, > > ext4, btrfs and perhaps others). Don't they all need to be aware of > > this tagged_sync field? > > Right, good point. Currently only ext4 is updated. The other > filesystems --- afs, btrfs, cifs, gfs2 --- do not even use > PAGECACHE_TAG_TOWRITE for livelock prevention. My plan was to add > PAGECACHE_TAG_TOWRITE and tagged_sync code to them as the next step, > when tagged_sync is accepted and proved to work fine. I think it would be better to try to figure out why these filesystems need to duplicate that functionality and figure out if there's any way to make them use the generic code. But given that we need to get some writeback updates ready for .40 it might be worth to postponed that and go down the copy & paste route for now.