From: Alex Elder <aelder@sgi.com>
To: Christoph Hellwig <hch@infradead.org>
Cc: xfs@oss.sgi.com
Subject: Re: [PATCH 1/3] xfs: unlock the inode before log force in xfs_fsync
Date: Thu, 29 Sep 2011 11:59:45 -0500 [thread overview]
Message-ID: <1317315585.3049.30.camel@doink> (raw)
In-Reply-To: <20110918204909.860669185@bombadil.infradead.org>
On Sun, 2011-09-18 at 16:47 -0400, Christoph Hellwig wrote:
> Only read the LSN we need to push to with the ilock held, and then release
> it before we do the log force to improve concurrency.
>
> This also removes the only direct caller of _xfs_trans_commit, thus
> allowing it to be merged into the plain xfs_trans_commit again.
>
> Signed-off-by: Christoph Hellwig <hch@lst.de>
Looks good.
The idea here is that once the transaction is committed
(which also sets the LSN to use), everything we need to
know about any changes are in the log so there's no need
to prevent others from moving on from that point--allowing
the inode to (transactionally) change to a new state--while
the log gets forced out. Right?
Reviewed-by: Alex Elder <aelder@sgi.com>
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2011-09-29 16:59 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-18 20:47 [PATCH 0/3] try to avoid locked inodes during log force Christoph Hellwig
2011-09-18 20:47 ` [PATCH 1/3] xfs: unlock the inode before log force in xfs_fsync Christoph Hellwig
2011-09-18 22:59 ` Dave Chinner
2011-09-19 14:55 ` [PATCH 1/3 v2] " Christoph Hellwig
2011-09-29 16:59 ` Alex Elder [this message]
2011-09-18 20:47 ` [PATCH 2/3] xfs: unlock the inode before log force in xfs_fs_nfs_commit_metadata Christoph Hellwig
2011-09-18 23:00 ` Dave Chinner
2011-09-29 16:59 ` Alex Elder
2011-09-18 20:47 ` [PATCH 3/3] xfs: unlock the inode before log force in xfs_change_file_space Christoph Hellwig
2011-09-18 23:00 ` Dave Chinner
2011-09-29 16:59 ` Alex Elder
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=1317315585.3049.30.camel@doink \
--to=aelder@sgi.com \
--cc=hch@infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox