From mboxrd@z Thu Jan 1 00:00:00 1970 From: Damien Wyart Subject: Re: writeout stalls in current -git Date: Tue, 20 Nov 2007 14:16:17 +0100 Message-ID: <20071120131617.GA24166@localhost.localdomain> References: <64bb37e0711011200n228e708eg255640388f83da22@mail.gmail.com> <1193998532.27652.343.camel@twins> <64bb37e0711021222q7d12c825mc62d433c4fe19e8@mail.gmail.com> <394340668.31055@ustc.edu.cn> <64bb37e0711061353g4a8b881cgd78fef3a11378b9c@mail.gmail.com> <20071106233114.GB995458@sgi.com> <20071107021324.GD995458@sgi.com> <64bb37e0711062315jef9efd7xc2ffc11b6d6c60fa@mail.gmail.com> <20071108003811.GP995458@sgi.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: Torsten Kaiser , Fengguang Wu , Peter Zijlstra , Maxim Levitsky , linux-kernel@vger.kernel.org, Andrew Morton , linux-fsdevel@vger.kernel.org To: David Chinner Return-path: Content-Disposition: inline In-Reply-To: <20071108003811.GP995458@sgi.com> Sender: linux-kernel-owner@vger.kernel.org List-Id: linux-fsdevel.vger.kernel.org Hello, > > > Ok, so it's not synchronous writes that we are doing - we're just > > > submitting bio's tagged as WRITE_SYNC to get the I/O issued > > > quickly. The "synchronous" nature appears to be coming from higher > > > level locking when reclaiming inodes (on the flush lock). It > > > appears that inode write clustering is failing completely so we > > > are writing the same block multiple times i.e. once for each inode > > > in the cluster we have to write. > > Works for me. The only remaining stalls are sub second and look > > completely valid, considering the amount of files being removed. > .... > > Tested-by: Torsten Kaiser * David Chinner [2007-11-08 11:38]: > Great - thanks for reporting the problem and testing the fix. This patch has not yet made its way into 2.6.24 (rc3). Is it intended? Maybe the fix can wait for 2.6.25, but wanted to make sure... -- Damien Wyart