From: I Lee Hetherington <ilh@sls.lcs.mit.edu>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: nfs@lists.sourceforge.net
Subject: Re: 2.4.18: NFS_ALL patch greatly hurting UDP speed
Date: Wed, 20 Mar 2002 10:39:55 -0500 [thread overview]
Message-ID: <3C98AD4B.8244EDC0@sls.lcs.mit.edu> (raw)
In-Reply-To: shs7kollatu.fsf@charged.uio.no
Did you ever get a chance to look at the tcpdumps I sent you?
Given that UDP is now *100* times slower with NFS_ALL vs. without,
something is fishy. We have always gotten good performance with UDP in
our network, even with the 1Gb/s to 100Mb/s switching. Maybe our
switches have big enough buffers to deal with the peaks.
--Lee Hetherington
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next parent reply other threads:[~2002-03-20 15:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <3C88F8EE.86058BD5@sls.lcs.mit.edu>
[not found] ` <shs7kollatu.fsf@charged.uio.no>
2002-03-20 15:39 ` I Lee Hetherington [this message]
2002-03-20 15:45 ` 2.4.18: NFS_ALL patch greatly hurting UDP speed Trond Myklebust
2002-03-20 15:50 ` Trond Myklebust
2002-03-20 18:23 ` Eric Whiting
2002-03-21 0:20 ` Ion Badulescu
2002-03-21 0:33 ` 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=3C98AD4B.8244EDC0@sls.lcs.mit.edu \
--to=ilh@sls.lcs.mit.edu \
--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