From: Keith Owens <kaos@sgi.com>
To: Piet Delaney <piet@www.piet.net>
Cc: Christoph Hellwig <hch@sgi.com>,
"Matt D. Robinson" <yakker@aparity.com>,
linux-kernel@vger.kernel.org, steiner@sgi.com, jeremy@sgi.com
Subject: Re: [PATCH] 2.5.44: lkcd (9/9): dump driver and build files
Date: Wed, 23 Oct 2002 08:56:18 +1000 [thread overview]
Message-ID: <15606.1035327378@ocs3.intra.ocs.com.au> (raw)
In-Reply-To: Your message of "22 Oct 2002 15:21:02 MST." <1035325262.6847.23.camel@www.piet.net>
On 22 Oct 2002 15:21:02 -0700,
Piet Delaney <piet@www.piet.net> wrote:
>Looks like your right, for parisc even these functions are using a
>spinlock. Is it really necessary for parisc to use spinlocks? Even
>Solaris doesn't use spinlocks for atomic set and reads of atomic
>variables.
Hardware restriction. Somebody read that "all locks can be implemented
in terms of a single hardware primitive" and believed it :(. The only
atomic operation on parisc is load and clear word. According to the
comments in asm-parisc/atomic.h, atomic_set should not require a lock,
but it is coded to use one. Atomic add/sub obviously needs a lock.
next prev parent reply other threads:[~2002-10-22 22:50 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-21 10:16 Matt D. Robinson
2002-10-21 21:21 ` Christoph Hellwig
2002-10-21 19:07 ` Matt D. Robinson
2002-10-21 22:06 ` Piet Delaney
2002-10-22 18:47 ` Christoph Hellwig
2002-10-22 11:57 ` Keith Owens
2002-10-22 22:21 ` Piet Delaney
2002-10-22 22:56 ` Keith Owens [this message]
2002-10-22 16:49 ` Matt D. Robinson
2002-10-22 2:04 ` Nicholas Wourms
2002-10-22 5:45 ` Matt D. Robinson
2002-10-22 13:00 ` Christoph Hellwig
2002-10-22 15:05 ` Suparna Bhattacharya
2002-10-22 9:49 ` Jens Axboe
2002-10-22 14:43 ` Randy.Dunlap
2002-10-22 14:59 ` Jens Axboe
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=15606.1035327378@ocs3.intra.ocs.com.au \
--to=kaos@sgi.com \
--cc=hch@sgi.com \
--cc=jeremy@sgi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=piet@www.piet.net \
--cc=steiner@sgi.com \
--cc=yakker@aparity.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®