From: "Allen Curtis" <acurtis@onz.com>
To: <linuxppc-dev@lists.linuxppc.org>
Subject: eieio rule-of-thumb?
Date: Tue, 21 May 2002 21:43:37 -0700 [thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFMEGJDHAA.acurtis@onz.com> (raw)
I was wondering if anyone had a rule for the use of eieio or sync
instructions? After reviewing some of the newer code, it appears that eieio
is used fairly often (at least in some code), sync is hardly ever used. Is a
consideration for use whether data is being manipulated on different buses?
(that would be my assumption) I would assume that operations on the same bus
would occur in the proper sequence.
TIA
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2002-05-22 4:43 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-22 4:43 Allen Curtis [this message]
2002-05-22 6:01 ` eieio rule-of-thumb? 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
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=NCBBIINEHIPFGJPLBEIFMEGJDHAA.acurtis@onz.com \
--to=acurtis@onz.com \
--cc=linuxppc-dev@lists.linuxppc.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).