SI
SI
discoversearch

We've detected that you're using an ad content blocking browser plug-in or feature. Ads provide a critical source of revenue to the continued operation of Silicon Investor.  We ask that you disable ad blocking while on Silicon Investor in the best interests of our community.  If you are not using an ad blocker but are still receiving this message, make sure your browser's tracking protection is set to the 'standard' level.
Technology Stocks : Advanced Micro Devices - Moderated (AMD)
AMD 259.65+2.3%Jan 23 9:30 AM EST

 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext  
To: Scumbria who wrote (33443)3/25/2001 10:29:29 PM
From: Joe NYCRead Replies (1) of 275872
 
Scumbria,

Prefetching into the L2 could produce significant gains for Linpack-type code, so it is possible that some benchmarks will see 50% improvement (if they actually did that.)

But someone (I can't recall who) posted that all of the data from RAM goes to L1 in Athlon, not L2, and it only gets to L2 when it gets evicted from L1. Is this a correct (at least in the ballpark) representation of how Athlon works? if it is, it seems to preclude prefetching to L2.

Joe
Report TOU ViolationShare This Post
 Public ReplyPrvt ReplyMark as Last ReadFilePrevious 10Next 10PreviousNext