News for hackers. Stuff that matters.
Re:It's all about the cores. Why AMD doesn't use HyperThreading by Confusion on Friday January 22, 2010 @01:56AM (#1069253)
The second two are both on windows, which until windows 7 was unable to schedule hyperthreading correctly.

Hyperthreading doesn't require any special OS support. As the wikipedia page states:

  This technology is transparent to operating systems and 
  programs. All that is required to take advantage of hyper- 
  threading is symmetric multiprocessing (SMP) support in
  the operating system, as the logical processors appear as
  standard separate processors.
Re:It's all about the cores. Why AMD doesn't use HyperThreading by neilc on Friday January 22, 2010 @02:54AM (#1069309)
No extensive OS support is required to utilize basic SMT, true -- but the scheduler needs to be aware of SMT to do remotely-intelligent scheduling. As a trivial example, if you have 2 runnable processes, 4 logical cores, and 2 physical cores, it obviously makes sense to schedule one process on each physical core. (In fact, the Wikipedia article says this, in the very next paragraph after the one you quoted.)
Re:It's all about the cores. Why AMD doesn't use HyperThreading by Confusion on Friday January 22, 2010 @03:57AM (#1069354)
True, but then the point the original article makes kicks in: that's a relatively poor way of doing things. Originally HT was supposed to be transparent. Then it turned out the abstraction wasn't quite as good as they hoped and OS level support was needed. That adds a lot of complexity and possibilities for mistakes. At that point, they should have dropped HT and go for actual cores instead.
Re:It's all about the cores. Why AMD doesn't use HyperThreading by neilc on Friday January 22, 2010 @11:24AM (#1069924)
Originally HT was supposed to be transparent.

According to whom? I don't think anyone with a clue would have suggested that. If you care about writing high-performance code, you care about the behavior of your processor. Obviously, multiplexing the execution of two program threads onto a single physical core is going to affect performance, whether in the form of scheduling differences, caching effects, etc.

they should have dropped HT and go for actual cores instead.

Well, you can do both, of course. If HT gets you better utilization of a single core, then fair enough. The question is really whether the transistors/power you burn on HT would be better spent on additional cores (or bigger caches, etc.).