So what is the offical answer why no Hyper Threading in Core2?

LeviathanZERO

Supreme [H]ardness
Joined
Dec 20, 2003
Messages
6,496
I dont understand this.
If there is something wrong with HT, why are they bringing it back with Nehalem?
I searched all over and cant find a straight answer. Evidently the Core2's have HT, but are disabled?? Is this right? How? and is there a way to enable/test it? Either way, if the capability is there, why is it disabled?
 
Core 2 processors do not and have never have had any HT support, not because HT is inherently a bad idea but because Intel were working on other things, and I guess that on a true multi-core CPU there are fewer benefits so it wasn't a priority. Remember that Core 2 is not directly based on P4/NetBurst. It's closer to Yonah.
 
http://www.overclockers.com.au/article.php?id=489587
"Another caveat is that Intel’s acclaimed “Hyperthreading” feature is for the time being disabled on all current Core 2 Duo processors. Hyperthreading allows running 2 threads per execution core, instead of normally only 1. Intel is mentioning HT capability in their Core 2 Duo documentation and we assume therefore that they will enable it for future versions to keep the product line attractive over its life cycle"

This is the same vague response I am finding everywhere. Nowhere claims that HT support does not exsist on Core2, just that its disabled, like mentioned above.

More recently Hyper-Threading has been criticised as being energy inefficient. For example, specialist low power CPU design company ARM has stated SMT can use up to 46% more power than dual CPU designs. Furthermore, they claim SMT increases cache thrashing by 42%, whereas dual core results in a 37% decrease[2]. These considerations are claimed to be the reason Intel dropped SMT from the following microarchitecture.

Again, not only does that not explain why SMT/HT is not available, it does not make any sense. (A power issue? whatever?)
 
Core 2 processors do not and have never have had any HT support, not because HT is inherently a bad idea but because Intel were working on other things, and I guess that on a true multi-core CPU there are fewer benefits so it wasn't a priority. Remember that Core 2 is not directly based on P4/NetBurst. It's closer to Yonah.

I agree
 
Umm the 2nd quote looks like you answered your own question. Cache thrashing & inefficiency.

Core 2 is already good enough & powerful enough with out HT.

Now when Nehalem comes out with a direct memory connection that cache thrashing will probably be a non-issue, so they may add it back in. Remember HT actually negatively affected some applications that were single threaded. HT really only helped make things more "fluid" (better multitasking) when stepping up from a single core CPU to a single core CPU with HT.

So there was no reason to add it when pretty much the full current line up of CPU's are all dual core with some quad cores. Even Celeron is getting a dual core version now.
 
Umm the 2nd quote looks like you answered your own question. Cache thrashing & inefficiency.

That was an unsourced quote, that I have not been able to find proof of. Sounds like speculation to me...

Now when Nehalem comes out with a direct memory connection that cache thrashing will probably be a non-issue, so they may add it back in. Remember HT actually negatively affected some applications that were single threaded. HT really only helped make things more "fluid" (better multitasking) when stepping up from a single core CPU to a single core CPU with HT.

Direct memory connection... is this refering to the off-chip memory controller? They are doing that with Nehalem, right?
 
Nehalem will have an ON-DIE memory controller (like AMD currently has) vs. all of Intel's current line up that uses the northbridge chipset as the memory controller.
 
Nehalem will have an ON-DIE memory controller (like AMD currently has) vs. all of Intel's current line up that uses the northbridge chipset as the memory controller.

Oh yeah yeah, thats what I meant. It came out backwards...
So what I was implying, is this the solution to the Cache Thrashing issue? Was/is that a problem with P4's?
 
The Netburst architecture had other problems as well. Stupid long pipe lines being one of them. Another is explained in an article by X-bit labs: http://www.xbitlabs.com/articles/cpu/display/replay.html

You have to remember that everyone knows HT isn't as good as having a multiple physical logic cores. Hence the real reason Intel does not use HT. Other features of the Core 2 architecture allow it to be a strong performer regardless of hat tricks like HT.

On the other hand, Intels Reverse-Hyperthreading looks really promising. Being able to split a single thread and execute it only more than one core at a time does have its merits.
 
I remember reading somewhere that Hyperthreading might eventually find its way back into Intel processors eventually. Then again, this was long ago and I don't remember the exact details.

Also, I thought the whole Reverse-Hyperthreading thing wasn't real?
 
I like to think anything is possible. If someone were to say 4 years ago that we would have octo-core cpu's capable of processing 16 threads at a time with a smaller die size than what a single current (2004) single core chip is by the year 2009, Im pretty sure you'd tell them they were mad.

Snap forward to 2008 and its not so maddening anymore now is it? I wouldnt be surprised if we saw RHT in either Intel's or AMD's next generation or the generation after Nehalem/Bulldozer.
 
HT will be back with nehalamamamam?(Sorry) but still I think it's only really useful in a server , desktops don't need 16threads/cpu =p
 
I remember reading somewhere that Hyperthreading might eventually find its way back into Intel processors eventually. Then again, this was long ago and I don't remember the exact details.

Also, I thought the whole Reverse-Hyperthreading thing wasn't real?

Nehalem.

But yeah, I'm not finding anything on the net about Reverse Hyper Threading. All I see is articles claiming that it, either does not exist, or AM2 chips have it. (yeah right)
 
Back
Top