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.

Technology Stocks : Intel Corporation (INTC) -- Ignore unavailable to you. Want to Upgrade?

To: rkral who wrote (177943)	5/12/2004 11:01:31 AM
From: Tenchusatsu	Respond to of 186894

Ron, But doesn't the updating core need to wait until the read operation is complete .. in order to avoid a corrupted read? Conflicts on the bus are handled via bus protocol, either with retry mechanisms or proper queuing. It will be handled similarly on the processor in a dual-core CPU, but the difference is that the latency of conflict resolution will be much lower. In terms of time wasted waiting, how does that differ from 'bus contention' waits? "Bus contention" is avoided using a round-robin arbitration scheme on the bus. I doubt there would be a "bus" inside a dual-core CPU, so bus contention would be a non-issue, just like it's a non-issue with HyperTransport. Tenchusatsu