You guys will be surprised after seeing the cache hierachy and size of L2 in Nehalem. It shrinks.
Intel, AMD what next?, 2008 Roadmap.....
Intel, AMD what next?, 2008 Roadmap.....
|
|
May 7 2007, 10:46 AM
Return to original view | Post
#1
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
4,060 posts Joined: Jan 2003 From: Penang / PJ |
You guys will be surprised after seeing the cache hierachy and size of L2 in Nehalem. It shrinks.
|
|
|
May 7 2007, 11:27 AM
Return to original view | Post
#2
|
![]() ![]() ![]() ![]() ![]() ![]() ![]()
Senior Member
4,060 posts Joined: Jan 2003 From: Penang / PJ |
QUOTE(afosz @ May 7 2007, 10:46 AM) What does cache do or help anyway? I mean like it is hard for me to explain to my bro that A64 X2 3600+ with 256x2 is different with A64 3000+ with 512K. Although 256x2 is 512 mathematically 2x256K is 256K L2 per core. In A64 3000+, the only core has dedicated 512K L2.So higher cache is better or lower is better? Or just ignore about the cache thing? In single threaded software, 3000+ might work faster due to larger L2. QUOTE(ikanayam @ May 7 2007, 11:01 AM) Hm... interesting, if it has a L3, then it makes sense that they will shrink the L2 and make it faster, or possibly even make it non unified L2 for latency/bandwidth & a large unified L3 for coverage. This sounds like Barcelona cache hierachy I've read that Barcelona design the cache this way to increase performance in Virtualization, instead of going for shared L2. Since we are heading towards VT world pretty soon, you can roughly guess the design trend. |
| Change to: | 0.0134sec
0.88
6 queries
GZIP Disabled
Time is now: 21st December 2025 - 06:15 AM |