Read it for yourself...

[ 05-22-2005, 05:27 PM: Message edited by: Hivetyrant ]

I'm sure it has just increased considerably now he has written his documentation. :rolleyes:

Any chance of getting this in plain English?

Hyper threading?...Sounds like a weaver on speed. What's hyper threading?...What's RSA?

I thought it was going to be a fancy name for spamming.

LOL! Not everything can be explained in "plain english" without the necessary background. Actually I've never bothered to read up on how hyper threading works, but just to intro the topic: you know what a process is right? Open up windows task manager and you have a list of running processes, like each application usually has its own process - this is an entity that has its own memory space etc. i.e. memory used by one process cannot be used by any other etc. A thread is like a process within a process - for example microsoft word will need several threads seemingly running at the same time: e.g. one thread will monitor keyboard input, another mouse input, while another handles updating the screen - however threads may all share the same memory space, that's why they're able to communicate with each other, they're all within the MS word process.

Of course, since the processor can only do one thing at a time, what is happening is that it is processing instructions from one thread then very quickly switching to instructions from another thread over and over again. In hyperthreading from what I understand with the very small bit I've read, what happens is that instructions from different threads can be in the pipeline at once.

Now you prob don't know what pipelining is (*digs in memory*). Basically when you have an instruction for a processor, say something like "do contents of register 1 + contents of register 2 (registers are just bits of memory) and give me the answer" there are many stages. 1. the instruction has to be fetched from cache 2. it has to be decoded into machine language. 3. fetch the contents of registers 1 & 2, 4. compute the answer 5. store the result in a register

something like that. Now of course to avoid wasting time, the processor can be decoding one instruction while fetching the operands for another, while storing the result of the previous instruction so in hyperthreading, I think what happens is that multiple threads are allowed to contribute instructions to the pipeline at once so that the MOST efficient combination of instructions is processed at any time. By most efficient I mean the ones that waste least amount of time. E.g. having these 2 instructions "add register 1 to register 2 and store the result in register 3" and "add register 3 to register 4 and store in register 1", you have to wait for the first one to finish to get the right values for the registers. So you can't have 2 being executed while 1 is still in the pipeline, so instead of waiting around the processor will take another instruction.

Anyway hope that helps...can't be bothered to explain further now :D

LOL! Not everything can be explained in "plain english" without the necessary background. Actually I've never bothered to read up on how hyper threading works, but just to intro the topic: you know what a process is right? Open up windows task manager and you have a list of running processes, like each application usually has its own process - this is an entity that has its own memory space etc. i.e. memory used by one process cannot be used by any other etc. A thread is like a process within a process - for example microsoft word will need several threads seemingly running at the same time: e.g. one thread will monitor keyboard input, another mouse input, while another handles updating the screen - however threads may all share the same memory space, that's why they're able to communicate with each other, they're all within the MS word process.

Of course, since the processor can only do one thing at a time, what is happening is that it is processing instructions from one thread then very quickly switching to instructions from another thread over and over again. In hyperthreading from what I understand with the very small bit I've read, what happens is that instructions from different threads can be in the pipeline at once.

Now you prob don't know what pipelining is (*digs in memory*). Basically when you have an instruction for a processor, say something like "do contents of register 1 + contents of register 2 (registers are just bits of memory) and give me the answer" there are many stages. 1. the instruction has to be fetched from cache 2. it has to be decoded into machine language. 3. fetch the contents of registers 1 & 2, 4. compute the answer 5. store the result in a register

something like that. Now of course to avoid wasting time, the processor can be decoding one instruction while fetching the operands for another, while storing the result of the previous instruction so in hyperthreading, I think what happens is that multiple threads are allowed to contribute instructions to the pipeline at once so that the MOST efficient combination of instructions is processed at any time. By most efficient I mean the ones that waste least amount of time. E.g. having these 2 instructions "add register 1 to register 2 and store the result in register 3" and "add register 3 to register 4 and store in register 1", you have to wait for the first one to finish to get the right values for the registers. So you can't have 2 being executed while 1 is still in the pipeline, so instead of waiting around the processor will take another instruction.

Anyway hope that helps...can't be bothered to explain further now :D </font>[/QUOTE]ouch, that explanation didn't explain anything!!! [img]tongue.gif[/img] That's too much for one sitting, I think I'll come back and read it again later, so I can figure out what you said...

lol, basically, all processors (except AMD-64 Bit and Intel 64-Bit) can only handle one process at a time, but with Hyper-threading, the processor can essentially "split" itself and do two processes at a time, making your PC much better at handling multiple things/programs ;)

Only thing is, hyperthreading isn't really used much these days anyway, as programs don't support it etc. And infact you might even see a performance loss in some games with it enabled.

bump...I didn't write all that for nothing! :D

HiveTyrant - what are you on about? [img]tongue.gif[/img] All modern processors can handle multiple processes (seemingly) "at once". It seems to me just that they couldn't allow instructions from more than one thread to be in the pipeline at once and with hyperthreading they can (that's from 2 mins reading :D )

That's what I meant, as you said they can technicaly only process one thing at a time, but they switch between them so damn fast you don't notice.