From: J Sloan <jjs@pobox.com>
To: trond.myklebust@fys.uio.no, linux-kernel <linux-kernel@vger.kernel.org>
Cc: Mark Hahn <hahn@physics.mcmaster.ca>
Subject: Re: sunrpc woes with tux2 in 2.4.15-pre8,9
Date: Thu, 22 Nov 2001 17:48:56 -0800 [thread overview]
Message-ID: <3BFDAB08.28F8B5C8@pobox.com> (raw)
In-Reply-To: <3BFD7633.2525641E@pobox.com> <shsn11eidv0.fsf@charged.uio.no> <3BFD9078.63FE28F2@pobox.com> <15357.38291.883472.720575@charged.uio.no>
Trond Myklebust wrote:
> Something is indeed very wrong. Your setup uses a PIII, and no SMP. It
> shouldn't be requiring atomic_dec_and_lock() at all. Certainly this is
> the case on my own setup on stock 2.4.15-pre9.
>
> Could you check that the TUX patch isn't squashing the #define and
> test for ATOMIC_DEC_AND_LOCK that is contained in
> include/linux/spinlock.h in the stock Linus kernel. The latter is a
> workaround that is designed to stop MODVERSIONS from interfering with
> the re-#definition of atomic_dec_and_lock() in spinlock.h.
Yes, it looks like he's doing just that -
I built it with smp enabled and the problem
goes away, so it's an implicit assumption
of smp in the current tux code.
cu
jjs
next prev parent reply other threads:[~2001-11-23 1:49 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-22 22:03 sunrpc woes with tux2 in 2.4.15-pre8,9 J Sloan
2001-11-22 23:29 ` Trond Myklebust
2001-11-22 23:55 ` J Sloan
2001-11-23 0:17 ` Trond Myklebust
2001-11-23 1:48 ` J Sloan [this message]
2001-11-23 10:54 ` Ingo Molnar
2001-11-23 22:43 ` J Sloan
2001-11-23 12:06 ` Ingo Molnar
2001-11-23 22:46 ` J Sloan
2001-11-24 1:46 ` J Sloan
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=3BFDAB08.28F8B5C8@pobox.com \
--to=jjs@pobox.com \
--cc=hahn@physics.mcmaster.ca \
--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