From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: Eric Whiting <ewhiting@amis.com>
Cc: "nfs@lists.sourceforge.net" <nfs@lists.sourceforge.net>
Subject: Re: 2.4.20rc1 NFS V3 UDP client problems
Date: 14 Nov 2002 20:47:46 +0100 [thread overview]
Message-ID: <shsptt83pct.fsf@helicity.uio.no> (raw)
In-Reply-To: <3DD3E796.46E4F4AC@amis.com>
>>>>> " " == Eric Whiting <ewhiting@amis.com> writes:
> I disabled jumbo frames and I'm seeing 70M/s reads (with a
> clean cache)..
> There must be a UDP or NFS client problem with the 9000 mtu
> packets.
NFS neither knows nor cares what the MTU is: all it knows is that it
has a socket. I've suspected a bug in the UDP layer for a long time as
you are far from being the first person to report this problem when
enabling jumbo frames.
Cheers,
Trond
-------------------------------------------------------
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 19:47 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 [this message]
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 ` 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=shsptt83pct.fsf@helicity.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=ewhiting@amis.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