From: Chuck Lever <chuck.lever@oracle.com>
To: trond.myklebust@netapp.com
Cc: linux-nfs@vger.kernel.org
Subject: [PATCH 00/12] Snapshot of client-side NFSv4 migration support (v2)
Date: Mon, 14 Mar 2011 08:56:22 -0400 [thread overview]
Message-ID: <20110314125204.2413.8870.stgit@matisse.1015granger.net> (raw)
This is a second snapshot of migration support for the Linux NFS
client. This snapshot is untested. I think I've addressed recent
review comments.
The one remaining piece seems to be adding logic to send a SETCLIENTID
to the destination server to update the client's callback endpoint
information. I think we'll need to move cl_ipaddr and other fields
related to constructing the long-form client ID into the nfs_server
struct. More discussion is needed.
---
Chuck Lever (12):
NFS: Implement support for NFS4ERR_LEASE_MOVED
NFS: Add migration recovery callouts in nfs4proc.c
NFS: Remove "const" from "struct nfs_server *" fields
NFS: Add basic migration support to state manager thread
NFS: Add functions to swap transports during migration recovery
NFS: Introduce nfs4_proc_get_mig_status()
NFS: Introduce NFS_ATTR_FATTR_V4_LOCATIONS
NFS: Save root file handle in nfs_server
NFS: Add a client-side function to display file handles
NFS: Add NFS4CLNT_UPDATE_CLIENTID
SUNRPC: Add API to acquire source address
SUNRPC: Remove obsolete comment
fs/nfs/client.c | 2 +
fs/nfs/getroot.c | 5 +
fs/nfs/inode.c | 45 ++++++++++++
fs/nfs/internal.h | 2 +
fs/nfs/nfs4_fs.h | 7 ++
fs/nfs/nfs4namespace.c | 162 +++++++++++++++++++++++++++++++++++++++++++
fs/nfs/nfs4proc.c | 143 +++++++++++++++++++++++++++++++++-----
fs/nfs/nfs4state.c | 150 ++++++++++++++++++++++++++++++++++++++--
fs/nfs/nfs4xdr.c | 50 ++++++++++---
include/linux/nfs_fs.h | 14 ++++
include/linux/nfs_fs_sb.h | 6 ++
include/linux/nfs_xdr.h | 38 ++++++----
include/linux/sunrpc/clnt.h | 1
net/sunrpc/clnt.c | 136 +++++++++++++++++++++++++++++++++++-
14 files changed, 700 insertions(+), 61 deletions(-)
--
Chuck Lever
next reply other threads:[~2011-03-14 12:56 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-14 12:56 Chuck Lever [this message]
2011-03-14 12:56 ` [PATCH 01/12] SUNRPC: Remove obsolete comment Chuck Lever
2011-03-14 12:56 ` [PATCH 02/12] SUNRPC: Add API to acquire source address Chuck Lever
2011-03-14 12:56 ` [PATCH 03/12] NFS: Add NFS4CLNT_UPDATE_CLIENTID Chuck Lever
2011-03-14 12:57 ` [PATCH 04/12] NFS: Add a client-side function to display file handles Chuck Lever
2011-03-14 12:57 ` [PATCH 05/12] NFS: Save root file handle in nfs_server Chuck Lever
2011-03-14 12:57 ` [PATCH 06/12] NFS: Introduce NFS_ATTR_FATTR_V4_LOCATIONS Chuck Lever
2011-03-14 12:57 ` [PATCH 07/12] NFS: Introduce nfs4_proc_get_mig_status() Chuck Lever
2011-03-14 12:57 ` [PATCH 08/12] NFS: Add functions to swap transports during migration recovery Chuck Lever
2011-03-14 12:57 ` [PATCH 09/12] NFS: Add basic migration support to state manager thread Chuck Lever
2011-03-14 12:57 ` [PATCH 10/12] NFS: Remove "const" from "struct nfs_server *" fields Chuck Lever
2011-03-14 12:58 ` [PATCH 11/12] NFS: Add migration recovery callouts in nfs4proc.c Chuck Lever
2011-03-14 12:58 ` [PATCH 12/12] NFS: Implement support for NFS4ERR_LEASE_MOVED Chuck Lever
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=20110314125204.2413.8870.stgit@matisse.1015granger.net \
--to=chuck.lever@oracle.com \
--cc=linux-nfs@vger.kernel.org \
--cc=trond.myklebust@netapp.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;
as well as URLs for NNTP newsgroup(s).