NFSv4.1 Refactor nfs4_init_session and nfs4_init_channel_attrs
authorAndy Adamson <andros@netapp.com>
Wed, 26 Jun 2013 16:21:49 +0000 (12:21 -0400)
committerTrond Myklebust <Trond.Myklebust@netapp.com>
Fri, 28 Jun 2013 19:55:19 +0000 (15:55 -0400)
commit18aad3d552c73adf2652a34baf0fe766058018e4
treec4291710ff620be3ed2935cbd250d33137f84015
parent9111c95b077a81573fb27df3ba8255d0a3a9ebdf
NFSv4.1 Refactor nfs4_init_session and nfs4_init_channel_attrs

nfs4_init_session was originally written to be called prior to
nfs4_init_channel_attrs, setting the session target_max response and request
sizes that nfs4_init_channel_attrs would pay attention to.

In the current code flow, nfs4_init_session, just like nfs4_init_ds_session
for the data server case, is called after the session is all negotiated, and
is actually used in a RECLAIM COMPLETE call to the server.

Remove the un-needed fc_target_max response and request fields from
nfs4_session and just set the max_resp_sz and max_rqst_sz in
nfs4_init_channel_attrs.

Signed-off-by: Andy Adamson <andros@netapp.com>
Signed-off-by: Trond Myklebust <Trond.Myklebust@netapp.com>
fs/nfs/nfs4client.c
fs/nfs/nfs4proc.c
fs/nfs/nfs4session.c
fs/nfs/nfs4session.h