From: Jerry Jiang <wjiang@resilience.com>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: why are some atomic_t's not volatile, while most are?
Date: Mon, 6 Aug 2007 12:35:51 +0800 [thread overview]
Message-ID: <20070806123551.a6c3c154.wjiang@resilience.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0707010847370.22564@localhost.localdomain>
Is there some feedback on this point ?
Thank you
./Jerry
On Sun, 1 Jul 2007 08:49:37 -0400 (EDT)
"Robert P. J. Day" <rpjday@mindspring.com> wrote:
>
> prompted by the earlier post on "volatile"s, is there a reason that
> most atomic_t typedefs use volatile int's, while the rest don't?
>
> $ grep "typedef.*struct" $(find . -name atomic.h)
> ./include/asm-v850/atomic.h:typedef struct { int counter; } atomic_t;
> ./include/asm-mips/atomic.h:typedef struct { volatile int counter; } atomic_t;
> ./include/asm-mips/atomic.h:typedef struct { volatile long counter; } atomic64_t;
> ...
>
> etc, etc. just curious.
>
> rday
> --
> ========================================================================
> Robert P. J. Day
> Linux Consulting, Training and Annoying Kernel Pedantry
> Waterloo, Ontario, CANADA
>
> http://fsdev.net/wiki/index.php?title=Main_Page
> ========================================================================
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
>
next prev parent reply other threads:[~2007-08-06 4:57 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 [this message]
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
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=20070806123551.a6c3c154.wjiang@resilience.com \
--to=wjiang@resilience.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rpjday@mindspring.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).