From: Dan Malek <dan@embeddededge.com>
To: benh@kernel.crashing.org
Cc: acurtis@onz.com, Paul Mackerras <paulus@samba.org>,
linuxppc-dev@lists.linuxppc.org
Subject: Re: eieio rule-of-thumb?
Date: Thu, 23 May 2002 14:02:53 -0400 [thread overview]
Message-ID: <3CED2ECD.4090405@embeddededge.com> (raw)
In-Reply-To: 20020523184426.19045@mailhost.mipsys.com
benh@kernel.crashing.org wrote:
> Regarding eieio on uncached, Paul or Anton can tell you more about it,
> I think there is still a case where guarded doesn't prevent a load
> from moving accross a store.
Oh right....You get guarded to prevent out of order loads, and I just
get lucky that the uncached store doesn't cross the load.
> Regarding the bridge,...
OK. I thought that was a PCI master, memory controller thing, not
something that would happen from a CPU programmed I/O.
> I think it is on desktop CPUs, but again, here, Paul and Anton have more
> knowledge than I do.
Right. I know I found a couple of things we had to update for the 74xx
processors.
Thanks.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-23 18:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 4:43 eieio rule-of-thumb? Allen Curtis
2002-05-22 6:01 ` Paul Mackerras
2002-05-23 2:25 ` Allen Curtis
2002-05-23 4:26 ` Paul Mackerras
2002-05-23 13:38 ` Allen Curtis
2002-05-23 13:54 ` Dan Brennan
2002-05-23 14:42 ` Allen Curtis
2002-05-23 17:28 ` Dan Malek
2002-05-23 17:45 ` Chris Thomson
2002-05-23 19:02 ` Dan Malek
2002-05-23 22:36 ` Paul Mackerras
2002-05-23 18:44 ` benh
2002-05-23 18:02 ` Dan Malek [this message]
2002-05-23 22:58 ` Paul Mackerras
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=3CED2ECD.4090405@embeddededge.com \
--to=dan@embeddededge.com \
--cc=acurtis@onz.com \
--cc=benh@kernel.crashing.org \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=paulus@samba.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).