public inbox for linux-nfs@vger.kernel.org
 help / color / mirror / Atom feed
From: NeilBrown <neilb@suse.de>
To: Trond Myklebust <trond.myklebust@primarydata.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] SUNRPC: Add missing support for RPC_CLNT_CREATE_NO_RETRANS_TIMEOUT
Date: Fri, 26 Sep 2014 11:10:05 +1000	[thread overview]
Message-ID: <20140926111005.3124f859@notabene.brown> (raw)
In-Reply-To: <1411613479-8803-1-git-send-email-trond.myklebust@primarydata.com>

[-- Attachment #1: Type: text/plain, Size: 2223 bytes --]

On Wed, 24 Sep 2014 22:51:19 -0400 Trond Myklebust
<trond.myklebust@primarydata.com> wrote:

> The flag RPC_CLNT_CREATE_NO_RETRANS_TIMEOUT was intended introduced in
> order to allow NFSv4 clients to disable resend timeouts. Since those
> cause the RPC layer to break the connection, they mess up the duplicate
> reply caches that remain indexed on the port number in NFSv4..
> 
> This patch includes the code that was missing in the original to
> set the appropriate flag in struct rpc_clnt, when the caller of
> rpc_create() sets RPC_CLNT_CREATE_NO_RETRANS_TIMEOUT.
> 
> Fixes: 8a19a0b6cb2e (SUNRPC: Add RPC task and client level options to...)
> Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
> ---
>  net/sunrpc/clnt.c | 2 ++
>  1 file changed, 2 insertions(+)
> 
> diff --git a/net/sunrpc/clnt.c b/net/sunrpc/clnt.c
> index 488ddeed9363..841565450354 100644
> --- a/net/sunrpc/clnt.c
> +++ b/net/sunrpc/clnt.c
> @@ -461,6 +461,8 @@ struct rpc_clnt *rpc_create_xprt(struct rpc_create_args *args,
>  
>  	if (args->flags & RPC_CLNT_CREATE_AUTOBIND)
>  		clnt->cl_autobind = 1;
> +	if (args->flags & RPC_CLNT_CREATE_NO_RETRANS_TIMEOUT)
> +		clnt->cl_noretranstimeo = 1;
>  	if (args->flags & RPC_CLNT_CREATE_DISCRTRY)
>  		clnt->cl_discrtry = 1;
>  	if (!(args->flags & RPC_CLNT_CREATE_QUIET))

Hi Trond,
 do this relate to my observation in 
    Subject: Re: NFS auto-reconnect tuning

 that NFSv4 closes a connections after the first timeout?
 This patch seems to be a step towards changing that behaviour, though it
 doesn't succeed.

You would need

@@ -580,6 +582,7 @@ static struct rpc_clnt *__rpc_clone_client(struct rpc_create_args *args,
 	new->cl_autobind = 0;
 	new->cl_softrtry = clnt->cl_softrtry;
 	new->cl_discrtry = clnt->cl_discrtry;
+	new->cl_noretranstimeo = clnt->cl_noretranstimeo;
 	new->cl_chatty = clnt->cl_chatty;
 	return new;

as well.

What do you think of having the client close the connection more quickly when
there is a timeout?  There does seem to be a case for closing sooner than 30
minutes...

I must admit I'm a bit confused by these flags so I might be missing
something important.

Thanks,
NeilBrown


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 828 bytes --]

  reply	other threads:[~2014-09-26  1:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-09-25  2:51 [PATCH] SUNRPC: Add missing support for RPC_CLNT_CREATE_NO_RETRANS_TIMEOUT Trond Myklebust
2014-09-26  1:10 ` NeilBrown [this message]
2014-09-26  1:23   ` Trond Myklebust
2014-09-26  2:25     ` NeilBrown

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=20140926111005.3124f859@notabene.brown \
    --to=neilb@suse.de \
    --cc=linux-nfs@vger.kernel.org \
    --cc=trond.myklebust@primarydata.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