All of lore.kernel.org
 help / color / mirror / Atom feed
From: Steve Dickson <SteveD@redhat.com>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, nfs@lists.sourceforge.net
Subject: Re: [PATCH] Timeouts gone wild on ia64
Date: Thu, 15 May 2003 10:10:39 -0400	[thread overview]
Message-ID: <3EC39FDF.60609@RedHat.com> (raw)
In-Reply-To: <482A3FA0050D21419C269D13989C6113127DC8@lavender-fe.eng.netapp.com>


It appears the RTO code does seem to be working but when the
minimums start so low (like at 4m instead 40ms) it takes some
time for the timeout value to build up and with soft mounts
there is no time...

Maybe I'm missing something... increasing the timeout value should
not have any affect on performance since in a well tuned
client and server these timeout will never occur since the
responses from the server will be returned before the
timeout expires... right? Also decreasing the number of timeouts
will decrease the number of retransmits which is another good
thing... True?

SteveD.

Lever, Charles wrote:

>steve-
> 
>i think there must be an underlying problem here.  soft mounts
>to slow servers should work correctly without raising the RTO
>minimum.  
> 
>the RTO estimator should automatically raise the RTO values to
>avoid extra timeouts.  if not, there is a problem with the RTO
>estimator that needs to be addressed.
> 
>
>-----Original Message----- 
>From: Steve Dickson [mailto:SteveD@RedHat.com] 
>Sent: Wed 5/14/2003 8:34 PM 
>To: Trond Myklebust; nfs@lists.sourceforge.net 
>Cc: 
>Subject: Re: [NFS] [PATCH] Timeouts gone wild on ia64
>
>
>
>Hi Trond, 
>
>Trond Myklebust wrote: 
>
>  
>
>>>>>>>" " == Steve Dickson <SteveD@RedHat.com> writes: 
>>>>>>>           
>>>>>>>
>>>>>>>              
>>>>>>>
>>    > What this patch does is make the minimal Round Trip time value 
>>    > relative to HZ. So When HZ is greater (as in the case of ia64) 
>>    > the minimal value goes up. 
>>    >  Comments? 
>>
>>1/30 of a second is a long time. Why that particular choice? 
>>
>>Note: "It works" won't cut ice as that is completely a function of the 
>>choice of hardware. 
>>
>>    
>>
>I realize this but... I figured waiting a few extra ticks of time before 
>timing 
>out was probably a good thing with respect to soft mounts to slow 
>servers... 
>Especially  since EIO errors can be pretty disruptive... 
>
>And as I see, its a no-op with a fast (or slow) client  talking to a fast 
>server because the timeout will should never happen... (i.e. the waiting 
>thread will get the response before the time out occurs).... 
>
>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 
>
>  
>



-------------------------------------------------------
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

  reply	other threads:[~2003-05-15 14:11 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 [this message]
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
  -- 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=3EC39FDF.60609@RedHat.com \
    --to=steved@redhat.com \
    --cc=Charles.Lever@netapp.com \
    --cc=nfs@lists.sourceforge.net \
    --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 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.