From: Segher Boessenkool <segher@koffie.nl>
To: Eugene Surovegin <ebs@ebshome.net>
Cc: linuxppc-embedded@lists.linuxppc.org
Subject: Re: Possible bug in flush_dcache_all on 440GP
Date: Wed, 26 Feb 2003 16:39:05 +0100 [thread overview]
Message-ID: <3E5CDF99.3080708@koffie.nl> (raw)
In-Reply-To: <5.1.0.14.2.20030225185928.00ac3198@mail.zultys.com>
Eugene Surovegin wrote:
> I believe there is a bug in flush_dcache_all implementation for not cache
> coherent processors.
>
> This function uses simple algorithm to force dcache flush by reading
> "enough" data to completely reload the cache:
[snip]
So you're saying it doesn't use an LRU replacement algorithm
but a FIFO one?
> 1) Use twice as much memory than the cache size. This solution is not very
> efficient,
> but it doesn't add _any_ special requirements to the memory we use to
> reload the
> cache with.
That doesn't work correctly, either, in that case. You have to
read the same memory region twice, not read a twice as big region
once.
Segher
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-02-26 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-26 4:08 Possible bug in flush_dcache_all on 440GP Eugene Surovegin
2003-02-26 15:39 ` Segher Boessenkool [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-02-28 15:00 Ralph Blach
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=3E5CDF99.3080708@koffie.nl \
--to=segher@koffie.nl \
--cc=ebs@ebshome.net \
--cc=linuxppc-embedded@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).