From owner-freebsd-stable@FreeBSD.ORG Fri Dec 19 14:33:31 2003 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 1096416A4CE for ; Fri, 19 Dec 2003 14:33:31 -0800 (PST) Received: from smtp.mho.com (smtp.mho.net [64.58.4.6]) by mx1.FreeBSD.org (Postfix) with SMTP id A665143D46 for ; Fri, 19 Dec 2003 14:33:29 -0800 (PST) (envelope-from scottl@freebsd.org) Received: (qmail 29721 invoked by uid 1002); 19 Dec 2003 22:33:22 -0000 Received: from unknown (HELO ?10.4.1.5?) (64.58.1.252) by smtp.mho.net with SMTP; 19 Dec 2003 22:33:22 -0000 Date: Fri, 19 Dec 2003 15:34:00 -0700 (MST) From: Scott Long X-X-Sender: scottl@pooker.samsco.home To: Mike Tancsa In-Reply-To: <6.0.1.1.0.20031219172103.092e4c90@209.112.4.2> Message-ID: <20031219152927.V47291@pooker.samsco.home> References: <6.0.1.1.0.20031219172103.092e4c90@209.112.4.2> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: stable@freebsd.org Subject: Re: to hyperthread or not to hyperthread X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 19 Dec 2003 22:33:31 -0000 On Fri, 19 Dec 2003, Mike Tancsa wrote: > > We are replacing a box that is fairly busy with many different processes > (sendmail / pop3). The new MB and CPU is hyperthreading capable. Is it > worth it to enable this ? Does anyone have any real world experiences with > it in RELENG_4 that say one way or the other to use or not use it ? > > dmesg shows, > > CPU: Intel(R) Pentium(R) 4 CPU 3.00GHz (2992.52-MHz 686-class CPU) > Origin = "GenuineIntel" Id = 0xf29 Stepping = 9 > Features=0xbfebfbff SE2,SS,HTT,TM,PBE> > Hyperthreading: 2 logical CPUs > > ---Mike HyperThreading usually requires special smarts in the OS process scheduler so that the cores don't bottleneck each other with cache thrashing and pipeline stalls/starvation. Without this, Hyperthreading is usually slightly slower than non-Hyperthreading. 4.x does not have a scheduler that understand HTT, but 5.2-CURRENT does. Scott