From: Steve Dickson <SteveD@redhat.com>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: [PATCH] Timeouts gone wild on ia64
Date: Fri, 09 May 2003 13:19:45 -0400 [thread overview]
Message-ID: <3EBBE331.5000207@RedHat.com> (raw)
In-Reply-To: 482A3FA0050D21419C269D13989C6113127DB4@lavender-fe.eng.netapp.com
Lever, Charles wrote:
>however, equivalent behavior would be:
>
> #define RPC_RTO_MIN (HZ/50)
>
>not HZ/30. why did you choose 30?
>
I realize this but... I figured waiting a
a few extra ticks of time before timing
out was probably a good thing with respect
to soft mounts on slow servers... Especially
since EIO errors can be pretty disruptive... ;-)\
SteveD.
-------------------------------------------------------
Enterprise Linux Forum Conference & Expo, June 4-6, 2003, Santa Clara
The only event dedicated to issues related to Linux enterprise solutions
www.enterpriselinuxforum.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-05-09 17:19 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 15:24 [PATCH] Timeouts gone wild on ia64 Lever, Charles
2003-05-09 17:19 ` Steve Dickson [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-05-15 15:34 Lever, Charles
2003-05-15 14:26 Lever, Charles
2003-05-15 14:41 ` Trond Myklebust
2003-05-15 15:16 ` Steve Dickson
2003-05-15 5:46 Lever, Charles
2003-05-15 14:10 ` Steve Dickson
2003-05-15 14:31 ` Trond Myklebust
2003-05-15 15:33 ` Steve Dickson
2003-09-17 4:14 ` Yusuf Goolamabbas
2003-09-17 13:46 ` Trond Myklebust
2003-09-18 7:03 ` Yusuf Goolamabbas
2003-09-18 12:13 ` Trond Myklebust
2003-05-09 13:40 Lever, Charles
2003-05-09 14:12 ` Steve Dickson
2003-05-09 12:41 Steve Dickson
2003-05-10 13:50 ` Trond Myklebust
2003-05-15 0:34 ` Steve Dickson
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=3EBBE331.5000207@RedHat.com \
--to=steved@redhat.com \
--cc=Charles.Lever@netapp.com \
--cc=nfs@lists.sourceforge.net \
/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.