linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jamie Lokier <lk@tantalophile.demon.co.uk>
To: "David S. Miller" <davem@redhat.com>
Cc: David Woodhouse <dwmw2@infradead.org>,
	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, 5 Jun 2001 19:01:28 +0200	[thread overview]
Message-ID: <20010605190128.A12204@pcep-jamie.cern.ch> (raw)
In-Reply-To: <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> <15132.40298.80954.434805@pizda.ninka.net>
In-Reply-To: <15132.40298.80954.434805@pizda.ninka.net>; from davem@redhat.com on Tue, Jun 05, 2001 at 01:50:50AM -0700

David S. Miller wrote:
> 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.

Whether this works depends on the cache line replacement policy.  It
will always work with LRU, for example, and probably everything else
that exists.  But it is not guaranteed, is it?

-- Jamie

  reply	other threads:[~2001-06-05 17:02 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
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 [this message]
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=20010605190128.A12204@pcep-jamie.cern.ch \
    --to=lk@tantalophile.demon.co.uk \
    --cc=bjornw@axis.com \
    --cc=cw@f00f.org \
    --cc=davem@redhat.com \
    --cc=dwmw2@infradead.org \
    --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).