From: mulyadi.santosa@gmail.com (Mulyadi Santosa)
To: kernelnewbies@lists.kernelnewbies.org
Subject: memory barrier in UP
Date: Tue, 13 Dec 2011 11:19:59 +0700 [thread overview]
Message-ID: <CAGdaadb8-bU5aKdtBzwZaxQmqw+yDe4ypVFddkf8Ee-X__1+Sw@mail.gmail.com> (raw)
In-Reply-To: <CAKRO8zLJ-sy9=05USO0Gg=XkG92t+CvfirA5mXG7C-eU6Oq6qg@mail.gmail.com>
Hi Subin....
On Tue, Dec 13, 2011 at 01:57, subin gangadharan
<subingangadharan@gmail.com> wrote:
> Hi Mulyadi,
>
> Thanks for the answer.
You welcome...I just shared what I know :)
> In that case (ALPHA), is compiler barrier sufficient enough to prevent
> the re ordering done by the processor.
> What I was thinking,compiler barrier is to instruct the compiler to
> not do any re ordering.
Again this is architecture problem. I am not sure about Alpha, since I
only know about one compiler barrier that is "volatile". What I guess
is that in Alpha, it could be something else....maybe it is assembly
instruction like "lock" or something.
I remember there's an old Linuxjournal article that explains about it.
So to avoid further misunderstandings that I might bring, please
kindly read this article:
http://www.linuxjournal.com/article/8212
Hope that helps...
--
regards,
Mulyadi Santosa
Freelance Linux trainer and consultant
blog: the-hydra.blogspot.com
training: mulyaditraining.blogspot.com
prev parent reply other threads:[~2011-12-13 4:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-11 18:11 memory barrier in UP subin gangadharan
2011-12-12 17:16 ` Mulyadi Santosa
2011-12-12 18:57 ` subin gangadharan
2011-12-13 4:19 ` Mulyadi Santosa [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=CAGdaadb8-bU5aKdtBzwZaxQmqw+yDe4ypVFddkf8Ee-X__1+Sw@mail.gmail.com \
--to=mulyadi.santosa@gmail.com \
--cc=kernelnewbies@lists.kernelnewbies.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;
as well as URLs for NNTP newsgroup(s).