On Saturday 01 June 2002 09:39 pm, Louis Garcia wrote:
> I was just thinking about that. Do you now if this has a real speed
> improvement?
As with most speed improvements, it depends on your workload.
Hyper-threading is a way of keeping more execution cores busy more of the
time, hopefully without putting as much pressure on the cache and memory bus
(which are the REAL performance bottlenecks with a clock multipler of 18X or
so) quite as badly as VLIW/EPIC seem to.
If you're running something like distributed.net that has a small enough
cache footprint, hyperthreading might be really nice. But seti@home will
probably suck: it flushes cache contents 24/7.
More to the point, one of the recurring arguments in favor of dual processors
is that having a second proc to handle interrupt-triggered asynchronous work
(disk activity,mouse move, keypress, network packet) can, in theory,
significantly lower your latency.
And in the future, it allows them to pull the Xeon trick of blowing a HUGE
transistor budget on L1 or on-die L2 cache (next time they rev their
manufacturing process), and potentially get some actual real-world benefit
out of it (as something other than compensating for their brain-dead SMP
memory bus design).
The main down side (other than two threads fighting for the same cache space,
although interrupts and context switches are going to do that ANYWAY, so...)
is probably less locality of reference about memory access, so you wind up
doing more bank switching and such, adding latency to main memory accesses.
There's a great old series about how memory works on Ars Technica (from SRAM
and DRAM to DDR vs Rambus...):
Part 1: http://www.arstechnica.com/paedia/r/ram_guide/ram_guide.part1-1.html
Part 2: http://www.arstechnica.com/paedia/r/ram_guide/ram_guide.part2-1.html
Part 3: http://www.arstechnica.com/paedia/r/ram_guide/ram_guide.part3-1.html
(And once again, a new technology emerges for which DDR is just a little bit
better than Rambus... :)
</rampant opinion>
Rob
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
This archive was generated by hypermail 2b29 : Fri Jun 07 2002 - 22:00:16 EST