From: "Chris Friesen" <cfriesen@nortel.com>
To: Jan Engelhardt <jengelh@computergmbh.de>
Cc: Chris Snook <csnook@redhat.com>,
Jerry Jiang <wjiang@resilience.com>,
"Robert P. J. Day" <rpjday@mindspring.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: why are some atomic_t's not volatile, while most are?
Date: Tue, 07 Aug 2007 16:49:31 -0600 [thread overview]
Message-ID: <46B8F6FB.8070904@nortel.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0708080005260.26397@fbirervta.pbzchgretzou.qr>
Jan Engelhardt wrote:
> On Aug 7 2007 15:38, Chris Friesen wrote:
>>That volatile is there precisely to force the compiler to dereference it every
>>single time.
> Actually, the dereference will be done once (or more often if registers
> are short or the compiler does not feel like keeping it around),
> and the read from memory will be done on every iteration ;-)
My bad. You are, of course, correct. :)
Chris
next prev parent reply other threads:[~2007-08-07 22:49 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-01 12:49 why are some atomic_t's not volatile, while most are? Robert P. J. Day
2007-08-06 4:35 ` Jerry Jiang
2007-08-06 14:12 ` Chris Snook
2007-08-07 15:51 ` Chris Friesen
2007-08-07 20:32 ` Chris Snook
2007-08-07 21:02 ` Chris Friesen
2007-08-07 21:19 ` Chris Snook
2007-08-07 21:38 ` Chris Friesen
2007-08-07 22:02 ` Chris Snook
2007-08-07 22:46 ` Chris Friesen
2007-08-07 22:06 ` Jan Engelhardt
2007-08-07 22:49 ` Chris Friesen [this message]
2007-08-07 22:32 ` Zan Lynx
2007-08-08 1:31 ` Chris Snook
2007-08-08 4:50 ` Chris Friesen
2007-08-08 6:47 ` Chris Snook
2007-08-08 8:16 ` Jerry Jiang
2007-08-08 8:27 ` Jerry Jiang
2007-08-08 20:54 ` Chris Snook
2007-08-09 12:37 ` Robert P. J. Day
2007-08-09 12:52 ` Chris Snook
2007-08-09 18:02 ` Robert P. J. Day
2007-08-09 18:04 ` Robert P. J. Day
2007-08-08 2:27 ` Jerry Jiang
2007-08-08 5:39 ` Chris Snook
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=46B8F6FB.8070904@nortel.com \
--to=cfriesen@nortel.com \
--cc=csnook@redhat.com \
--cc=jengelh@computergmbh.de \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.com \
--cc=wjiang@resilience.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.