From: Eric Whiting <ewhiting@amis.com>
To: "nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>
Subject: Re: 2.4.20rc1 NFS V3 UDP client problems
Date: Thu, 14 Nov 2002 11:12:38 -0700 [thread overview]
Message-ID: <3DD3E796.46E4F4AC@amis.com> (raw)
In-Reply-To: 3DD3DF5F.854AD688@amis.com
I disabled jumbo frames and I'm seeing 70M/s reads (with a clean
cache)..
There must be a UDP or NFS client problem with the 9000 mtu packets.
eric
Eric Whiting wrote:
>
> I'm seeing some 2.4.20rc1 client problems.
>
> 25 seconds to write a 1G file
> 13 minutes to read that file back
>
> CLIENT 2.4.20rc1 NFSV3 UDP HIGHMEM SUPPORT ON
> gigE card with jumbo frames enabled
> Tested with both netgear and intel -- same result
>
> SERVER
> Netapps 825 ontap 6.3
> gigE card with jumbo frames enabled
>
> private point-to-point connection.
>
> Is this a HIGHMEM problem? Or is it related to jumbo frames? I'll test
> with both disabled.
>
> I'm seeing network errors on the client -- dropped and overruns are both
> the same.
>
> Anything I should try?
>
> eric
>
> # time dd if=/dev/zero of=file1 bs=1G count=1
> 1+0 records in
> 1+0 records out
>
> real 0m25.881s
> user 0m0.000s
> sys 0m4.220s
>
> (run a program to calloc 1G of RAM and clear some buffer cache)
>
> # time dd if=file1 of=/dev/null
>
> 2097152+0 records in
> 2097152+0 records out
>
> real 13m7.445s
> user 0m0.370s
> sys 0m2.160s
>
> # ifconfig eth0
> eth0 Link encap:Ethernet HWaddr 00:02:B3:AC:52:F5
> inet addr:10.0.0.2 Bcast:10.255.255.255 Mask:255.0.0.0
> UP BROADCAST RUNNING MULTICAST MTU:9000 Metric:1
> RX packets:1534585 errors:10240 dropped:10240 overruns:10240
> frame:0
> TX packets:5332748 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
> RX bytes:2069590604 (1973.7 Mb) TX bytes:587855320 (560.6 Mb)
> Interrupt:12 Base address:0xc000 Memory:ea020000-ea040000
>
> -------------------------------------------------------
> This sf.net email is sponsored by: To learn the basics of securing
> your web site with SSL, click here to get a FREE TRIAL of a Thawte
> Server Certificate: http://www.gothawte.com/rd524.html
> _______________________________________________
> NFS maillist - NFS@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/nfs
-------------------------------------------------------
This sf.net email is sponsored by: To learn the basics of securing
your web site with SSL, click here to get a FREE TRIAL of a Thawte
Server Certificate: http://www.gothawte.com/rd524.html
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-11-14 18:04 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-11-14 17:37 2.4.20rc1 NFS V3 UDP client problems Eric Whiting
2002-11-14 18:12 ` Eric Whiting [this message]
2002-11-14 19:47 ` Trond Myklebust
2002-11-14 20:33 ` canon
2002-11-14 23:13 ` Eric Whiting
2002-11-14 23:11 ` Benjamin LaHaise
2002-11-14 23:23 ` Eric Whiting
2002-11-14 23:23 ` Benjamin LaHaise
2002-11-18 18:59 ` 2.4.20rc1 NFS V3 UDP client problems -- (not a problem now) Eric Whiting
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=3DD3E796.46E4F4AC@amis.com \
--to=ewhiting@amis.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