From: jamie@shareable.org (Jamie Lokier)
To: linux-arm-kernel@lists.infradead.org
Subject: ARM caches variants.
Date: Tue, 23 Mar 2010 23:39:52 +0000 [thread overview]
Message-ID: <20100323233952.GF20130@shareable.org> (raw)
In-Reply-To: <1269355564.13209.56.camel@e102109-lin.cambridge.arm.com>
Catalin Marinas wrote:
> > > Even if you have a 1-way associative cache (some processors allow the
> > > disabling of the other 3 ways if you want to try), the tag stored with
> > > the cache line is different between different VAs on a VIVT cache.
> > >
> > > So with two different VAs mapping the same PA, if a VA0 access allocates
> > > the cache line and VA1 would find the same cache line via the index
> > > calculation, it would get a cache miss because the tags for VA0 and VA1
> > > do not match.
> >
> > But if we assume that it evicts the contents of VA0 and allocates the
> > cache for VA1 when VA1 is accessed, the system would just work.
>
> That's correct, for this particular case it should work (though I think
> fully associative caches are not that common).
I think you might have meant 1-way caches, or running then with 1-way,
is never done. But if you did have 1-way, then it might work. :-)
With 2-way or more, all bets are off because you don't know which way
will be evicted.
-- Jamie
next prev parent reply other threads:[~2010-03-23 23:39 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-23 12:39 ARM caches variants Gilles Chanteperdrix
2010-03-23 12:53 ` Catalin Marinas
2010-03-23 13:15 ` Gilles Chanteperdrix
2010-03-23 13:42 ` Catalin Marinas
2010-03-23 13:59 ` Gilles Chanteperdrix
2010-03-23 14:33 ` Catalin Marinas
2010-03-23 14:39 ` Gilles Chanteperdrix
2010-03-23 14:46 ` Catalin Marinas
2010-03-23 14:47 ` Catalin Marinas
2010-03-23 14:49 ` Gilles Chanteperdrix
2010-03-23 23:39 ` Jamie Lokier [this message]
2010-03-24 9:33 ` Catalin Marinas
2010-03-23 23:49 ` Jamie Lokier
2010-03-24 9:42 ` Catalin Marinas
2010-03-26 5:45 ` Jamie Lokier
2010-03-26 13:23 ` Catalin Marinas
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=20100323233952.GF20130@shareable.org \
--to=jamie@shareable.org \
--cc=linux-arm-kernel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.