Chris Jeppesen <pov### [at] kwansystemsorg> wrote:
> Hyperthreading addresses this by adding another decoder, visible to the 
> OS and programs as another set of registers and instruction pointer. It 
> really does look like another processor. If one decoder is running a 
> series of floating point instructions, another program running on the 
> other decoder could run a bunch of integer instructions, keep the 
> integer units busy, use the chip more efficiently, and crank out twice 
> as much work in the same amount of time.

  So in theory if a program needs to perform floating point calculations
and (independent) integer calculations, it should run those calculations
in separate threads for maximum speed advantage in a P4?

-- 
plane{-x+y,-1pigment{bozo color_map{[0rgb x][1rgb x+y]}turbulence 1}}
sphere{0,2pigment{rgbt 1}interior{media{emission 1density{spherical
density_map{[0rgb 0][.5rgb<1,.5>][1rgb 1]}turbulence.9}}}scale
<1,1,3>hollow}text{ttf"timrom""Warp".1,0translate<-1,-.1,2>}//  - Warp -

Post a reply to this message