Linux NFS development
 help / color / mirror / Atom feed
From: Tom McNeal <trmcneal@attbi.com>
To: Rex Dieter <rdieter@math.unl.edu>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>, nfs@lists.sourceforge.net
Subject: Re: RH 7.3 kernels and NFS performance
Date: Wed, 07 Aug 2002 10:19:05 -0700	[thread overview]
Message-ID: <3D515689.DE925A02@attbi.com> (raw)
In-Reply-To: Pine.LNX.4.44.0208071142060.1462-100000@duran.unl.edu

Rex Dieter wrote:
> 
> On Wed, 7 Aug 2002, Trond Myklebust wrote:
> 
> >
> > If you are getting that performance with v3, then it does indeed sound
> > like a bug somewhere. Try with a stock 2.4.19 kernel instead...
> 
> I just tested things with a test kernel (2.4.18-7) from redhat, and it
> sync write speeds were again way up there.  Problem fixed, as far as I'm
> concerned... hopefully, they'll release an errata soon.
> 
> --
> Rex A. Dieter                   rdieter@unl.edu
> Computer System Administrator   http://www.math.unl.edu/~rdieter/
> Mathematics and Statistics
> University of Nebraska Lincoln

and

"Lever, Charles" wrote:
> 
> hi jeff-
> 
> >    I remember reading on the list about the terrible NFS
> > performance of the latest RH kernels. Would someone
> > care to summarize this for me (UDP or TCP, etc.)? Also,
> > does anyone have any rough estimates of the performance
> > hit?
> 
> if you are referring to bad NFS client performance, this
> is due to a bug in the Linux IP fragmentation logic which
> causes it to send part of a fragmented packet, and drop
> the rest, if it runs out of socket buffer space during
> the fragmentation process.
> 
> thus it only affects NFS over UDP.
> 
> there is an easy workaround:  enlarge the size of the
> RPC transport socket's buffers.  see the NFS FAQ for
> instructions.
> 
> a bug was reported in the eepro100 driver too, and that
> may have some effect on client performance.
> 

So if this is one and the same bug, then enlarging the transport
socket size is actually discussed in the performance section
of the howto documents (section 5.7) at 
http://nfs.sourceforge.net/nfs-howto/performance.html#MEMLIMITS

Tom
--
------------------------------------------------------------
Tom McNeal       trmcneal@attbi.com     (650)906-0761 (cell) 
------------------------------------------------------------


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
NFS maillist  -  NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs

  reply	other threads:[~2002-08-07 17:15 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-08-07 15:35 RH 7.3 kernels and NFS performance Jeff Layton
2002-08-07 15:37 ` Rex Dieter
2002-08-07 15:55   ` Trond Myklebust
2002-08-07 16:05     ` Rex Dieter
2002-08-07 16:17       ` Trond Myklebust
2002-08-07 16:21         ` Rex Dieter
2002-08-07 16:25           ` Trond Myklebust
2002-08-07 16:43             ` Rex Dieter
2002-08-07 17:19               ` Tom McNeal [this message]
2002-08-07 19:04               ` Bill Rugolsky Jr.
2002-08-08  5:08               ` Seth Vidal
2002-08-08 11:56                 ` Rex Dieter
  -- strict thread matches above, loose matches on Subject: below --
2002-08-07 15:45 Lever, Charles

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=3D515689.DE925A02@attbi.com \
    --to=trmcneal@attbi.com \
    --cc=nfs@lists.sourceforge.net \
    --cc=rdieter@math.unl.edu \
    --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