All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: Max Matveev <makc@redhat.com>
Cc: linux-nfs@vger.kernel.org, rees@umich.edu
Subject: Re: [PATCH v2] Update nfs(5) manpage - timeo for NFS/TCP
Date: Tue, 30 Aug 2011 08:41:26 -0400	[thread overview]
Message-ID: <4E5CDA76.7020703@RedHat.com> (raw)
In-Reply-To: <201108300245.p7U2jN4j011424-K5Dt2rfd30Yf7BdofF/totBPR1lH4CV8@public.gmane.org>



On 08/04/2011 01:47 AM, 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>
> Signed-off-by: Jim Rees <rees@umich.edu>
Committed... 

steved.

> ---
>  utils/mount/nfs.man |   16 ++++++++++------
>  1 files changed, 10 insertions(+), 6 deletions(-)
> 
> diff --git a/utils/mount/nfs.man b/utils/mount/nfs.man
> index be91a25..ff0ed60 100644
> --- a/utils/mount/nfs.man
> +++ b/utils/mount/nfs.man
> @@ -113,12 +113,16 @@ option may mitigate some of the risks of using the
>  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.
> +The time in deciseconds (tenths of a second) the NFS client waits for a
> +response before it retries an NFS request.
> +.IP
> +For NFS over TCP the default
> +.B timeo
> +value is 600 (60 seconds).
> +The NFS client performs linear backoff: After each retransmission the 
> +timeout is increased by
> +.BR timeo 
> +up to 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
> -- 1.7.4.4 -- 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

       reply	other threads:[~2011-08-30 12:41 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <201108300245.p7U2jN4j011424@ns3.rdu.redhat.com>
     [not found] ` <201108300245.p7U2jN4j011424-K5Dt2rfd30Yf7BdofF/totBPR1lH4CV8@public.gmane.org>
2011-08-30 12:41   ` Steve Dickson [this message]
2011-08-04  5:47 [PATCH v2] Update nfs(5) manpage - timeo for NFS/TCP Max Matveev
2011-08-05 12:40 ` Jim Rees
2011-08-05 13:34   ` Jim Rees
2011-08-05 20:33   ` Chuck Lever
2011-08-08  0:50     ` Max Matveev
2011-08-06  1:40   ` Max Matveev
2011-08-06 12:43     ` Jim Rees

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=4E5CDA76.7020703@RedHat.com \
    --to=steved@redhat.com \
    --cc=linux-nfs@vger.kernel.org \
    --cc=makc@redhat.com \
    --cc=rees@umich.edu \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.