diff mbox

Update nfs(5) manpage - timeo for NFS/TCP

Message ID 20110804062858.EAD96813270B@regina.usersys.redhat.com (mailing list archive)
State New, archived
Headers show

Commit Message

Max Matveev Aug. 4, 2011, 5:47 a.m. UTC 
NFS/TCP does linear backoff then retransmiting - the manpage
was mistakenly asserting the "no backoff" theory.

Signed-off-by: Max Matveev <makc@redhat.com>
---
 utils/mount/nfs.man |   14 +++++++++-----
 1 files changed, 9 insertions(+), 5 deletions(-)

Comments

Jim Rees Aug. 4, 2011, 12:04 p.m. UTC | #1 
Max Matveev wrote:

  NFS/TCP does linear backoff then retransmiting - the manpage
  was mistakenly asserting the "no backoff" theory.
  
  Signed-off-by: Max Matveev <makc@redhat.com>
  ---
   utils/mount/nfs.man |   14 +++++++++-----
   1 files changed, 9 insertions(+), 5 deletions(-)
  
  diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
  index be91a25..7681b10 100644
  --- a/utils/mount/nfs.man
  +++ b/utils/mount/nfs.man
  @@ -114,11 +114,15 @@ option.
   .TP 1.5i
   .BI timeo= n
   The time (in tenths of a second) the NFS client waits for a
  -response before it retries an NFS request. If this
  -option is not specified, requests are retried every
  -60 seconds for NFS over TCP.
  -The NFS client does not perform any kind of timeout backoff
  -for NFS over TCP.
  +response before it retries an NFS request.
  +.IP
  +For NFS over TCP the default
  +.B timeo
  +value is 600 which equals to 60 seconds.
  +The NFS client performs linear backoff  -
  +after each retransmission the timeout is increased by
  +.BR timeo /10
  +seconds upto the maximum of 600 seconds.

"upto" should be "up to".

I'm not crazy about the wording.  How about

  For NFS over TCP the default timeo is 600 (60 seconds).  The NFS client
  performs linear backoff.  After each retransmission the timeout is
  increased by timeo up to the maximum of 600 seconds.

Finally, I would call them "deciseconds".

timeo: The time in deciseconds (tenths of a second) ...
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Max Matveev Aug. 5, 2011, 12:57 a.m. UTC | #2 
On Thu, 4 Aug 2011 08:04:01 -0400, Jim Rees wrote:

 rees> I'm not crazy about the wording.  How about

 rees>   For NFS over TCP the default timeo is 600 (60 seconds).  The NFS client
 rees>   performs linear backoff.  After each retransmission the timeout is
 rees>   increased by timeo up to the maximum of 600 seconds.

I'm fine with this except the third sentence is the explanation of
"linear backoff" - I'd rather keep them together, i.e.:

	The NFS client performs linear backoff: after each
	retransmission the timeout is increased by timeo up to the
	maximum of 600 seconds.

 rees> Finally, I would call them "deciseconds".

Secquipedalians'r'us.

 rees> timeo: The time in deciseconds (tenths of a second) ...
Will do.

Anything else before I send v2?

max
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Jim Rees Aug. 5, 2011, 1:39 a.m. UTC | #3 
Max Matveev wrote:

  	The NFS client performs linear backoff: after each
  	retransmission the timeout is increased by timeo up to the
  	maximum of 600 seconds.

Good point about keeping this together.  Probably should be a semicolon, but
if you go with a colon, capitalize "after".
--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Max Matveev Aug. 5, 2011, 2:14 a.m. UTC | #4 
On Thu, 4 Aug 2011 21:39:36 -0400, Jim Rees wrote:

 rees> Max Matveev wrote:
 rees>   	The NFS client performs linear backoff: after each
 rees>   	retransmission the timeout is increased by timeo up to the
 rees>   	maximum of 600 seconds.

 rees> Good point about keeping this together.  Probably should be a
 rees> semicolon, but if you go with a colon, capitalize "after".

Will keep the colon and capitalize.

max

--
To unsubscribe from this list: send the line "unsubscribe linux-nfs" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
diff mbox

Patch

diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
index be91a25..7681b10 100644
--- a/utils/mount/nfs.man
+++ b/utils/mount/nfs.man
@@ -114,11 +114,15 @@  option.
 .TP 1.5i
 .BI timeo= n
 The time (in tenths of a second) the NFS client waits for a
-response before it retries an NFS request. If this
-option is not specified, requests are retried every
-60 seconds for NFS over TCP.
-The NFS client does not perform any kind of timeout backoff
-for NFS over TCP.
+response before it retries an NFS request.
+.IP
+For NFS over TCP the default
+.B timeo
+value is 600 which equals to 60 seconds.
+The NFS client performs linear backoff  -
+after each retransmission the timeout is increased by
+.BR timeo /10
+seconds upto the maximum of 600 seconds.
 .IP
 However, for NFS over UDP, the client uses an adaptive
 algorithm to estimate an appropriate timeout value for frequently used