From: Benjamin LaHaise <bcrl@redhat.com>
To: "Lever, Charles" <Charles.Lever@netapp.com>
Cc: nfs@lists.sourceforge.net
Subject: Re: RedHat 7.3 crashed NetApp?
Date: Fri, 17 May 2002 20:17:59 -0400 [thread overview]
Message-ID: <20020517201759.C16999@redhat.com> (raw)
In-Reply-To: <6440EA1A6AA1D5118C6900902745938E50CF34@black.eng.netapp.com>; from Charles.Lever@netapp.com on Fri, May 17, 2002 at 03:17:53PM -0700
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain; charset=us-ascii, Size: 859 bytes --]
[a few data points from the bugzilla entries]
On Fri, May 17, 2002 at 03:17:53PM -0700, Lever, Charles wrote:
> i'm wondering what are the common elements here:
>
> is the EEpro 100 ethernet card common to all clients
> that exhibit this problem?
eepro, tulip, 3com have all shown problems with 2.4.18 (at least
serious performance issues).
> NFSv3 over UDP?
Yes. A number of people have now reported that forcing v2 operation
does not result in slow performance, whereas in the 2.4.9-ac12 based
kernel, v3 was fine.
-ben
_______________________________________________________________
Hundreds of nodes, one monster rendering program.
Now that’s a super model! Visit http://clustering.foundries.sf.net/
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2002-05-18 0:18 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-17 22:17 RedHat 7.3 crashed NetApp? Lever, Charles
2002-05-18 0:17 ` Benjamin LaHaise [this message]
2002-05-18 1:43 ` seth vidal
-- strict thread matches above, loose matches on Subject: below --
2002-05-21 21:53 Vladimir Vuksan
2002-05-20 14:19 Lever, Charles
2002-05-20 14:46 ` Benjamin LaHaise
2002-05-17 13:14 Cooke, Alan
2002-05-17 15:11 ` H . J . Lu
2002-05-17 17:16 ` Daryl Herzmann
2002-05-17 17:32 ` Benjamin LaHaise
2002-05-16 22:39 H . J . Lu
2002-05-16 23:16 ` seth vidal
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=20020517201759.C16999@redhat.com \
--to=bcrl@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox