| commit | 15d03055cf39fe61714aeda8d0a722b3137531ed | |
| author | Trond Myklebust <trond.myklebust@primarydata.com> | |
| Tue, 16 Aug 2016 15:08:22 +0000 (16 11:08 -0400) | ||
| committer | Trond Myklebust <trond.myklebust@primarydata.com> | |
| Tue, 16 Aug 2016 15:16:19 +0000 (16 11:16 -0400) | ||
| tree | 5387b291f27f3eac59f68d6780e5bae4e485ce3f | treesnapshot (tar.gz zip) |
| parent | a956beda19a6b39fbc19d0aaf21947acdc18cf74 | commitdiff |
pNFS/flexfiles: Set reasonable default retrans values for the data channel
Prior to this patch, the retrans value was set at 5, meaning that we
could see a maximum retransmission timeout value of more than 6 minutes.
That's a tad high for NFSv3 where the protocol does allow the server to
drop requests at any time.
Since this is a data channel, let's just set retrans to 0, and the default
timeout to 60s. The user can continue to adjust these defaults using the
dataserver_retrans and dataserver_timeo module parameters.
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
Prior to this patch, the retrans value was set at 5, meaning that we
could see a maximum retransmission timeout value of more than 6 minutes.
That's a tad high for NFSv3 where the protocol does allow the server to
drop requests at any time.
Since this is a data channel, let's just set retrans to 0, and the default
timeout to 60s. The user can continue to adjust these defaults using the
dataserver_retrans and dataserver_timeo module parameters.
Signed-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
| fs/nfs/flexfilelayout/flexfilelayoutdev.c | diffblobblamehistory |