From: Yusuf Goolamabbas <yusufg@outblaze.com>
To: nfs@lists.sourceforge.net
Subject: Re: [PATCH] Timeouts gone wild on ia64
Date: Thu, 18 Sep 2003 15:03:52 +0800 [thread overview]
Message-ID: <20030918070352.GA23924@outblaze.com> (raw)
In-Reply-To: <16232.26027.789453.979782@charged.uio.no>
> > Trond, In your opinion. What should be the default retrans
> > value given your recent work in having adaptive timeouts in the
> > NFS client ?
>
> I'd like to cap the minimum value for the estimated error on the RTO
> at 1/10sec as per the 2.6 kernel (currently it is set at 2/HZ sec ~
> 2/100sec on most architectures, but 2/1000sec on ia64).
>
> Then I'd like to increase the default value that "mount" uses for
> "retrans" to the kernel value (which is currently set at 5).
What value are you looking at ?
Also man 5 nfs seems (in RH 9) that default retrans value is 3
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2003-09-18 7:04 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-15 5:46 [PATCH] Timeouts gone wild on ia64 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 [this message]
2003-09-18 12:13 ` Trond Myklebust
-- 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-09 15:24 Lever, Charles
2003-05-09 17:19 ` Steve Dickson
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=20030918070352.GA23924@outblaze.com \
--to=yusufg@outblaze.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox