From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: David Howells <dhowells@redhat.com>
Cc: Linux Kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] WorkStruct: Use direct assignment rather than cmpxchg()
Date: Sun, 10 Dec 2006 09:19:36 +1100 [thread overview]
Message-ID: <1165702776.1103.162.camel@localhost.localdomain> (raw)
In-Reply-To: <200612092059.kB9Kx1NC010199@hera.kernel.org>
> The problem is where we end up tangling with test_and_set_bit() emulated
> using spinlocks, and even then it's not a problem _provided_
> test_and_set_bit() doesn't attempt to modify the word if the bit was
> set.
I'm not 100% sure what is the problem there, but beware that bitops
don't provide the same semantics as spinlocks regarding memory ordering.
Ben.
parent reply other threads:[~2006-12-09 22:19 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <200612092059.kB9Kx1NC010199@hera.kernel.org>]
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=1165702776.1103.162.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=dhowells@redhat.com \
--cc=linux-kernel@vger.kernel.org \
/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®