From: "Quentin Fennessy" <quentin.fennessy@amd.com>
To: "Andrew Ryan" <andrewr@nam-shub.com>
Cc: trond.myklebust@fys.uio.no, nfs@lists.sourceforge.net
Subject: Re: 2.4.20-rc1 NFS/TCP client (still) hangs running dbench 2.0
Date: Sun, 03 Nov 2002 08:16:34 -0600 [thread overview]
Message-ID: <cs9n0oqbuwt.fsf@tesla.amd.com> (raw)
In-Reply-To: <5.0.2.1.0.20021102211350.0291eec0@pop.sfrn.dnai.com> ( "Andrew Ryan"'s message of "Sat, 02 Nov 2002 21:21:02 -0800")
>>>>> Andrew Ryan writes:
> At 10:58 PM 11/1/02 +0100, Trond Myklebust wrote:
>> It is probably just the (known) accounting error in the 'retransmit'
>> statistics. Try applying the patch
>>
>> http://www.fys.uio.no/~trondmy/src/2.4.20-pre9/linux-2.4.20-01-call_start.dif
>>
>> if it bothers you.
> Yes, you are right, it seems the counter is broken, and performance is
> fine. I did bonnie++ runs with 2.4.20rc1 kernels with and without the
> call_start patch, and didn't see any significant difference.
> But, it does bother me since I want to be able to diagnose network errors if
> I ever have them, and with a busted counter it will be impossible to tell
> what my real error rate is. Can the call_start patch go to Marcelo for
> 2.4.20rc2?
I'm an end user with approximately 3000 Linux NFS clients.
I will really appreciate correct counters when I'm debugging
nfs server, client and network problems. I've had to ignore
spurious counts of nfs retrans while debugging network issues.
I hope this patch will be in 2.4.20rc2. Thanks to all of you for
providing an excellent client-side implementation. And I am
serious.
> After a bonnie run with the call_start patch, I get this, which is much
> better :)
> $ nfsstat -c
> Client rpc stats:
> calls retrans authrefrsh
> 1648050 0 0
--
Quentin Fennessy Quentin.Fennessy@amd.com
Office: 512.602.3873
Cell: 512.694.7489
-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-11-03 14:16 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3DC2E7B6.6090400@collab.net>
2002-11-01 21:18 ` 2.4.20-rc1 NFS/TCP client (still) hangs running dbench 2.0 Andrew Ryan
2002-11-01 21:58 ` Trond Myklebust
2002-11-03 5:21 ` Andrew Ryan
2002-11-03 14:16 ` Quentin Fennessy [this message]
2002-11-01 22:06 ` [PATCH] another kmap imbalance in 2.4.x/2.5.x RPC Trond Myklebust
[not found] <6440EA1A6AA1D5118C6900902745938E07D55047@black.eng.netapp. com>
2002-11-04 16:51 ` 2.4.20-rc1 NFS/TCP client (still) hangs running dbench 2.0 Andrew Ryan
2002-11-03 17:05 Lever, Charles
-- strict thread matches above, loose matches on Subject: below --
2002-11-03 0:33 Lever, Charles
[not found] <6440EA1A6AA1D5118C6900902745938E07D5503C@black.eng.netapp. com>
2002-11-02 16:49 ` Andrew Ryan
2002-11-02 14:57 Lever, Charles
2002-11-02 21:19 ` Trond Myklebust
2002-10-31 5:06 Andrew Ryan
2002-11-01 17:24 ` Trond Myklebust
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=cs9n0oqbuwt.fsf@tesla.amd.com \
--to=quentin.fennessy@amd.com \
--cc=andrewr@nam-shub.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox