mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jamie Lokier <jamie@shareable.org>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux-kernel@vger.kernel.org
Subject: Re: NFS client problems in 2.4.18 to 2.4.20
Date: Sun, 7 Sep 2003 16:42:38 +0100	[thread overview]
Message-ID: <20030907154238.GK19977@mail.jlokier.co.uk> (raw)
In-Reply-To: <16219.19506.659542.990013@charged.uio.no>

Trond Myklebust wrote:
> This is not an issue for tapes, etc. NFS has an alternative mechanisms
> for dealing with this in the form of the NFSERR_JUKEBOX error.

Oh, cool.  Perhaps the server should send these automatically, when
I/O operations are taking a little bit too long?

> However for disks I agree that you do have 'large' variations between
> the cached and uncached case. Should latency really be much larger
> than 1/10 second for a 32k read though?

Yes, it often is.  I seek 32k reads taking several seconds, when the
disk is busy with other tasks.

>      > The fundamental error is assuming that all NFS requests take
>      > about the same time to server, and delays are caused by the
>      > network.  This isn't true especially on a LAN.  Delays for NFS
>      > are typically caused by I/O, and vary by 6 orders of magnitude
>      > from request to request.
> 
> If it was merely a case of random error, then we wouldn't have a
> problem at all. The RTT code does make an estimate of the error on the
> the measurement. The problem is that there is a large tail in the
> graph of round trip time vs. number of events due to these disk
> spinups, etc...

Yes, exactly.  Though I saw the tail due to normal disk seek + access
time is quite significant, compared with cached access time.

> However retransmissions compensate somewhat because they impose a
> geometric increase in the timeout value. i.e. The for the first
> transmission the timeout == the rto, then the retransmissions follow
> 2*rto, 4*rto, 8*rto,...
> 
> Part of the problem in the Linux case is therefore that we have a too
> low default value for 'retrans'. The kernel default is '5' (same as
> for Solaris, however the mount program still overrides that default
> with a value of '3'. This implies that for soft mounts, we never wait
> longer than 15*rto before we time out (well - 7*rto actually since the
> code in xdr_adjust_timeout() actually appears to confuse number of
> retransmissions with the number of transmissions).
> 
> By setting 'retrans=6' (5 + 1 to compensate for the bug), therefore,
> people can ensure that we retry for at least 6 seconds before timing
> out. The question is: is this an adequate default?

That would be a big improvement.  I take it you have effectively
clamped the retransmit time at a minimum of 1/10 second, then?  (I
didn't understand what you meant earlier).

Last time I used a soft mount, I was seeing the first retransmit after
some time smaller than a millisecond.  (I don't remember, but 0.1ms
sounds about right).  If that is the retransmit time, then retrans=6
won't be enough - retrans=16 would be needed.  I don't think a good
correct retrans=xxx setting should depend on the network like that.
Setting a minimum retransmit time is one way to fix that.

-- Jamie

  reply	other threads:[~2003-09-07 15:42 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-09-05 20:44 Joshua Weage
2003-09-05 21:51 ` Trond Myklebust
2003-09-06 16:29   ` Joshua Weage
2003-09-06 17:09     ` Trond Myklebust
2003-09-06 21:22       ` Joshua Weage
2003-09-06 23:14         ` Jamie Lokier
2003-09-07  1:54           ` Trond Myklebust
2003-09-07  2:02           ` Trond Myklebust
2003-09-07 14:27             ` Jamie Lokier
2003-09-07 15:18               ` Trond Myklebust
2003-09-07 15:42                 ` Jamie Lokier [this message]
2003-09-07 16:03                   ` Trond Myklebust
2003-09-10 18:37     ` Wouter Vlothuizen

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=20030907154238.GK19977@mail.jlokier.co.uk \
    --to=jamie@shareable.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=trond.myklebust@fys.uio.no \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®