From: Christoph Hellwig <hch@infradead.org>
To: Brian Foster <bfoster@redhat.com>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH] xfs: don't trigger fsync log force based on inode pin count
Date: Wed, 22 Apr 2015 09:15:09 -0700 [thread overview]
Message-ID: <20150422161509.GA27237@infradead.org> (raw)
In-Reply-To: <1429713466-22137-1-git-send-email-bfoster@redhat.com>
On Wed, Apr 22, 2015 at 10:37:46AM -0400, Brian Foster wrote:
> There are probably a couple different ways to handle this. We could log
> the inode in the bmap cases in order to preserve the pincount check.
I'd favor that. For one performance should be better, second we really
need to dirty the inode anyway for v5 file systems as that's the
mechanism used to increment di_changecount.
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-04-22 16:15 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-22 14:37 [PATCH] xfs: don't trigger fsync log force based on inode pin count Brian Foster
2015-04-22 16:15 ` Christoph Hellwig [this message]
2015-04-22 17:13 ` Brian Foster
2015-04-22 21:18 ` Dave Chinner
2015-04-22 22:02 ` Brian Foster
2015-04-22 22:06 ` Christoph Hellwig
2015-04-22 22:10 ` Brian Foster
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=20150422161509.GA27237@infradead.org \
--to=hch@infradead.org \
--cc=bfoster@redhat.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox