From: Dan Kegel <dank@kegel.com>
To: Chuck Lever <cel@citi.umich.edu>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: re: [PATCH] new timeout behavior for RPC requests on TCP sockets
Date: Tue, 12 Nov 2002 15:48:02 -0800 [thread overview]
Message-ID: <3DD19332.1050703@kegel.com> (raw)
Chuck wrote:
> make RPC timeout behavior over TCP sockets behave more like reference
> client implementations. reference behavior is to transmit the same
> request three times at 60 second intervals; if there is no response, close
> and reestablish the socket connection. we modify the Linux RPC client as
> follows:
>
> + after a minor retransmit timeout, use the same timeout value when
> retrying on a TCP socket rather than doubling the value
> + after a major retransmit timeout, close the socket and attempt
> to reestablish a fresh TCP connection
>
> note that today mount uses a 6 second timeout with 5 retries for NFS over
> TCP by default; proper default behavior is 2 retries each with 60 second
> timeouts. a separate patch for mount is pending.
Chuck, can you briefly explain why RPC does any minor
retransmits at all over TCP?
Shouldn't TCP's natural retransmit take care of that?
- Dan
next reply other threads:[~2002-11-12 23:20 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-12 23:48 Dan Kegel [this message]
2002-11-13 15:58 ` [PATCH] new timeout behavior for RPC requests on TCP sockets Chuck Lever
2002-11-13 16:44 ` Richard B. Johnson
2002-11-13 16:49 ` Trond Myklebust
2002-11-13 18:38 ` Richard B. Johnson
2002-11-14 15:41 ` Trond Myklebust
2002-11-14 18:36 ` Richard B. Johnson
2002-11-14 19:33 ` Trond Myklebust
2002-11-14 20:26 ` Chuck Lever
2002-11-14 20:37 ` Richard B. Johnson
2002-11-14 21:05 ` Chuck Lever
2002-11-13 17:42 ` Alan Cox
2002-11-13 18:33 ` Richard B. Johnson
-- strict thread matches above, loose matches on Subject: below --
2002-11-26 19:57 Chuck Lever
2002-11-12 23:15 Chuck Lever
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=3DD19332.1050703@kegel.com \
--to=dank@kegel.com \
--cc=cel@citi.umich.edu \
--cc=linux-kernel@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