From: David Woodhouse <dwmw2@infradead.org>
To: root@chaos.analogic.com
Cc: Keith Owens <kaos@ocs.com.au>,
Linux kernel <linux-kernel@vger.kernel.org>
Subject: Re: spin-locks
Date: Fri, 10 May 2002 15:17:50 +0100 [thread overview]
Message-ID: <26626.1021040270@redhat.com> (raw)
In-Reply-To: <Pine.LNX.3.95.1020510095907.2632A-100000@chaos.analogic.com>
root@chaos.analogic.com said:
> Well, here is code that worked on linux 2.2.17. Same CPUs, same
> everything... Just a different version of OS...
I suspect your code was protected by the BKL in 2.2.17, not by your
'spinlocks'.
root@chaos.analogic.com said:
> cli
> lock
> incb (lockf) # Bump lock-value
Ponder what happens if two CPUs get here at the same time. Lock count is
now two.
> 1: cmpb $1,(lockf) # See if we own it
> jnz 1b # Nope, spin until we do.
Now they both spin forever.
--
dwmw2
next prev parent reply other threads:[~2002-05-10 14:21 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-10 12:58 spin-locks Richard B. Johnson
2002-05-10 13:24 ` spin-locks Keith Owens
2002-05-10 14:06 ` spin-locks Richard B. Johnson
2002-05-10 14:17 ` David Woodhouse [this message]
2002-05-10 14:28 ` spin-locks Richard B. Johnson
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=26626.1021040270@redhat.com \
--to=dwmw2@infradead.org \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=root@chaos.analogic.com \
/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®