From: chris@basementcode.com (Christopher Harvey)
To: kernelnewbies@lists.kernelnewbies.org
Subject: IRQs and memory consistency
Date: Wed, 11 Apr 2012 15:14:44 -0500 [thread overview]
Message-ID: <a6554b231600d032628d59f975476e13@basementcode.com> (raw)
In-Reply-To: <CAKk8isrng+8-o-B07H7UFMfPDyQ7d1s67Q5XcJ2sQje6wy2Btg@mail.gmail.com>
On 11.04.2012 10:35, Wink Saville wrote:
> Do you have a read barrier in the IRQ?
Ah, no I don't.
> See "SMP BARRIER PAIRING" in:
>
> http://www.kernel.org/doc/Documentation/memory-barriers.txt [3]
I saw that but only skimmed it.
I'll let the mailing list know if it worked when I get a chance to try
it.
thanks,
-Chris
next prev parent reply other threads:[~2012-04-11 20:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-10 20:22 IRQs and memory consistency Christopher Harvey
2012-04-11 0:58 ` Wink Saville
2012-04-11 11:59 ` Christopher Harvey
2012-04-11 15:35 ` Wink Saville
2012-04-11 20:14 ` Christopher Harvey [this message]
2012-04-11 3:18 ` Mulyadi Santosa
2012-04-11 11:53 ` Christopher Harvey
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=a6554b231600d032628d59f975476e13@basementcode.com \
--to=chris@basementcode.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).