• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

What's the L1 and L2 cache for Duron 850??

If I remember correctly, isn't the biggest difference between the Intel and AMD cache architectures that the AMD uses orthogonal L1 and L2 caches? That is, no replicated entries?
 
The normal term is "exlcusive" L2, but yes it L1 data is not duplicated in L2.

It would be kind of useless to have a smaller L2 cache than L1 if you had to duplicate the L1 in the L2 😉

The Duron has a total of 192kB of cache, the Celeron has 128kB (it has 32kB L1, 128kB L2, but it's insclusive L2 so 32kB of it is reserved to mirror the L1), the Thunderbird has 384kB, the P3 has 256kB (same story as the celeron with it's 32kB L1).

 
Noriaki: The academic articles I've read about those types of caches (dating back 20 years or so) seemed to use the term "orthogonal" so if the term has been deprecated since that time, my apologies.

Regarding the "uselessness" of the smaller L2 cache... not to nit-pick or anything, but there are several reasons why adding an L2 cache even though it is smaller than L1 would prove beneficial even if it is not "exclusive."

The main reason is that L2 caches are typically fully associative (or have much higher set associativity) than L1 caches and can therefore be used as "victim buffers" for conflict misses. It was once thought that conflict misses were somewhat rare due to the so-called pathological nature of accesses which would consistently produce them. However, as system memories become larger and used more heavily, conflict misses go up dramatically, especially in direct-mapped or two-way set associative caches.

However, in AMD's case you are quite correct, since a 64kb victim buffer would most likely be dramatic overkill. In the simulations that I have run, I see virtually no improvement in hit rate under most SPEC benchmarks when increasing the size of a victim buffer beyond 1kb.
 
In this corner Noriaki weighing in at....

In this conrer Kylef weighing in at....

J/K guys... want to subscribe to the thread...
 
Back
Top