From: Olga Kornievskaia <aglo@umich.edu>
To: Trond Myklebust <trondmy@hammerspace.com>
Cc: linux-nfs <linux-nfs@vger.kernel.org>
Subject: Re: NFS/TCP timeouts
Date: Wed, 3 Oct 2018 15:06:01 -0400 [thread overview]
Message-ID: <CAN-5tyFVb_jqt+jknn2+o6_Cu=7cKw4qt9B_e2pd0azu2-7zaQ@mail.gmail.com> (raw)
In-Reply-To: <e2541b5d08b823aaec01195178e87ba39526aa92.camel@hammerspace.com>
On Wed, Oct 3, 2018 at 2:45 PM Trond Myklebust <trondmy@hammerspace.com> wrote:
>
> On Wed, 2018-10-03 at 14:31 -0400, Olga Kornievskaia wrote:
> > Hi folks,
> >
> > Is it true that NFS mount option "timeo" has nothing to do with the
> > socket's setting of the user-specified timeout TCP_USER_TIMEOUT.
> > Instead, when creating a TCP socket NFS uses either default/hard
> > coded
> > value of 60s for v3 or for v4.x it's lease based. Is there no value
> > is
> > having an adjustable TCP timeout value?
> >
>
> It is adjusted. Please see the calculation in
> xs_tcp_set_socket_timeouts().
but it's not user configurable, is it? I don't see a way to modify
v3's default 60s TCP timeout. and also in v4, the timeouts are set
from xs_tcp_set_connect_timeout() for the lease period but again not
user configurable, as far as i can tell.
>
> --
> Trond Myklebust
> Linux NFS client maintainer, Hammerspace
> trond.myklebust@hammerspace.com
>
>
next prev parent reply other threads:[~2018-10-04 1:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-03 18:31 NFS/TCP timeouts Olga Kornievskaia
2018-10-03 18:45 ` Trond Myklebust
2018-10-03 19:06 ` Olga Kornievskaia [this message]
2019-12-11 20:36 ` Olga Kornievskaia
2019-12-12 16:47 ` Trond Myklebust
2019-12-12 18:13 ` Olga Kornievskaia
2019-12-12 19:31 ` Trond Myklebust
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='CAN-5tyFVb_jqt+jknn2+o6_Cu=7cKw4qt9B_e2pd0azu2-7zaQ@mail.gmail.com' \
--to=aglo@umich.edu \
--cc=linux-nfs@vger.kernel.org \
--cc=trondmy@hammerspace.com \
/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.