From: Trond Myklebust <trond.myklebust@fys.uio.no>
To: "Alex Kerkhove" <alex.kerkhove@staff.zeelandnet.nl>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: x86 SMP and RPC/NFS problems
Date: 09 Aug 2001 14:00:26 +0200 [thread overview]
Message-ID: <shs66bxigth.fsf@charged.uio.no> (raw)
In-Reply-To: <1C48875BDE7ED0469485A5FD49925C4AF01265@zmx.staff.zeelandnet.nl>
In-Reply-To: "Alex Kerkhove"'s message of "Wed, 8 Aug 2001 23:09:21 +0200"
>>>>> " " == Alex Kerkhove <alex.kerkhove@staff.zeelandnet.nl> writes:
> So my (blunt?) conclusion is that there must be some serious
> problems with RPC/NFS (I guess RPC) and 2.4 SMP kernels! (and
> lots of processes doing NFS stuff)
> Anyone any thoughts on this? My kernel hacking knowledge is
> limited, but I'm willing to test patches :)
Could you try out the patch
http://www.fys.uio.no/~trondmy/src/2.4.3/linux-2.4.3-rpc_smpfixes.dif
and see if it changes things?
The latter straightens out a number of iffy locking issues in the
net/sunrpc/xprt.c
Most of it will only hit you if you're doing NFS over TCP though...
Cheers,
Trond
prev parent reply other threads:[~2001-08-09 12:00 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-08-08 21:09 x86 SMP and RPC/NFS problems Alex Kerkhove
2001-08-08 21:30 ` Andrew Morton
2001-08-09 12:00 ` Trond Myklebust [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=shs66bxigth.fsf@charged.uio.no \
--to=trond.myklebust@fys.uio.no \
--cc=alex.kerkhove@staff.zeelandnet.nl \
--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