From: Max Matveev <makc@redhat.com>
To: Trond Myklebust <Trond.Myklebust@netapp.com>
Cc: linux-nfs@vger.kernel.org
Subject: Re: NFS/TCP timeout sequence
Date: Fri, 8 Jul 2011 10:20:12 +1000 [thread overview]
Message-ID: <19990.19772.54549.203398@regina.usersys.redhat.com> (raw)
In-Reply-To: <1310046439.3863.30.camel@lade.trondhjem.org>
On Thu, 07 Jul 2011 09:47:19 -0400, Trond Myklebust wrote:
TM> On Thu, 2011-07-07 at 18:11 +1000, Max Matveev wrote:
TM> Sigh... Firstly, 2 second timeouts are complete lunacy when using a
TM> protocol that guarantees reliable delivery, such as TCP does. Anyone who
TM> tries it deserves exactly what they get: poor unreliable performance.
2 seconds is besides the point - I'm not going to wait for 28 minutes
(timeout=600,retrans=7) when doing timeout testing just to prove that
it does not work.
TM> Secondly, the _other_ fix for this problem is to fix the documentation.
I can live with that too.
max
prev parent reply other threads:[~2011-07-08 0:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 8:11 NFS/TCP timeout sequence Max Matveev
2011-07-07 13:47 ` Trond Myklebust
2011-07-07 14:04 ` Chuck Lever
2011-07-07 14:16 ` Trond Myklebust
2011-07-07 14:44 ` Chuck Lever
2011-07-07 14:59 ` Trond Myklebust
2011-08-04 5:54 ` Max Matveev
2011-08-04 5:42 ` [PATCH] NFS: allow enough time for timeouts to run Max Matveev
2011-08-04 5:47 ` [PATCH] Update nfs(5) manpage - timeo for NFS/TCP Max Matveev
2011-08-04 12:04 ` Jim Rees
2011-08-05 0:57 ` Max Matveev
2011-08-05 1:39 ` Jim Rees
2011-08-05 2:14 ` Max Matveev
2011-07-08 6:05 ` NFS/TCP timeout sequence Max Matveev
2011-07-08 0:20 ` Max Matveev [this message]
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=19990.19772.54549.203398@regina.usersys.redhat.com \
--to=makc@redhat.com \
--cc=Trond.Myklebust@netapp.com \
--cc=linux-nfs@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).