From: Ben Myers <bpm@sgi.com>
To: linux-nfs@vger.kernel.org
Subject: [RFC PATCH 0/2] nfsd sync export_op (was 'wsync export option')
Date: Tue, 09 Feb 2010 18:33:26 -0600 [thread overview]
Message-ID: <20100210003220.6021.74943.stgit@case> (raw)
This is another try based upon Christoph and Trond's suggestions in the 'wsync
export option' thread. I've added the export operation and combined
nfsd_sync_dir and write_inode_now usage into nfsd_sync2 which passes the buck
onto XFS. It's been very lightly tested. It's just a little bit faster than
the previous try:
# time tar -xvf /mnt2/quilt-0.47.tar > /dev/null
plain jane:
0m13.177s 0m13.301s 0m13.528s
previous try:
0m8.361s 0m8.400s 0m8.301s
w/ xfs commit_metadata op:
0m7.426s 0m7.340s 0m7.198s
Thanks!
-Ben
---
Ben Myers (2):
commit_metadata export operation and nfsd_sync2
xfs_export_operations.commit_metadata
fs/nfsd/nfs3proc.c | 2 -
fs/nfsd/nfs4proc.c | 2 -
fs/nfsd/nfs4recover.c | 2 -
fs/nfsd/nfs4state.c | 2 -
fs/nfsd/nfsproc.c | 4 +
fs/nfsd/vfs.c | 113 ++++++++++++++++++++++++++---------------
fs/nfsd/vfs.h | 4 +
fs/xfs/linux-2.6/xfs_export.c | 64 +++++++++++++++++++++++
include/linux/exportfs.h | 6 ++
9 files changed, 151 insertions(+), 48 deletions(-)
--
next reply other threads:[~2010-02-10 0:33 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-10 0:33 Ben Myers [this message]
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 10:11 ` Christoph Hellwig
2010-02-10 20:15 ` bpm
2010-02-10 21:29 ` Dave Chinner
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=20100210003220.6021.74943.stgit@case \
--to=bpm@sgi.com \
--cc=linux-nfs@vger.kernel.org \
/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