From: Vipin Malik <vipin.malik@daniel.com>
To: Bjorn Wesen <bjorn.wesen@axis.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
linux-kernel@vger.kernel.org, linux-mtd@lists.infradead.org
Subject: Re: Missing cache flush.
Date: Tue, 05 Jun 2001 09:22:13 -0500 [thread overview]
Message-ID: <3B1CEB15.FFB2EADB@daniel.com> (raw)
In-Reply-To: Pine.LNX.4.21.0106051105110.1078-100000@godzilla.axis.se
Bjorn Wesen wrote:
>
> I'd agree that to be really certain, a "flush_dcache()" function
> should be implemented and used when an erase finishes. Like David Miller
> wrote somewhere in the thread, one way is to use your knowledge of the
> arch's cache and do suitable dummy accesses to flush it, if there is no
> explicit command to do it. But that's just up to the arch coders..
>
Here's a stupid question: Are there any processors out there that have a cache
but no explicit cache-flush command?
If not (i.e. no such "funny" processors), then what's wrong with the arch
dependent include through a define to execute the
arch specific asm command?
The only issue (besides knowing the cache size at run time) that I can think
about the "dummy" eviction scheme is that you now need to xfer potentially 3
times the cache
size data to and from memory:
#1. The dummy read
#2. The eviction of the entire cache data being evicted
#3. The refilling of the cache with good data again, as the dummy data cannot
really represent anything useful.
Is my thinking here completely non coherent with others? ;)
Vipin
next prev parent reply other threads:[~2001-06-05 14:16 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-06-04 23:16 Missing cache flush David Woodhouse
2001-06-04 23:23 ` Jeff Garzik
2001-06-04 23:29 ` David Woodhouse
2001-06-05 2:04 ` David S. Miller
2001-06-05 2:03 ` David S. Miller
[not found] ` <20010605155550.C22741@metastasis.f00f.org>
2001-06-05 4:01 ` David S. Miller
2001-06-05 8:46 ` David Woodhouse
2001-06-05 8:50 ` David S. Miller
2001-06-05 9:05 ` David Woodhouse
2001-06-05 9:11 ` David S. Miller
2001-06-05 12:42 ` David Woodhouse
2001-06-05 12:48 ` David S. Miller
2001-06-05 12:52 ` David Woodhouse
2001-06-06 8:32 ` Albert D. Cahalan
2001-06-06 19:48 ` Pavel Machek
2001-06-05 17:01 ` Jamie Lokier
2001-06-05 9:29 ` kira brown
2001-06-05 17:16 ` Alan Cox
2001-06-06 19:44 ` Earyly Cyrix CPUs was " Pavel Machek
2001-06-08 16:00 ` Alan Cox
2001-06-05 9:43 ` Johan Adolfsson
2001-06-05 9:17 ` Bjorn Wesen
2001-06-05 14:22 ` Vipin Malik [this message]
[not found] ` <20010606005703.A23758@metastasis.f00f.org>
2001-06-05 15:17 ` Ralf Baechle
[not found] <20010606112419.A24800@metastasis.f00f.org>
2001-06-06 8:43 ` James Sutherland
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=3B1CEB15.FFB2EADB@daniel.com \
--to=vipin.malik@daniel.com \
--cc=bjorn.wesen@axis.com \
--cc=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mtd@lists.infradead.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