View Full Version : Re: Entering the BIOS on XP
Bob Cain
November 11th 03, 11:20 PM
pH wrote:
>
> Steve Jorgensen posted this very good link... back in January:
>
> http://arstechnica.com/paedia/h/hyperthreading/hyperthreading-1.html
>
> Very digestable info, and *well* worth reading (imo, at least).
>
Thanks, Jeff. Excellent article!
Bob
--
"Things should be described as simply as possible, but no
simpler."
A. Einstein
BrightBoy
November 12th 03, 01:18 PM
I'm pretty sure only motherboards with the Intel 875 chip set will have
hyper-threading capabilities.
A few motherboard companies figured out how to "un-officially" do it with
the Intel 865 chip set.
There's more information about this at the usual places:
www.tomshardware.com
www.anandtech.com
www.motherboads.org
Jeff
Roger W. Norman
November 13th 03, 01:27 PM
"Bob Cain" > wrote in message
...
> Both? You stated four. :-)
Both counts being hyperthreading's access through bios and the cpu it was
introduced on. Actually, the P4 3.06 gHz chip is the P4 that it was
introduced on, but it was also introduced on the Xeon 2.2 gHz AND became
part of the chip on some slower P4s, so I assume it was already built into
the production process, so I was kinda right and kinda wrong. As far as the
statements about hyperthreading, I feel ok about them. And while I know
that hyperthreading was a bios selection in the early Xeons, I'm not so sure
about the P4s, but I will bow to greater knowledge.
I pretty much gave up on constantly keeping up with CPUs when I got a system
together that would do most anything I asked of it. I somewhat got tired of
having arrows in my back all the time by being a first adopter and beta
tester. Now I get to work on music, not on computers! <g>
--
Roger W. Norman
SirMusic Studio
Purchase your copy of the Fifth of RAP CD set at www.recaudiopro.net.
See how far $20 really goes.
>
> As I understand hyperthreading, the processor is dual
> i-stream which means it follows two instruction counters at
> the same time and keeps their effects separate within the
> processor. Utilization would be a function of the
> dispatcher in the OS rather than code embedded in the
> application. Anybody know otherwise?
>
>
> Bob
> --
>
> "Things should be described as simply as possible, but no
> simpler."
>
> A. Einstein
vBulletin® v3.6.4, Copyright ©2000-2025, Jelsoft Enterprises Ltd.