From: Dan Yocum <yocum@fnal.gov>
To: Benjamin LaHaise <bcrl@redhat.com>
Cc: Trond Myklebust <trond.myklebust@fys.uio.no>,
linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: ns83820 bug. [was Re: Poor NFS client performance on 2.4.18?]
Date: Thu, 09 May 2002 15:54:53 -0500 [thread overview]
Message-ID: <3CDAE21D.F671AFFA@fnal.gov> (raw)
In-Reply-To: <3CC86BDC.C8784EA2@fnal.gov> <shsu1pyppnz.fsf@charged.uio.no> <3CD6FE1E.A20384D@fnal.gov> <E174zP0-0007N9-00@charged.uio.no> <3CD7F385.BAA3870B@fnal.gov> <3CD7F8A2.24DF8433@fnal.gov> <3CD98837.16B32F84@fnal.gov> <20020508180705.B14959@redhat.com>
Ben, Trond,
Ugh. It's been a bad week in general. Anyway, yes, you're right, the 0.17
upgrade did the trick - I had actually tried that, but had accidentally
re-applied the rpc_tweaks dif which knocked the performance down again.
Backing out that patch, updating to v 0.17 of the ns83820 driver and all is
well, again.
So, it's back in Trond's court, with the rpc_tweaks causing the slow
read/write over NFS, problem.
Trond, if all I want is 32k block transfers from that dif, can I just apply
the following, or is there more to it:
diff -u --recursive --new-file
linux-2.4.18-svc_tcp/include/linux/nfsd/const.h
linux-2.4.18-rpc_cong/include/linux/nfsd/const.h
--- linux-2.4.18-svc_tcp/include/linux/nfsd/const.h Sat Apr 1 18:04:27
2000+++ linux-2.4.18-rpc_cong/include/linux/nfsd/const.h Wed Feb 20
17:20:45 2002@@ -21,7 +21,7 @@
/*
* Maximum blocksize supported by daemon currently at 8K
*/
-#define NFSSVC_MAXBLKSIZE 8192
+#define NFSSVC_MAXBLKSIZE (32*1024)
#ifdef __KERNEL__
Thanks,
Dan
Benjamin LaHaise wrote:
>
> Upgrade to 0.17 (which is in 2.4.19-pre5 or so and later) and you should
> find the issue resolved.
>
> -ben
>
> On Wed, May 08, 2002 at 03:19:03PM -0500, Dan Yocum wrote:
> > Trond, et al.
> >
> > You're right, it's a driver (ns83820) issue. Strange that it only shows up
> > when trying to execute an app that's mounted via NFS, but, whatever.
> > Running apps from the the NFS volumes with the eepro100 adapter that's on
> > the machine works fine with the updated NFS_all patch applied.
> >
> > Thanks, again,
> > Dan
> >
> >
> > Dan Yocum wrote:
> > >
> > > Dan Yocum wrote:
> > > >
> > > > Trond Myklebust wrote:
> > > > >
> > > > > On Tuesday 7. May 2002 00:05, Dan Yocum wrote:
> > > > > > Trond,
> > > > > >
> > > > > > OK, so backing out the rpc_tweaks dif fixed the performance problem,
> > > > > > however, seems to have introduced another problem that appears to be
> > > > > > stemming from the seekdir.dif. Attempting to run an app from an IRIX
> > > > > > client (that has the 32bitclients option set) freezes the NFS volume - one
> > > > > > can't access it from the Linux side, anymore.
> > > > > >
> > > > > > You can read and write to the NFS volume *before* trying to run something
> > > > > > from there, but not after.
> > > > > >
> > > > > > Ideas?
> > > > >
> > > > > That smells like another network driver bug. Have you tcpdumped the traffic
> > > > > between client and server?
> > > >
> > > > Ah, that may be the case - the problem also exists with a Linux server as
> > > > well... let me check, and I'll let you know.
> > >
> > > I take that back - it's only hanging on the Linux server when the IRIX
> > > server is already hung.
> >
> >
> > --
> > Dan Yocum
> > Sloan Digital Sky Survey, Fermilab 630.840.6509
> > yocum@fnal.gov, http://www.sdss.org
> > SDSS. Mapping the Universe.
> > -
> > To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> > the body of a message to majordomo@vger.kernel.org
> > More majordomo info at http://vger.kernel.org/majordomo-info.html
> > Please read the FAQ at http://www.tux.org/lkml/
>
> --
> "You will be reincarnated as a toad; and you will be much happier."
--
Dan Yocum
Sloan Digital Sky Survey, Fermilab 630.840.6509
yocum@fnal.gov, http://www.sdss.org
SDSS. Mapping the Universe.
prev parent reply other threads:[~2002-05-09 20:54 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
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 [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=3CDAE21D.F671AFFA@fnal.gov \
--to=yocum@fnal.gov \
--cc=bcrl@redhat.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.