From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Wolfgang Grandegger <wg@grandegger.com>
Cc: linuxppc-embedded@ozlabs.org
Subject: Re: Is in_le32 and out_le32 atomic?
Date: Mon, 11 Dec 2006 17:47:50 +1100 [thread overview]
Message-ID: <1165819670.7260.38.camel@localhost.localdomain> (raw)
In-Reply-To: <4579C586.5040809@grandegger.com>
> Can anybody tell me why the spin_* protection is needed? I thought that
> 32-bit read and write operations are atomic.
It doesn't seem to make sense indeed...
Ben.
prev parent reply other threads:[~2006-12-11 6:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-08 20:05 Is in_le32 and out_le32 atomic? Wolfgang Grandegger
2006-12-08 20:15 ` Arnd Bergmann
2006-12-11 6:48 ` Benjamin Herrenschmidt
2006-12-11 8:11 ` Wolfgang Grandegger
2006-12-11 9:05 ` Benjamin Herrenschmidt
2006-12-11 6:47 ` 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=1165819670.7260.38.camel@localhost.localdomain \
--to=benh@kernel.crashing.org \
--cc=linuxppc-embedded@ozlabs.org \
--cc=wg@grandegger.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).