Home
last modified time | relevance | path

Searched hist:a956beda19a6b39fbc19d0aaf21947acdc18cf74 (Results 1 – 3 of 3) sorted by relevance

/linux/fs/nfs/
H A Dclient.cdiff a956beda19a6b39fbc19d0aaf21947acdc18cf74 Tue Aug 16 16:26:47 CEST 2016 Trond Myklebust <trond.myklebust@primarydata.com> NFS: Allow the mount option retrans=0

We should allow retrans=0 as just meaning that every timeout is a major
timeout, and that there is no increment in the timeout value.

For instance, this means that we would allow TCP users to specify a
flat timeout value of 60s, by specifying "timeo=600,retrans=0" in their
mount option string.

Siged-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
H A Dinternal.hdiff a956beda19a6b39fbc19d0aaf21947acdc18cf74 Tue Aug 16 16:26:47 CEST 2016 Trond Myklebust <trond.myklebust@primarydata.com> NFS: Allow the mount option retrans=0

We should allow retrans=0 as just meaning that every timeout is a major
timeout, and that there is no increment in the timeout value.

For instance, this means that we would allow TCP users to specify a
flat timeout value of 60s, by specifying "timeo=600,retrans=0" in their
mount option string.

Siged-off-by: Trond Myklebust <trond.myklebust@primarydata.com>
H A Dsuper.cdiff a956beda19a6b39fbc19d0aaf21947acdc18cf74 Tue Aug 16 16:26:47 CEST 2016 Trond Myklebust <trond.myklebust@primarydata.com> NFS: Allow the mount option retrans=0

We should allow retrans=0 as just meaning that every timeout is a major
timeout, and that there is no increment in the timeout value.

For instance, this means that we would allow TCP users to specify a
flat timeout value of 60s, by specifying "timeo=600,retrans=0" in their
mount option string.

Siged-off-by: Trond Myklebust <trond.myklebust@primarydata.com>