From: Larry McVoy <lm@bitmover.com>
To: David Lang <david.lang@digitalinsight.com>
Cc: Larry McVoy <lm@bitmover.com>, Stevie O <stevie@qrpff.net>,
linux-kernel@vger.kernel.org
Subject: Re: "Colo[u]rs"
Date: Sun, 9 Dec 2001 23:51:26 -0800 [thread overview]
Message-ID: <20011209235126.J25754@work.bitmover.com> (raw)
In-Reply-To: <20011209232859.I25754@work.bitmover.com> <Pine.LNX.4.40.0112092319020.4915-100000@dlang.diginsite.com>
In-Reply-To: <Pine.LNX.4.40.0112092319020.4915-100000@dlang.diginsite.com>; from david.lang@digitalinsight.com on Sun, Dec 09, 2001 at 11:21:23PM -0800
On Sun, Dec 09, 2001 at 11:21:23PM -0800, David Lang wrote:
> Larry, I thought that direct mapped caches had full mapping from any cache
> address to any physical address while the N-way mapped caches were more
> limited. modern caches are N-way instead of direct mapped becouse it's
> much more expensive (transistor count wise) for the direct mapped
> approach.
That's not correct unless they changed terminology without asking my
permission :-) A direct mapped cache is the same as a 1-way set
associative cache. It means each cache line has one and only one
place it can be in the cache. It also means there is only one set
of tag comparitors, which makes it cheaper and easier to build.
> If I'm mistaken about my termonology (very possible :-) what is the term
> for what I am refering to as direct mapped?
Fully associative cache, I believe.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2001-12-10 7:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200112100656.fBA6ukA14374@www.hockin.org>
2001-12-10 7:07 ` "Colo[u]rs" Stevie O
2001-12-10 7:26 ` "Colo[u]rs" Robert Love
2001-12-10 7:36 ` "Colo[u]rs" Robert Love
2001-12-10 7:28 ` "Colo[u]rs" Larry McVoy
2001-12-10 7:21 ` "Colo[u]rs" David Lang
2001-12-10 7:51 ` Larry McVoy [this message]
2001-12-10 7:30 ` "Colo[u]rs" David Lang
2001-12-10 7:33 ` "Colo[u]rs" Stevie O
2001-12-10 8:37 ` "Colo[u]rs" Alan Cox
2001-12-10 8:00 ` "Colo[u]rs" Stevie O
2001-12-10 8:13 ` "Colo[u]rs" Robert Love
2001-12-10 12:22 ` "Colo[u]rs" ncw
2001-12-10 17:52 ` "Colo[u]rs" 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=20011209235126.J25754@work.bitmover.com \
--to=lm@bitmover.com \
--cc=david.lang@digitalinsight.com \
--cc=linux-kernel@vger.kernel.org \
--cc=stevie@qrpff.net \
/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