From: Gary Thomas <gary@mlbassoc.com>
To: John Newlin <jnewlin@rawbw.com>
Cc: ecos-discuss@sources.redhat.com
Subject: Re: [ECOS] Question on hal macro: HAL_DCACHE_INVALIDATE_ALL
Date: Thu, 06 May 2004 01:26:00 -0000 [thread overview]
Message-ID: <1083806794.5389.530.camel@hermes> (raw)
In-Reply-To: <20040505154924.X25440@shell.rawbw.com>
On Wed, 2004-05-05 at 16:50, John Newlin wrote:
> On architectures with writeback cache, should this do:
>
> writeback + invalidate
> or simply
> invalidate
If you need the data in the cache to make it to memory, then you need
to flush (writeback).
One normally invalidates the cache when it is assumed that some other
agent has [or is about to] change memory that would make the contents
of the cache incorrect. By invalidating the cache, new [read] accesses
will cause the contents to be refreshed from memory.
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
next prev parent reply other threads:[~2004-05-06 1:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-05 22:50 John Newlin
2004-05-06 1:26 ` Gary Thomas [this message]
2004-05-06 4:38 ` John Newlin
2004-05-06 12:06 ` Gary Thomas
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=1083806794.5389.530.camel@hermes \
--to=gary@mlbassoc.com \
--cc=ecos-discuss@sources.redhat.com \
--cc=jnewlin@rawbw.com \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).