From: Caleb Epstein <cae@bklyn.org>
To: linux-kernel@vger.kernel.org
Subject: Re: NFS client code slow in 2.4.3
Date: Tue, 3 Apr 2001 15:08:52 -0400 [thread overview]
Message-ID: <20010403150852.A1310@hagrid.bklyn.org> (raw)
In-Reply-To: <20010403145615.C1049@hagrid.bklyn.org>
In-Reply-To: <20010403145615.C1049@hagrid.bklyn.org>; from cae@bklyn.org on Tue, Apr 03, 2001 at 02:56:15PM -0400
On Tue, Apr 03, 2001 at 02:56:15PM -0400, Caleb Epstein wrote:
> I am having problems with timeouts and generaly throughput in
> the 2.4.3 NFS client side code which are not present in the 2.4.2
> kernel running in the same configuraiton on the same hardware. The
> machines are on a 100 Mbit switched local network with essentially
> no other trafic.
On second thought, it looks like 2.4.2 may also exhibit the
same behaviro after a little while. Now that the machine has
been up for a half hour or so, NFS traffic has become slow on
my 2.4.2 client again. I am seeing messages like this in my
kernel log:
Apr 3 15:01:54 hagrid kernel: nfs: server tela not responding, still trying
Apr 3 15:01:54 hagrid kernel: nfs: server tela OK
The machines are *not* having any connectivity problems, at
least judging from TCP sessions I have open between them.
So it would seem that NFS performace degrades over a very
short window in 2.4.2+. It seems to fairly fly when the
machine is freshly booted, but after 30 minutes or less, the
performance is severely degraded.
Is anyone using 2.4.2+ as a NFS server/client with success?
Am I missing something?
--
cae at bklyn dot org | Caleb Epstein | bklyn . org | Brooklyn Dust Bunny Mfg.
next prev parent reply other threads:[~2001-04-03 19:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-03 18:56 Caleb Epstein
2001-04-03 19:08 ` Caleb Epstein [this message]
2001-04-03 20:00 ` Trond Myklebust
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=20010403150852.A1310@hagrid.bklyn.org \
--to=cae@bklyn.org \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®