From: Eric Whiting <ewhiting@amis.com>
To: canon@pookie.nersc.gov
Cc: 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 16:13:42 -0700 [thread overview]
Message-ID: <3DD42E26.A603AD36@amis.com> (raw)
In-Reply-To: 200211142033.gAEKXGHe010083@pookie.nersc.gov
I tried various MTU values headed gradually towards 9000. I found that a
MTUs between 1500 and 7500 give me the expected performance. MTU values
of anything much more than that causes problems given my setup.
eric
canon@pookie.nersc.gov wrote:
>
> We had to set our MTUs to 8960 for things to work.
> We've never followed through to see what the issue
> was though.
>
> We are using SysKonnect cards and 2.4.18 kernel. Note,
> we haven't recently verified that the problem still
> exists.
>
> --Shane
-------------------------------------------------------
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:05 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 [this message]
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=3DD42E26.A603AD36@amis.com \
--to=ewhiting@amis.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