From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 2/6] writeback: introduce writeback_control.inodes_cleaned Date: Wed, 4 May 2011 07:16:47 -0400 Message-ID: <20110504111647.GA19261@infradead.org> References: <20110420080336.441157866@intel.com> <20110420080917.890756812@intel.com> <20110504110500.GB4646@infradead.org> <20110504111130.GA5191@localhost> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Christoph Hellwig , Andrew Morton , Jan Kara , Mel Gorman , Mel Gorman , Dave Chinner , Itaru Kitayama , Minchan Kim , Linux Memory Management List , "linux-fsdevel@vger.kernel.org" , LKML To: Wu Fengguang Return-path: Content-Disposition: inline In-Reply-To: <20110504111130.GA5191@localhost> Sender: owner-linux-mm@kvack.org List-Id: linux-fsdevel.vger.kernel.org On Wed, May 04, 2011 at 07:11:30PM +0800, Wu Fengguang wrote: > On Wed, May 04, 2011 at 07:05:00PM +0800, Christoph Hellwig wrote: > > Same here - this has nothing to do with actual page writeback and really > > should stay internal to fs/fs-writeback.c > > OK, I'll check how to constrain writeback_control to the minimal scope. The basic idea would be to pass the struct wb_writeback_work all the way down to writeback_sb_inodes, and initialize the struct writeback_control there. This requires adding a few more fields like more_io and older_than_this to struct wb_writeback_work, and redoing a lot of the tracing, but it immediately clean things up, e.g. suddently wbc.nr_to_write vs work->nr_pages starts to make sense, and instead of saving and restoring pages_skipped in writeback_sb_inodes it can always start with a clean zero value. -- To unsubscribe, send a message with 'unsubscribe linux-mm' in the body to majordomo@kvack.org. For more info on Linux MM, see: http://www.linux-mm.org/ . Fight unfair telecom internet charges in Canada: sign http://stopthemeter.ca/ Don't email: email@kvack.org