All of lore.kernel.org
 help / color / mirror / Atom feed
From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: hch@infradead.org, linux-fsdevel@vger.kernel.org, xfs@oss.sgi.com
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	[thread overview]
Message-ID: <20110803220344.GA9435@infradead.org> (raw)
In-Reply-To: <1312404545-15400-3-git-send-email-jack@suse.cz>

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.

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

WARNING: multiple messages have this Message-ID (diff)
From: Christoph Hellwig <hch@infradead.org>
To: Jan Kara <jack@suse.cz>
Cc: hch@infradead.org, xfs@oss.sgi.com, linux-fsdevel@vger.kernel.org
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	[thread overview]
Message-ID: <20110803220344.GA9435@infradead.org> (raw)
In-Reply-To: <1312404545-15400-3-git-send-email-jack@suse.cz>

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.


  reply	other threads:[~2011-08-03 22:03 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-03 20:49 [PATCH 0/2] Improve writeout pattern from xfs_flush_pages() Jan Kara
2011-08-03 20:49 ` Jan Kara
2011-08-03 20:49 ` [PATCH 1/2] vfs: Create filemap_flush_range() Jan Kara
2011-08-03 20:49   ` Jan Kara
2011-08-03 20:49 ` [PATCH 2/2] xfs: Call filemap_flush_range() for async xfs_flush_pages() call Jan Kara
2011-08-03 20:49   ` Jan Kara
2011-08-03 22:03   ` Christoph Hellwig [this message]
2011-08-03 22:03     ` Christoph Hellwig
2011-08-03 22:34   ` Vivek Goyal
2011-08-03 22:34     ` Vivek Goyal
2011-08-04 10:03     ` Jan Kara
2011-08-04 10:03       ` Jan Kara
2011-08-03 21:42 ` [PATCH 0/2] Improve writeout pattern from xfs_flush_pages() Christoph Hellwig
2011-08-03 21:42   ` Christoph Hellwig
2011-08-04 10:36   ` Jan Kara
2011-08-04 10:36     ` Jan Kara
2011-08-04 10:42     ` Christoph Hellwig
2011-08-04 10:42       ` Christoph Hellwig
2011-08-04 12:07       ` Jan Kara
2011-08-04 12:07         ` Jan Kara
2011-08-04 12:19         ` Christoph Hellwig
2011-08-04 12:19           ` Christoph Hellwig
2011-08-04 12:37           ` Jan Kara
2011-08-04 12:37             ` Jan Kara
2011-08-04 12:41             ` Christoph Hellwig
2011-08-04 12:41               ` Christoph Hellwig

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20110803220344.GA9435@infradead.org \
    --to=hch@infradead.org \
    --cc=jack@suse.cz \
    --cc=linux-fsdevel@vger.kernel.org \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.