Date: Thu, 25 Aug 2005 17:50:26 +0300 From: Ville-Pertti Keinonen <will+freebsd-current@will.iki.fi> To: Jeremie Le Hen <jeremie@le-hen.org> Cc: freebsd-current@freebsd.org, josh.carroll@psualum.com Subject: Re: On a hyperthreaded system, top and gnome system monitor only report one processor Message-ID: <430DDAB2.1030101@will.iki.fi> In-Reply-To: <20050825134942.GO659@obiwan.tataz.chchile.org> References: <430D68D4.50609@drexel.edu> <430D6C0F.1070909@freebsd.org> <8cb6106e0508250035f066aa1@mail.gmail.com> <20050825134942.GO659@obiwan.tataz.chchile.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Jeremie Le Hen wrote: > It is commonly accepted that HyperThreading decreases performances > on FreeBSD systems. Both 4BSD and ULE consider dual-core processors > as two separates processors. This is a problem because dual-core > processors use the same L2 cache for their logical processors (IIRC) > and therefore we cannot schedule whatever threads on them without > taking care of not invalidating the cache too much. You seem to be confusing dual-core and HyperThreading. Dual-core (and multi-core in general) is "real" SMP; it may or may not share various levels of caches (but then again, historically so can SMP on machines with multiple separately packaged processors), but there are definitely multiple independent CPUs. HyperThreading (and various non-Intel forms of SMT) doesn't just share caches, but there's basically just one CPU with multiple sets of registers. Instructions from several threads can be "in flight" simultaneously in the (single) execution core, in order to make better use of the resources available...sometimes, for certain types of code.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?430DDAB2.1030101>