-
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.
"Hyperthreading" on Athlon64 X2?
- Thread starter GRIdpOOL
- Start date
thanatos355
Senior member
they couldnt stop them from developing their own ht-esq design.
Did anyone actually read the article? All it means is that the Dual Athlon will enable the Hyperthreading bit on the chip. This way, when a program written with Hyperthreading support is run, it can take advantage of the 2nd core. It does NOT mean that AMD has included hyperthreading, they just want to take advantage of programs already designed for multithreading via Hyperthreading.
StormRider
Diamond Member
It seems like when HT enabled programs are run on an Intel chip, the two threads are run on the same CPU (but being executed at the same time in two different functional units on that same CPU).
If that same program is run on the Dual Core Athlon, then the two threads are run on the two cores at the same time.
But the thing is that the program itself cannot tell how the two threads are being run.
If that same program is run on the Dual Core Athlon, then the two threads are run on the two cores at the same time.
But the thing is that the program itself cannot tell how the two threads are being run.
DC Opteron
This was hijacked from another post. The dual-core Opteron shows hyper-threading.
This was hijacked from another post. The dual-core Opteron shows hyper-threading.
Aenslead
Golden Member
Thing is, people... we are speculating a tad bit.
See, HyperThreading was implemented out of necessity on P4 due to its HUGE pipeline and the incredible penalities involved in an empty/idle pipeline; AMD's pipeline is CONSIDERABLY smaller (hence the low latency it has shown since the XP days).
This bit is meant to make HT optimized apps use more of A64's resources, like a better use of the twin 1Mb caches.
Pretty smart from AMD: using existing technology that already has optimizations on important software. now that its fully functional.
And that is all I have to say about that.
See, HyperThreading was implemented out of necessity on P4 due to its HUGE pipeline and the incredible penalities involved in an empty/idle pipeline; AMD's pipeline is CONSIDERABLY smaller (hence the low latency it has shown since the XP days).
This bit is meant to make HT optimized apps use more of A64's resources, like a better use of the twin 1Mb caches.
Pretty smart from AMD: using existing technology that already has optimizations on important software. now that its fully functional.
And that is all I have to say about that.
If anybody want to now start using a vendor-neutral, marketing-free term for "Hyperthreading," you can say "simultaneous multi-threading" or "SMT."
Just FYI.
Just FYI.
I'm thinking that the difference you see is due to the dual core Athlons having 2 cores, with each core having a unique ID and being able to handle its own thread. In other words, neither core is hyperthreaded, but since you now have 2 cores to work with they can now handle hyperthreaded instructions like single core Intel HT chips can.
TRENDING THREADS
-
Discussion Zen 5 Speculation (EPYC Turin and Strix Point/Granite Ridge - Ryzen 9000)- Started by DisEnchantment
- Replies: 25K
-
Discussion Intel Meteor, Arrow, Lunar & Panther Lakes + WCL Discussion Threads
- Started by Tigerick
- Replies: 25K
-
Discussion Intel current and future Lakes & Rapids thread- Started by TheF34RChannel
- Replies: 24K
-
-
