From: Benjamin LaHaise <bcrl@redhat.com>
To: Eric Whiting <ewhiting@amis.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
Date: Thu, 14 Nov 2002 18:23:20 -0500 [thread overview]
Message-ID: <20021114182320.K20258@redhat.com> (raw)
In-Reply-To: <3DD4305B.D439C6CD@amis.com>; from ewhiting@amis.com on Thu, Nov 14, 2002 at 04:23:07PM -0700
On Thu, Nov 14, 2002 at 04:23:07PM -0700, Eric Whiting wrote:
> Both of these NICs seemed to have the same behavior.
> <6>eth0: Intel(R) PRO/1000 Network Connection
> <6>eth1: NetGear GA620 Gigabit Ethernet at 0xea060000, irq 11
>
> Yes -- I'm running on a 32bit/33Mhz bus right now. I do have a Sun 280R
> with a 64bit/66Mhz card in a 66Mhz slot that doesn't even seem to
> support jumbo frames at all.
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
next prev parent reply other threads:[~2002-11-14 23:23 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 [this message]
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=20021114182320.K20258@redhat.com \
--to=bcrl@redhat.com \
--cc=canon@pookie.nersc.gov \
--cc=ewhiting@amis.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.