xfs
[Top] [All Lists]

Re: [PATCH 2/2] xfs: Call filemap_flush_range() for async xfs_flush_page

To: Jan Kara <jack@xxxxxxx>
Subject: Re: [PATCH 2/2] xfs: Call filemap_flush_range() for async xfs_flush_pages() call
From: Christoph Hellwig <hch@xxxxxxxxxxxxx>
Date: Wed, 3 Aug 2011 18:03:44 -0400
Cc: hch@xxxxxxxxxxxxx, xfs@xxxxxxxxxxx, linux-fsdevel@xxxxxxxxxxxxxxx
In-reply-to: <1312404545-15400-3-git-send-email-jack@xxxxxxx>
References: <1312404545-15400-1-git-send-email-jack@xxxxxxx> <1312404545-15400-3-git-send-email-jack@xxxxxxx>
User-agent: Mutt/1.5.21 (2010-09-15)
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.

<Prev in Thread] Current Thread [Next in Thread>