linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Trond Myklebust <Trond.Myklebust@netapp.com>
To: Chuck Lever <chuck.lever@oracle.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH 3/8] NFS: Introduce nfs4_proc_get_mig_status()
Date: Thu, 10 Mar 2011 14:58:59 -0500	[thread overview]
Message-ID: <1299787139.3075.36.camel@heimdal.trondhjem.org> (raw)
In-Reply-To: <20110310172959.8878.88948.stgit@matisse.1015granger.net>

On Thu, 2011-03-10 at 12:29 -0500, Chuck Lever wrote: 
> @@ -5915,6 +5962,37 @@ out:
>  	return status;
>  }
>  
> +/*
> + * Decode migration status probe
> + */
> +static int nfs4_xdr_dec_get_mig_status(struct rpc_rqst *req,
> +				       struct xdr_stream *xdr,
> +				       struct nfs4_fs_locations_res *res)
> +{
> +	struct compound_hdr hdr;
> +	int status;
> +
> +	status = decode_compound_hdr(xdr, &hdr);
> +	if (status)
> +		goto out;
> +	status = decode_sequence(xdr, &res->seq_res, req);
> +	if (status)
> +		goto out;
> +	status = decode_putfh(xdr);
> +	if (status)
> +		goto out;
> +	xdr_enter_page(xdr, PAGE_SIZE);
> +	status = decode_getfattr(xdr, &res->fs_locations->fattr,
> +				 res->fs_locations->server,
> +				 !RPC_IS_ASYNC(req->rq_task));
> +	if (status)
> +		goto out;
> +	if (res->renew)
> +		status = decode_renew(xdr);
> +out:
> +	return status;
> +}
> +
>  #if defined(CONFIG_NFS_V4_1)
>  /*
>   * Decode EXCHANGE_ID response
> @@ -6255,6 +6333,7 @@ struct rpc_procinfo	nfs4_procedures[] = {
>  	PROC(GETACL,		enc_getacl,		dec_getacl),
>  	PROC(SETACL,		enc_setacl,		dec_setacl),
>  	PROC(FS_LOCATIONS,	enc_fs_locations,	dec_fs_locations),
> +	PROC(GET_MIG_STATUS,	enc_get_mig_status,	dec_get_mig_status)

Yet more trouble for nfsstat...

> ,
>  	PROC(RELEASE_LOCKOWNER,	enc_release_lockowner,	dec_release_lockowner),
>  #if defined(CONFIG_NFS_V4_1)
>  	PROC(EXCHANGE_ID,	enc_exchange_id,	dec_exchange_id),

So looking at what you are doing in GET_MIG_STATUS, it appears to me
that

1) We don't need it for NFSv4.1: the existing fs_locations request just
works for that.
2) The only new thing in NFSv4.0 is the renew operation...

So how about if we just modify the existing fs_locations call to append
a RENEW request if/when we supply a clientid?

Cheers
  Trond
-- 
Trond Myklebust
Linux NFS client maintainer

NetApp
Trond.Myklebust@netapp.com
www.netapp.com


  reply	other threads:[~2011-03-10 19:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-10 17:29 [PATCH 0/8] Snapshot of client-side NFSv4 migration support Chuck Lever
2011-03-10 17:29 ` [PATCH 1/8] NFS: Add a lame client-side function to display file handles Chuck Lever
2011-03-10 17:29 ` [PATCH 2/8] NFS: Save root file handle in nfs_server Chuck Lever
2011-03-10 17:29 ` [PATCH 3/8] NFS: Introduce nfs4_proc_get_mig_status() Chuck Lever
2011-03-10 19:58   ` Trond Myklebust [this message]
2011-03-10 20:14     ` Chuck Lever
2011-03-10 20:21       ` Chuck Lever
2011-03-10 17:30 ` [PATCH 4/8] NFS: Add functions to swap transports during migration recovery Chuck Lever
2011-03-10 17:30 ` [PATCH 5/8] NFS: Add basic migration support to state manager thread Chuck Lever
2011-03-10 20:35   ` Trond Myklebust
2011-03-10 20:40     ` Chuck Lever
2011-03-11 20:53     ` Chuck Lever
2011-03-10 17:30 ` [PATCH 6/8] NFS: Remove "const" from "struct nfs_server *" fields Chuck Lever
2011-03-10 17:30 ` [PATCH 7/8] NFS: Add migration recovery callouts in nfs4proc.c Chuck Lever
2011-03-10 17:30 ` [PATCH 8/8] 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=1299787139.3075.36.camel@heimdal.trondhjem.org \
    --to=trond.myklebust@netapp.com \
    --cc=chuck.lever@oracle.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;
as well as URLs for NNTP newsgroup(s).