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 10:12:27 -0400 [thread overview]
Message-ID: <3EBBB74B.4000008@RedHat.com> (raw)
In-Reply-To: 482A3FA0050D21419C269D13989C6113127DB3@lavender-fe.eng.netapp.com
It has to do with the value of HZ.... On a ia64, HZ is
at 1024 and on an x86 machine its 100. Not taking this
difference in account when figure the the minimal
timeout values was causing timeouts to occur every 4ms
instead of 40ms.
The network trace didn't show anything substantial,
but here is the debugging trail.
By logging (and counting) the number of times call_status() was called
with a -ETIMEDOUT status, it became very apparent that ia64 machine
were timing out thousands of times more often than an x86 machine.
The actual numbers was something like 1400 to 50 when I generated
traffic by doing md5sum /nfs/mounted/*.rpm > /dev/null.
Next I took a look at what task->tk_timeout was being set to in
do_xprt_transmit(). On an x86 it was being set to ~40ms. On
an ia64 machine it was being set to ~4ms.
That lead me to how rpc_calc_rto() was figuring out
the RTOs... I noticed that RPC_RTO_MIN was the only
constant that was not relative to HZ. So I did some
experiments and found out by making it relative to HZ
the timeout decreased substantially...
SteveD.
Lever, Charles wrote:
>steve-
>
>can you explain why there are more timeouts for ia64? do you
>have a network trace you can share?
>
>-----Original Message-----
>From: Steve Dickson [mailto:SteveD@RedHat.com]
>Sent: Fri 5/9/2003 8:41 AM
>To: nfs@lists.sourceforge.net
>Cc:
>Subject: [NFS] [PATCH] Timeouts gone wild on ia64
>
>
>
>Here is a patch that greatly reduces that number of
>timeout (and EIO errors with soft mounts) that
>occur when a fast client is talking to a slow server.
>
>We were noticing a large number of EIO errors when
>a ia64 client was talking to a x86 server with
>soft mounts (ala autofs)....
>
>True, EIO errors should be expect with soft mounts but
>it turns out that thousands of timeouts were occurring on
>a ia64 client compared to 50 to 60 timeouts with
>a x86 client when talking to the same slow server and
>generating the same traffic.
>
>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?
>
>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 14:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-09 13:40 [PATCH] Timeouts gone wild on ia64 Lever, Charles
2003-05-09 14:12 ` 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 15:24 Lever, Charles
2003-05-09 17:19 ` 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=3EBBB74B.4000008@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.