linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Woodhouse <dwmw2@infradead.org>
To: "David S. Miller" <davem@redhat.com>
Cc: Chris Wedgwood <cw@f00f.org>,
	Jeff Garzik <jgarzik@mandrakesoft.com>,
	bjornw@axis.com, linux-kernel@vger.kernel.org,
	linux-mtd@lists.infradead.org
Subject: Re: Missing cache flush.
Date: Tue, 05 Jun 2001 10:05:35 +0100	[thread overview]
Message-ID: <25831.991731935@redhat.com> (raw)
In-Reply-To: <15132.40298.80954.434805@pizda.ninka.net>
In-Reply-To: <15132.40298.80954.434805@pizda.ninka.net>  <15132.22933.859130.119059@pizda.ninka.net> <13942.991696607@redhat.com> <3B1C1872.8D8F1529@mandrakesoft.com> <15132.15829.322534.88410@pizda.ninka.net> <20010605155550.C22741@metastasis.f00f.org> <25587.991730769@redhat.com>


davem@redhat.com said:
>  One way to do this, (even portably :-) is via displacement flushes.
> Linus mentioned this.

> Basically if you know the L2 cache size and the assosciativity you can
> do this as long as you can get a "2 * L2 cache size * assosciativity"
> piece of contiguous physical memory.  When you need this "simon says"
> flush, you basically read this physical memory span and this will
> guarentee that all dirty data has exited the L2 cache. 

Fine. So it should be possible to do it on all architectures with 
physically-indexed caches - that's good. Architectures with 
virtually-indexed caches are going to have explicit cache management 
functionality anyway, presumably :)

Obviously the algorithm you describe should not be implemented in
arch-independent drivers. It should be in include/asm-*, for those
architectures which _can't_ do it with a single cache management instruction
(or loop of same).

What shall we call this function? The intuitive "flush_dcache_range" appears
to have already been taken.

--
dwmw2



  reply	other threads:[~2001-06-05  9:06 UTC|newest]

Thread overview: 34+ 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:03 ` David S. Miller
2001-06-05  3:55   ` Chris Wedgwood
2001-06-05  5:28     ` Linus Torvalds
2001-06-05  6:49       ` Alan Cox
2001-06-05  8:29       ` Ingo Molnar
2001-06-05 15:10         ` Ralf Baechle
2001-06-05  8:46     ` David Woodhouse
2001-06-05  9:05       ` David Woodhouse [this message]
2001-06-05 12:42         ` David Woodhouse
2001-06-05 12:52           ` David Woodhouse
2001-06-05 12:48         ` David S. Miller
2001-06-06  8:32           ` Albert D. Cahalan
2001-06-06 19:48         ` Pavel Machek
2001-06-05  9:11       ` David S. Miller
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  8:50     ` David S. Miller
2001-06-05 17:01       ` Jamie Lokier
2001-06-05 23:24         ` Chris Wedgwood
2001-06-06  8:43           ` James Sutherland
2001-06-05  4:01   ` David S. Miller
2001-06-05  2:04 ` David S. Miller
2001-06-05  9:17 ` Bjorn Wesen
2001-06-05 12:57   ` Chris Wedgwood
2001-06-05 15:17     ` Ralf Baechle
2001-06-05 17:41     ` Daniel Phillips
2001-06-05 14:22   ` Vipin Malik
2001-06-05 14:40     ` Chris Wedgwood

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=25831.991731935@redhat.com \
    --to=dwmw2@infradead.org \
    --cc=bjornw@axis.com \
    --cc=cw@f00f.org \
    --cc=davem@redhat.com \
    --cc=jgarzik@mandrakesoft.com \
    --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;
as well as URLs for NNTP newsgroup(s).