From: "J. Bruce Fields" <bfields@fieldses.org>
To: Ben Myers <bpm@sgi.com>
Cc: linux-nfs@vger.kernel.org, xfs@oss.sgi.com
Subject: Re: [PATCH 0/2] commit_metadata export operation v5
Date: Tue, 16 Feb 2010 21:39:48 -0500 [thread overview]
Message-ID: <20100217023948.GB32315@fieldses.org> (raw)
In-Reply-To: <20100216210026.5694.14423.stgit@case>
On Tue, Feb 16, 2010 at 03:04:08PM -0600, Ben Myers wrote:
> Here is the latest version of the knfsd sync changes that I've been spamming
> you with.
Don't worry about spamming--it's good that people have lots of comments!
--b.
> I have addressed the latest suggestions provided by Christoph,
> Trond, Dave, and Alex. This version of the commit_metadata export operation
> takes only one inode as suggested by Christoph and it turns out to be much
> cleaner this way. Now we've gone back to committing all of the time in
> nfsd_create_setattr and don't bother with the added argument. A couple extra
> comments to explain the commit ordering.
>
> Thanks,
> Ben
>
> ---
>
> Ben Myers (2):
> commit_metadata export operation replacing nfsd_sync_dir
> xfs_export_operations.commit_metadata
>
>
> fs/nfsd/nfs4recover.c | 4 --
> fs/nfsd/vfs.c | 109 ++++++++++++++++++++---------------------
> fs/xfs/linux-2.6/xfs_export.c | 24 +++++++++
> include/linux/exportfs.h | 5 ++
> 4 files changed, 83 insertions(+), 59 deletions(-)
>
> --
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
prev parent reply other threads:[~2010-02-17 2:37 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-16 21:04 [PATCH 0/2] commit_metadata export operation v5 Ben Myers
2010-02-16 21:04 ` [PATCH 1/2] commit_metadata export operation replacing nfsd_sync_dir Ben Myers
2010-02-16 22:06 ` Christoph Hellwig
2010-02-16 21:04 ` [PATCH 2/2] xfs_export_operations.commit_metadata Ben Myers
2010-02-16 22:07 ` Christoph Hellwig
2010-02-17 0:29 ` Dave Chinner
2010-02-17 2:39 ` J. Bruce Fields [this message]
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=20100217023948.GB32315@fieldses.org \
--to=bfields@fieldses.org \
--cc=bpm@sgi.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox