From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Nick Piggin <npiggin@suse.de>
Cc: Andrew Morton <akpm@linux-foundation.org>,
Paul Mackerras <paulus@samba.org>,
tony.luck@intel.com, linux-arch@vger.kernel.org
Subject: Re: [patch] bitops: lock bitops
Date: Mon, 23 Jul 2007 19:50:55 +1000 [thread overview]
Message-ID: <1185184255.5439.109.camel@localhost.localdomain> (raw)
In-Reply-To: <20070723061642.GA7559@wotan.suse.de>
On Mon, 2007-07-23 at 08:16 +0200, Nick Piggin wrote:
>
> OK, I'll mention that in the ppc code... but generic code shouldn't
> rely on this anyway, right? (Or was it decided that spinlocks must
> fence IO?).
>
> Would _io postfixed locks be a sane way to handle this?
It's unclear what spinlocks are supposed to do, but for ppc, I decided
to be safe and put the fencing implicitely in spin_unlock.
Ben.
prev parent reply other threads:[~2007-07-23 9:51 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-12 3:14 [patch] bitops: lock bitops Nick Piggin
2007-07-12 3:38 ` David Miller
2007-07-12 3:49 ` Nick Piggin
2007-07-12 21:36 ` Ralf Baechle
2007-07-23 6:06 ` Benjamin Herrenschmidt
2007-07-23 6:16 ` Nick Piggin
2007-07-23 9:50 ` Benjamin Herrenschmidt [this message]
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=1185184255.5439.109.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=akpm@linux-foundation.org \
--cc=linux-arch@vger.kernel.org \
--cc=npiggin@suse.de \
--cc=paulus@samba.org \
--cc=tony.luck@intel.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;
as well as URLs for NNTP newsgroup(s).