Silicon Investor (SI) -- The First Internet Community

STOCKTALK

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.

Politics : Formerly About Advanced Micro Devices -- Ignore unavailable to you. Want to Upgrade?

To: Scumbria who wrote (101297)	3/31/2000 4:29:00 PM
From: Joe NYC	Read Replies (1) \| Respond to of 1573092

Scumbria, Thanks for explanation of the victim cache. I don't think I understand it yet, but I am sure there will be more info on it if AMD uses it. Is Coppermine L2 a victim cache? Answering your other question, there is no reason why you have to delay DRAM access pending an L2 lookup. (Although you may want to.) Are you saying that it's possible to start access of the main memory at the same time L2 cache lookup starts, and not wait if there was a cache hit or miss? I guess it makes sense, but wouldn't the main memory be overloaded with requests constantly, even though it may turn out that the access was not really needed, because the data was in L2? I don't think this would be a good idea for multiprocessor systems, or systems where graphics subsystem accesses main memory a lot. Do you know current CPUs work in this regard? Joe