From: Chris Worley <cworley@lnxi.com>
To: nfs@lists.sourceforge.net
Subject: NFS not negotiating MTU correctly?
Date: 25 May 2004 07:18:46 -0600 [thread overview]
Message-ID: <1085491125.30311.20808.camel@localhost> (raw)
I don't know why this is an NFS specific problem (I'd think this would
be part of IP)...
I run 9K MTU's on all my NFS servers and most of my clients. Great
performance (the servers are also channel bonded... but that's
irrelevant).
Clients that can't do 9K MTU's work with the 9K MTU systems for all
sorts of network tasks, except NFS.
To get NFS to work, I either have to use NFS over TCP, or set my w/rsize
below 1500 bytes. Both cause performance problems.
In grilling my switch vendor, they assure me that it's the client &
servers job to negotiate properly fragmented packets based on the lessor
MTU.
Chris
-------------------------------------------------------
This SF.Net email is sponsored by: Oracle 10g
Get certified on the hottest thing ever to hit the market... Oracle 10g.
Take an Oracle 10g class now, and we'll give you the exam FREE.
http://ads.osdn.com/?ad_id=3149&alloc_id=8166&op=click
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next reply other threads:[~2004-05-25 14:23 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-25 13:18 Chris Worley [this message]
2004-05-25 15:04 ` NFS not negotiating MTU correctly? Trond Myklebust
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=1085491125.30311.20808.camel@localhost \
--to=cworley@lnxi.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 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.