From mboxrd@z Thu Jan 1 00:00:00 1970 From: Christoph Hellwig Subject: Re: [PATCH 2/2] xfs: Call filemap_flush_range() for async xfs_flush_pages() call Date: Wed, 3 Aug 2011 18:03:44 -0400 Message-ID: <20110803220344.GA9435@infradead.org> References: <1312404545-15400-1-git-send-email-jack@suse.cz> <1312404545-15400-3-git-send-email-jack@suse.cz> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Cc: hch@infradead.org, xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org To: Jan Kara Return-path: Received: from 173-166-109-252-newengland.hfc.comcastbusiness.net ([173.166.109.252]:56931 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753714Ab1HCWDr (ORCPT ); Wed, 3 Aug 2011 18:03:47 -0400 Content-Disposition: inline In-Reply-To: <1312404545-15400-3-git-send-email-jack@suse.cz> Sender: linux-fsdevel-owner@vger.kernel.org List-ID: On Wed, Aug 03, 2011 at 10:49:05PM +0200, Jan Kara wrote: > XFS does its own data writeout from several places using xfs_flush_pages(). > When this writeout is racing with flusher thread writing the same inode the > performance gets bad because flusher thread submits writes as normal WRITE > commands while xfs_flush_pages() submits them as WRITE_SYNC (as it uses Oh, I think you really want commit xfs: improve sync behaviour in the face of aggressive dirtying for your vendor tree.