public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Dan Yocum <yocum@fnal.gov>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: Poor NFS client performance on 2.4.18?
Date: Fri, 26 Apr 2002 09:51:40 -0500	[thread overview]
Message-ID: <3CC9697C.41473ED9@fnal.gov> (raw)
In-Reply-To: <3CC86BDC.C8784EA2@fnal.gov> <shsu1pyppnz.fsf@charged.uio.no>

Trond,

So, would I be correct in assuming that backing out the
linux-2.4.18-ping.dif patch would solve the problem in the short term?

Thanks,
Dan

Trond Myklebust wrote:
> 
> >>>>> " " == Dan Yocum <yocum@fnal.gov> writes:
> 
>      > Trond, et al.  I'm getting poor NFS performance (~250KBps read
>      > and write) on 2.4.18 and am wondering if I'm the only one.
>      > There is no performance drop under other OSs or other kernel
>      > versions, so I don't think it's the server.
> 
>      > Here's the the details:
> 
>      > 2.4.18 patched with:
>      >  NFS client patches (linux-2.4.18-NFS_ALL.dif)
>      >  xfs-1.1-PR1-2.4.18-all.patch Ingo's Foster IRQ patch (these
>      >  are dual Xeons)
> 
>      > If you need any more details, let me know.
> 
> The latest NFS_ALL patches include experimental code that changes the
> UDP congestion control. I'm basically trying to relax the algorithm to
> what is standard on *BSD (i.e. we follow the standard Van Jacobson).
> 
> This would mean that we don't wait for the reply from the server
> before we send off the next request. Unfortunately, there appears to
> be a lot of setups out there that start to drop packets when this
> occurs, and I haven't yet finished determining the root cause.
> 
> If I can manage to get my laptop to work again, I'll try to
> investigate a bit more this weekend...
> 
> Cheers,
>   Trond



-- 
Dan Yocum
Sloan Digital Sky Survey, Fermilab  630.840.6509
yocum@fnal.gov, http://www.sdss.org
SDSS.  Mapping the Universe.

  reply	other threads:[~2002-04-26 14:51 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-25 20:49 Poor NFS client performance on 2.4.18? Dan Yocum
2002-04-26 13:14 ` Trond Myklebust
2002-04-26 14:51   ` Dan Yocum [this message]
2002-04-28 19:29     ` Trond Myklebust
2002-05-06 22:05   ` Dan Yocum
2002-05-07  7:28     ` Trond Myklebust
2002-05-07 15:32       ` Dan Yocum
2002-05-07 15:54         ` Dan Yocum
2002-05-08 20:19           ` ns83820 bug. [was Re: Poor NFS client performance on 2.4.18?] Dan Yocum
2002-05-08 22:07             ` Benjamin LaHaise
2002-05-09 20:54               ` Dan Yocum

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=3CC9697C.41473ED9@fnal.gov \
    --to=yocum@fnal.gov \
    --cc=linux-kernel@vger.kernel.org \
    --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