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

[Christoph Hellwig <hch@xxxxxxxxxxxxx>]

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.