Linux NFS development
 help / color / mirror / Atom feed
From: Eric Whiting <ewhiting@amis.com>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: canon@pookie.nersc.gov,
	Trond Myklebust <trond.myklebust@fys.uio.no>,
	"nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>
Subject: Re: 2.4.20rc1 NFS V3 UDP client problems -- (not a problem now)
Date: Mon, 18 Nov 2002 11:59:47 -0700	[thread overview]
Message-ID: <3DD938A3.682C38E3@amis.com> (raw)
In-Reply-To: 20021114182320.K20258@redhat.com

Ben, 

I found a 64Bit/66Mhz PCI bus and the jumbo frames are working fine.
Same 
kernel, same network cards, same Netapp 825 filer -- simply a different
motherboard.

Here are the NFS client read/write speeds for my setup.  The write
speeds appear to be somewhat limited by the netapps 825 disk/cpu speed.
I wish I had a netapps 9xx to test.

        TCP      UDP
READ    99MB/s  104MB/s
WRITE   36MB/s   49MB/s

UDP looks good with my current setup -- but with the gigE running jumbo
frames in the 32 bit PCI bus the UDP was sick on the reads -- 1MB/s.

Read testing is:
while(true);do mount blaa;dd if=path of=/dev/null bs=x count=y;umount
blaa;done
where bs/count equal a 500M file -- to use the netapps cache.

Write testing is:
dd if=/dev/zero of=file bs=1M

Network rates monitored using netapps syststat and the time results.

eric


Benjamin LaHaise wrote:
> I'd guess you're hitting the PCI bandwidth limitations then, as the larger
> packets permit greater throughput, which in turn drives up bus utilizations.
> If you've got any disk controllers on the same bus, that would definately
> explain the problem (or any other devices on the bus that are in use).
> 
>                 -ben


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

      reply	other threads:[~2002-11-18 18:58 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
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               ` Eric Whiting [this message]

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=3DD938A3.682C38E3@amis.com \
    --to=ewhiting@amis.com \
    --cc=bcrl@redhat.com \
    --cc=canon@pookie.nersc.gov \
    --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