public inbox for linux-arch@vger.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: dhowells@redhat.com
Cc: James.Bottomley@steeleye.com, akpm@osdl.org, torvalds@osdl.org,
	davem@davemloft.com, wli@holomorphy.com, matthew@wil.cx,
	linux-kernel@vger.kernel.org, linux-arch@vger.kernel.org
Subject: Re: [PATCH 3/3] WorkStruct: Use direct assignment rather than cmpxchg()
Date: Thu, 07 Dec 2006 14:11:40 -0800 (PST)	[thread overview]
Message-ID: <20061207.141140.39644636.davem@davemloft.net> (raw)
In-Reply-To: <10660.1165526163@redhat.com>

From: David Howells <dhowells@redhat.com>
Date: Thu, 07 Dec 2006 21:16:03 +0000

> I don't know that sparc32 can do conditional instructions for
> example.  If we force this assumption it becomes a potential
> limitation on the archs we can support.  OTOH, it may be that every
> arch that supports SMP and has to emulate bitops with spinlocks also
> supports conditional stores; but I don't know that.

Sparc32 has normal branches but no conditional instruction execution.

  reply	other threads:[~2006-12-07 22:11 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-12-07 15:31 [PATCH 1/3] WorkStruct: Fix up some PA-RISC work items David Howells
2006-12-07 15:31 ` [PATCH 2/3] WorkStruct: Add assign_bits() to give an atomic-bitops safe assignment David Howells
2006-12-07 15:31 ` [PATCH 3/3] WorkStruct: Use direct assignment rather than cmpxchg() David Howells
2006-12-07 16:54   ` Andrew Morton
2006-12-07 20:06     ` David Howells
2006-12-07 21:06       ` Andrew Morton
2006-12-07 21:06       ` James Bottomley
2006-12-07 21:16         ` David Howells
2006-12-07 22:11           ` David Miller [this message]
2006-12-07 23:42       ` Russell King
2006-12-07 23:58         ` David Howells
2006-12-08 11:14           ` Russell King
2006-12-08 13:57             ` David Howells
2006-12-08  3:42 ` [PATCH 1/3] WorkStruct: Fix up some PA-RISC work items Kyle McMartin

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=20061207.141140.39644636.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=James.Bottomley@steeleye.com \
    --cc=akpm@osdl.org \
    --cc=davem@davemloft.com \
    --cc=dhowells@redhat.com \
    --cc=linux-arch@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthew@wil.cx \
    --cc=torvalds@osdl.org \
    --cc=wli@holomorphy.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