From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 5/7] writeback: make writeback_control.nr_to_write straight Date: Sun, 19 Jun 2011 11:35:36 -0400 Message-ID: <20110619153536.GB20424@infradead.org> References: <20110619150108.691351746@intel.com> <20110619150510.484877943@intel.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: "linux-fsdevel@vger.kernel.org" , Jan Kara , Dave Chinner , Christoph Hellwig , Andrew Morton , LKML To: Wu Fengguang Return-path: Received: from 173-166-109-252-newengland.hfc.comcastbusiness.net ([173.166.109.252]:39293 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754377Ab1FSPfh (ORCPT ); Sun, 19 Jun 2011 11:35:37 -0400 Content-Disposition: inline In-Reply-To: <20110619150510.484877943@intel.com> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: I'd rather see this earlier in the series, before the write bandwith estimation ones, as it's groundwork independ of those changes. > + if (wrote) { > + if (jiffies - start_time > HZ / 10UL) > + break; > + if (work->nr_pages <= 0) > + break; > + } This code probably wants some comments. > static void bdi_flush_io(struct backing_dev_info *bdi) > { > - struct writeback_control wbc = { > - .sync_mode = WB_SYNC_NONE, > - .older_than_this = NULL, > - .range_cyclic = 1, > - .nr_to_write = 1024, > - }; > - > - writeback_inodes_wb(&bdi->wb, &wbc); > + writeback_inodes_wb(&bdi->wb, 1024); > } At this point you could probably also kill the bdi_flush_io wrapper, and just call writeback_inodes_wb directly. A comment on the 1024 pages to write would be nice, if you remember it from poking the code. I can't find any good explanation for it offhand.