From: Robert Love <rml@novell.com>
To: linux-os@analogic.com
Cc: Andrew Morton <akpm@osdl.org>,
Badari Pulavarty <pbadari@us.ibm.com>,
linux-kernel@vger.kernel.org
Subject: Re: 2.6.10-mm1 hang
Date: Wed, 19 Jan 2005 17:40:57 -0500 [thread overview]
Message-ID: <1106174457.5907.40.camel@localhost> (raw)
In-Reply-To: <Pine.LNX.4.61.0501191658020.11665@chaos.analogic.com>
On Wed, 2005-01-19 at 17:01 -0500, linux-os wrote:
> What would you expect this to do? After the first lock is
> obtained, the second MUST fail forever or else the spin-lock
> doesn't work. The code, above, just proves that spin-locks
> work!
He has a four processor machine. Since the lock is local, it is
somewhat odd that the other three lock up.
Robert Love
next prev parent reply other threads:[~2005-01-19 22:39 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-19 16:46 2.6.10-mm1 hang Badari Pulavarty
2005-01-19 21:31 ` Andrew Morton
2005-01-19 22:01 ` linux-os
2005-01-19 21:44 ` Badari Pulavarty
2005-01-19 22:40 ` Robert Love [this message]
2005-01-20 15:26 ` Badari Pulavarty
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=1106174457.5907.40.camel@localhost \
--to=rml@novell.com \
--cc=akpm@osdl.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-os@analogic.com \
--cc=pbadari@us.ibm.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