public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "H . J . Lu" <hjl@valinux.com>
To: Trond Myklebust <trond.myklebust@fys.uio.no>
Cc: Linux Kernel <linux-kernel@vger.kernel.org>,
	NFS maillist <nfs@lists.sourceforge.net>,
	Michael Kriss <kriss@fnal.gov>
Subject: Re: [NFS] [CFT] Improved RPC congestion handling for 2.4.0 (and 2.2.18)
Date: Wed, 24 Jan 2001 10:19:52 -0800	[thread overview]
Message-ID: <20010124101952.A24331@valinux.com> (raw)
In-Reply-To: <14904.54852.334762.889784@charged.uio.no> <20010122143740.A31589@valinux.com> <14956.48013.908491.509166@charged.uio.no> <20010122153638.B32449@valinux.com>
In-Reply-To: <20010122153638.B32449@valinux.com>; from hjl@valinux.com on Mon, Jan 22, 2001 at 03:36:38PM -0800

On Mon, Jan 22, 2001 at 03:36:38PM -0800, H . J . Lu wrote:
> On Tue, Jan 23, 2001 at 12:00:29AM +0100, Trond Myklebust wrote:
> > >>>>> " " == H J Lu <hjl@valinux.com> writes:
> > 
> >      > I got a report which indicates it may not be a good idea,
> >      > especially for UDP. Suppose you have a lousy LAN or NFS UDP
> >      > server for whatever reason, some NFS/UDP packets may get lost
> >      > very easily while a ping request may get through. In that case,
> >      > the rpc ping may slow down the NFS client over UDP
> >      > significantly.
> > 
> > Hi HJ,
> > 
> > Could you clarify this? Don't forget that we only send the ping after
> > a major timeout (usually after 3 or more resends).
> > 
> > IOW: If the ping gets through, then it'll have cost us 1 RPC request,
> > which is hardly a major contribution when talking about timescales of
> > the order of 5 seconds which is what that major timeout will have cost
> > (Don't forget that RPC timeout values increase geometrically).
> > 
> 
> Michael Kriss <kriss@fnal.gov> is having this problem. I think this
> problem may be very specific to his network setup. I couldn't duplicate
> his problem. My guess is for his case, every ping sent is a loss of
> a potential working retry packet. He is using Solaris NFS sever with
> Linux client. I had an impression that packets from Solaris NFS server
> was dropped quite often. I don't know what happened.
> 

I believe it is a false alarm. It turned out that the interface was not
in the full duplex mode. After turning on autonego on switch,
everything seems fine now. Sorry for that.

-- 
H.J. Lu (hjl@valinux.com)
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/

      reply	other threads:[~2001-01-24 18:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-12-14 14:16 [CFT] Improved RPC congestion handling for 2.4.0 (and 2.2.18) Trond Myklebust
2001-01-22 22:37 ` [NFS] " H . J . Lu
2001-01-22 23:00   ` Trond Myklebust
2001-01-22 23:36     ` H . J . Lu
2001-01-24 18:19       ` H . J . Lu [this message]

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=20010124101952.A24331@valinux.com \
    --to=hjl@valinux.com \
    --cc=kriss@fnal.gov \
    --cc=linux-kernel@vger.kernel.org \
    --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