linux-nfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Trond Myklebust <trond.myklebust@primarydata.com>,
	Anna Schumaker <schumakeranna@gmail.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: [PATCH] nfs: RPC_MAX_AUTH_SIZE is in bytes
Date: Wed, 20 Sep 2017 12:49:51 -0400	[thread overview]
Message-ID: <20170920164951.GG14329@fieldses.org> (raw)
In-Reply-To: <20170920164213.GF14329@fieldses.org>

On Wed, Sep 20, 2017 at 12:42:13PM -0400, bfields wrote:
> From: "J. Bruce Fields" <bfields@redhat.com>
> 
> The units of RPC_MAX_AUTH_SIZE is bytes, not 4-byte words.  This causes
> the client to request a larger-than-necessary session replay slot size.

By the way, the client's still asking for 3428 bytes after that, which
seems high.  It's mostly the fault of NFS4_MAXLABELLEN, which is 2048.
I haven't spotted an improvement there yet.

Noticed because knfsd was hitting session drc cache limits much to early
and failing CREATE_SESSION (hence mount).  The main trouble is on the
server side, so I'm relaxing the limits there (and revisiting Trond's
dynamic slot renegotiation patches).  But I thought I should check for
any easy improvements here too.

--b.

> 
> Signed-off-by: J. Bruce Fields <bfields@redhat.com>
> ---
>  fs/nfs/nfs4xdr.c | 4 ++--
>  1 file changed, 2 insertions(+), 2 deletions(-)
> 
> diff --git a/fs/nfs/nfs4xdr.c b/fs/nfs/nfs4xdr.c
> index 37c8af003275..14ed9791ec9c 100644
> --- a/fs/nfs/nfs4xdr.c
> +++ b/fs/nfs/nfs4xdr.c
> @@ -1842,8 +1842,8 @@ static void encode_create_session(struct xdr_stream *xdr,
>  	 * Assumes OPEN is the biggest non-idempotent compound.
>  	 * 2 is the verifier.
>  	 */
> -	max_resp_sz_cached = (NFS4_dec_open_sz + RPC_REPHDRSIZE +
> -			      RPC_MAX_AUTH_SIZE + 2) * XDR_UNIT;
> +	max_resp_sz_cached = (NFS4_dec_open_sz + RPC_REPHDRSIZE + 2)
> +				* XDR_UNIT + RPC_MAX_AUTH_SIZE;
>  
>  	encode_op_hdr(xdr, OP_CREATE_SESSION, decode_create_session_maxsz, hdr);
>  	p = reserve_space(xdr, 16 + 2*28 + 20 + clnt->cl_nodelen + 12);
> -- 
> 2.13.5
> 

  reply	other threads:[~2017-09-20 16:49 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-09-20 16:42 [PATCH] nfs: RPC_MAX_AUTH_SIZE is in bytes J. Bruce Fields
2017-09-20 16:49 ` J. Bruce Fields [this message]
2017-09-20 16:56   ` Chuck Lever
2017-09-20 18:15     ` J. Bruce Fields

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=20170920164951.GG14329@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=linux-nfs@vger.kernel.org \
    --cc=schumakeranna@gmail.com \
    --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;
as well as URLs for NNTP newsgroup(s).