From: Robert Love <rml@novell.com>
To: Joseph Seigh <jseigh_02@xemaps.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: What does atomic_read actually do?
Date: Sun, 19 Dec 2004 17:21:06 -0500 [thread overview]
Message-ID: <1103494866.6052.354.camel@localhost> (raw)
In-Reply-To: <opsi707edhs29e3l@grunion>
On Sat, 2004-12-18 at 15:43 -0500, Joseph Seigh wrote:
> > it does so on *x86
>
> Is this documented for gcc anywhere? Just because it does so doesn't
> mean it's guaranteed.
Listen to what Arjan is saying: It is not a compiler feature. x86
already guarantees that an aligned word-size read is atomic in the
nothing-can-interleave sense.
Robert Love
next prev parent reply other threads:[~2004-12-19 22:19 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-18 16:23 What does atomic_read actually do? Joseph Seigh
2004-12-18 17:11 ` Paolo Ornati
2004-12-18 18:14 ` Joseph Seigh
2004-12-18 18:34 ` Arjan van de Ven
2004-12-18 19:20 ` Joseph Seigh
2004-12-18 19:39 ` Joe Korty
2004-12-18 19:54 ` Arjan van de Ven
2004-12-18 20:43 ` Joseph Seigh
2004-12-18 21:03 ` Brian Gerst
2004-12-19 22:21 ` Robert Love [this message]
2004-12-19 23:50 ` Joseph Seigh
2004-12-20 11:51 ` Arjan van de Ven
2004-12-20 12:52 ` Andrea Arcangeli
2004-12-20 20:51 ` Joseph Seigh
2004-12-18 20:47 ` Brian Gerst
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=1103494866.6052.354.camel@localhost \
--to=rml@novell.com \
--cc=jseigh_02@xemaps.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