All of lore.kernel.org
 help / color / mirror / Atom feed
From: bpm@sgi.com
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-nfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [RFC PATCH 2/2] xfs_export_operations.commit_metadata
Date: Wed, 10 Feb 2010 14:15:27 -0600	[thread overview]
Message-ID: <20100210201527.GJ23654@sgi.com> (raw)
In-Reply-To: <20100210090750.GB21875@infradead.org>

Howdy,

On Wed, Feb 10, 2010 at 04:07:50AM -0500, Christoph Hellwig wrote:
> On Tue, Feb 09, 2010 at 06:33:37PM -0600, Ben Myers wrote:
> > hopefully
> > the XFS gurus can continue to provide guidance.
> 
> Ccing the xfs list would help with that :) 

I'll cross-post the next rev.  ;)

> > +		if (xfs_ipincount(c_xip)) {
> > +			/*
> > +			 * AFAICS the child is always modified after the parent
> > +			 * in nfsd so should always have a larger lsn.
> > +			 */
> > +			if (c_xip->i_itemp->ili_last_lsn > force_lsn) {
> > +				force_lsn = c_xip->i_itemp->ili_last_lsn;
> > +			} else {
> > +				force_lsn = 0; /* whole thing */
> > +			}
> 
> I wouldn't rely on that and always take the larger one.

I am concerned that ili_last_lsn will roll over at some point.  I
haven't figured out how to detect that yet.
 
> Now with the simplification of always having a non-zero first argument
> suggested in the previous mail this might be simplified down to:
> 
> STATIC int
> xfs_fs_nfs_commit_metadata(
> 	struct dentry		*parent,
> 	struct dentry		*child)
> {
> 	struct xfs_inode	*dp = XFS_I(parent->d_inode);
> 	struct xfs_inode	*ip = NULL;
> 	struct xfs_mount	*mp = dp->i_mount;
> 	xfs_lsn_t		force_lsn = 0;
> 	int			error = 0;
> 
> 	if (child) {
> 		ip = XFS_I(child->d_inode);
> 		xfs_lock_two_inodes(dp, ip, XFS_ILOCK_SHARED);
> 	} else {
> 		xfs_ilock(dp, XFS_ILOCK_SHARED);
> 	}
> 
> 	if (xfs_ipincount(dp))
> 		force_lsn = dp->i_itemp->ili_last_lsn;
> 	if (ip && xfs_ipincount(ip))
> 		force_lsn = max(force_lsn, ip->i_itemp->ili_last_lsn);
> 
+	if (force_lsn)
>	 	error = _xfs_log_force_lsn(mp, force_lsn, NULL);
> 
> 	if (ip)
> 		xfs_iunlock(ip, XFS_ILOCK_SHARED);
> 	xfs_iunlock(dp, XFS_ILOCK_SHARED);
> 
> 	return error;
> }

That's nice!

> Note that _xfs_log_force_lsn is new in the XFS tree, mainline still
> has _xfs_log_force with an lsn argument.

I've been working with Bruce's tree.  Not sure how best to handle that.

Thanks,
	Ben

WARNING: multiple messages have this Message-ID (diff)
From: bpm@sgi.com
To: Christoph Hellwig <hch@infradead.org>
Cc: linux-nfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [RFC PATCH 2/2] xfs_export_operations.commit_metadata
Date: Wed, 10 Feb 2010 14:15:27 -0600	[thread overview]
Message-ID: <20100210201527.GJ23654@sgi.com> (raw)
In-Reply-To: <20100210090750.GB21875@infradead.org>

Howdy,

On Wed, Feb 10, 2010 at 04:07:50AM -0500, Christoph Hellwig wrote:
> On Tue, Feb 09, 2010 at 06:33:37PM -0600, Ben Myers wrote:
> > hopefully
> > the XFS gurus can continue to provide guidance.
> 
> Ccing the xfs list would help with that :) 

I'll cross-post the next rev.  ;)

> > +		if (xfs_ipincount(c_xip)) {
> > +			/*
> > +			 * AFAICS the child is always modified after the parent
> > +			 * in nfsd so should always have a larger lsn.
> > +			 */
> > +			if (c_xip->i_itemp->ili_last_lsn > force_lsn) {
> > +				force_lsn = c_xip->i_itemp->ili_last_lsn;
> > +			} else {
> > +				force_lsn = 0; /* whole thing */
> > +			}
> 
> I wouldn't rely on that and always take the larger one.

I am concerned that ili_last_lsn will roll over at some point.  I
haven't figured out how to detect that yet.
 
> Now with the simplification of always having a non-zero first argument
> suggested in the previous mail this might be simplified down to:
> 
> STATIC int
> xfs_fs_nfs_commit_metadata(
> 	struct dentry		*parent,
> 	struct dentry		*child)
> {
> 	struct xfs_inode	*dp = XFS_I(parent->d_inode);
> 	struct xfs_inode	*ip = NULL;
> 	struct xfs_mount	*mp = dp->i_mount;
> 	xfs_lsn_t		force_lsn = 0;
> 	int			error = 0;
> 
> 	if (child) {
> 		ip = XFS_I(child->d_inode);
> 		xfs_lock_two_inodes(dp, ip, XFS_ILOCK_SHARED);
> 	} else {
> 		xfs_ilock(dp, XFS_ILOCK_SHARED);
> 	}
> 
> 	if (xfs_ipincount(dp))
> 		force_lsn = dp->i_itemp->ili_last_lsn;
> 	if (ip && xfs_ipincount(ip))
> 		force_lsn = max(force_lsn, ip->i_itemp->ili_last_lsn);
> 
+	if (force_lsn)
>	 	error = _xfs_log_force_lsn(mp, force_lsn, NULL);
> 
> 	if (ip)
> 		xfs_iunlock(ip, XFS_ILOCK_SHARED);
> 	xfs_iunlock(dp, XFS_ILOCK_SHARED);
> 
> 	return error;
> }

That's nice!

> Note that _xfs_log_force_lsn is new in the XFS tree, mainline still
> has _xfs_log_force with an lsn argument.

I've been working with Bruce's tree.  Not sure how best to handle that.

Thanks,
	Ben

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

  parent reply	other threads:[~2010-02-10 20:14 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-10  0:33 [RFC PATCH 0/2] nfsd sync export_op (was 'wsync export option') Ben Myers
2010-02-10  0:33 ` [RFC PATCH 1/2] commit_metadata export operation and nfsd_sync2 Ben Myers
2010-02-10  8:56   ` Christoph Hellwig
2010-02-10 19:53     ` bpm
2010-02-10 21:56       ` Christoph Hellwig
2010-02-10  0:33 ` [RFC PATCH 2/2] xfs_export_operations.commit_metadata Ben Myers
2010-02-10  9:07   ` Christoph Hellwig
2010-02-10  9:07     ` Christoph Hellwig
2010-02-10 10:11     ` Christoph Hellwig
2010-02-10 10:11       ` Christoph Hellwig
2010-02-10 20:15     ` bpm [this message]
2010-02-10 20:15       ` bpm
2010-02-10 21:29       ` Dave Chinner
2010-02-10 21:57       ` Christoph Hellwig
2010-02-10 21:57         ` 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=20100210201527.GJ23654@sgi.com \
    --to=bpm@sgi.com \
    --cc=hch@infradead.org \
    --cc=linux-nfs@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.