![]() |
Home
| Calendar
| Mail Lists
| List Archives
| Desktop SIG
| Hardware Hacking SIG
Wiki | Flickr | PicasaWeb | Video | Maps & Directions | Installfests | Keysignings Linux Cafe | Meeting Notes | Linux Links | Bling | About BLU |
Dan Ritter wrote: > On Sun, May 06, 2007 at 09:47:08PM -0400, markw at mohawksoft.com wrote: >> Please explain what you mean. "Hyperhreading" CPUs are multi-core CPUs, >> aren't they, or am I missing something? > > Nope. HyperThreading CPUs are complex single CPUs with the > ability to run in two modes: one is a full capacity single core, > and the other is two lower-capacity cores which share > significant on-chip resources. The most significant of which is the cache. The reason Hyperthreading is slower than single processors for some workloads is that you can get into this cache-thrashing situation that mucks up the pipelining really badly. They learned their lesson, and now all multi-core CPUs have independent caches. There's still sort of a bottleneck to main memory, but you can't get over that unless you go NUMA. Matt -- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
![]() |
|
BLU is a member of BostonUserGroups | |
We also thank MIT for the use of their facilities. |