From: NIIBE Yutaka <gniibe@fsij.org>
To: Carlos O'Donell <carlos@systemhalted.org>
Cc: Kyle McMartin <kyle@mcmartin.ca>,
debian-hppa@lists.debian.org,
linux-parisc <linux-parisc@vger.kernel.org>,
Helge Deller <deller@gmx.de>
Subject: Re: CAS (lws_compare_and_swap32)
Date: Thu, 01 Apr 2010 10:57:56 +0900 [thread overview]
Message-ID: <4BB3FDA4.4070706@fsij.org> (raw)
In-Reply-To: <4BB3F40A.7020401@fsij.org>
NIIBE Yutaka wrote:
> Today, I have a next question. Is there any cache alias problem here?
> Should we invalidate the cache line before "load" and flush the cache
> line after "store"?
Sorry, I was confused. We are talking threads which shares memory
context (space identifier), so, my concern is not relevant.
--
next prev parent reply other threads:[~2010-04-01 1:57 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <4BB0B2C8.8000302@fsij.org>
[not found] ` <119aab441003290913x6cb925b9v66b44a14c31393cb@mail.gmail.com>
2010-03-29 19:31 ` CAS (lws_compare_and_swap32) Carlos O'Donell
2010-03-29 20:07 ` Kyle McMartin
2010-03-30 20:38 ` Carlos O'Donell
2010-03-30 21:36 ` Kyle McMartin
2010-04-01 1:16 ` NIIBE Yutaka
2010-04-01 1:57 ` NIIBE Yutaka [this message]
2010-03-30 1:54 ` John David Anglin
2010-03-30 2:18 ` Carlos O'Donell
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=4BB3FDA4.4070706@fsij.org \
--to=gniibe@fsij.org \
--cc=carlos@systemhalted.org \
--cc=debian-hppa@lists.debian.org \
--cc=deller@gmx.de \
--cc=kyle@mcmartin.ca \
--cc=linux-parisc@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