• 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.

Dual Core AMD Opteron. First screenshot!

If you read the article, the so called HT is NOT the same as Intel's Hyper Threading. AMD chose to set the HT bit in the A64 so that it could take advantage of software that was writen for HT enabled processors. This means when you run an HT application, it will use both of the A64s cores to run. This is NOT the same as HT in the INtel sense.
 
Originally posted by: Brian23
If you read the article, the so called HT is NOT the same as Intel's Hyper Threading. AMD chose to set the HT bit in the A64 so that it could take advantage of software that was writen for HT enabled processors. This means when you run an HT application, it will use both of the A64s cores to run. This is NOT the same as HT in the INtel sense.


Isn't HT in "intel speak" Hyper-Threading while in "AMDeese" it's Hyper Transport?

One refers to how it multitasks the other how it handles the bus?
 
Isn't HT in "intel speak" Hyper-Threading while in "AMDeese" it's Hyper Transport?

One refers to how it multitasks the other how it handles the bus?
Yes BUT

Look at the screenshot

Hyper-threading = Yes

 
Originally posted by: Griffinhart
Originally posted by: Brian23
If you read the article, the so called HT is NOT the same as Intel's Hyper Threading. AMD chose to set the HT bit in the A64 so that it could take advantage of software that was writen for HT enabled processors. This means when you run an HT application, it will use both of the A64s cores to run. This is NOT the same as HT in the INtel sense.


Isn't HT in "intel speak" Hyper-Threading while in "AMDeese" it's Hyper Transport?

One refers to how it multitasks the other how it handles the bus?

What you're saying is true, but in this case, we're talking about hyperthreading for AMD.
 
Isn't the bit a way to have hyperthreading aware software utilize the 2nd core, and not actually hyperthreading though?
 
Isn't the bit a way to have hyperthreading aware software utilize the 2nd core, and not actually hyperthreading though?

Not quite. It's probably just to tell the OS that the you get 2 CPUs on one chip. E.g. Workstation editions of windows will only recognise 2 physical CPUs (so that you have to buy Windows Server if you have quad CPUs). However, WinXP is able to recognise the 'hyper-threading' bit, which tells it to only count half the CPUs it detects against it's licence.

Win2k doesn't detect hyperthreading - which means that it will detect a dual Xeon with HT machine as having 4 CPUs. If you have Win2k pro, it will only activate 2 CPUs at boot-up, which corresponds to one CPU and a virtual HT CPU. The other CPU will be disabled.

XP Pro realises that only 2 of those CPUs are actually real CPUs - so will activate them all.
 
Back
Top