From owner-freebsd-questions@FreeBSD.ORG Wed Jan 12 05:02:38 2005 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id D9E5A16A4CE for ; Wed, 12 Jan 2005 05:02:38 +0000 (GMT) Received: from wproxy.gmail.com (wproxy.gmail.com [64.233.184.202]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6037E43D49 for ; Wed, 12 Jan 2005 05:02:38 +0000 (GMT) (envelope-from fehwalker@gmail.com) Received: by wproxy.gmail.com with SMTP id 40so786109wri for ; Tue, 11 Jan 2005 21:02:37 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:references; b=P6GsncGKFIS2yS4dRuadeZpwpEO+9V73HEcMM41e6hx9K98nGEBJzQ27Xybnfvn6tVp1ajaXei/E7vJ8oe/vdCEAZ5snMKnHARx55iQcxP9nbVbPe9xpp3EyXg0ZFsUn1DwF5OBGnTUSF1C+xldYC7d9BvlXRjmcA9oY9LIqyUQ= Received: by 10.54.59.11 with SMTP id h11mr273614wra; Tue, 11 Jan 2005 21:02:37 -0800 (PST) Received: by 10.54.19.59 with HTTP; Tue, 11 Jan 2005 21:02:37 -0800 (PST) Message-ID: <35de0c30050111210235ea3060@mail.gmail.com> Date: Wed, 12 Jan 2005 00:02:37 -0500 From: Bryan Fullerton To: freebsd-questions@freebsd.org In-Reply-To: Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit References: <9094-SnapperMsgD246FC56BE0A255B@68.243.126.247> <20050112014359.GA3722@gothmog.gr> Subject: Re: Hyperthreading hurts 5.3? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Bryan Fullerton List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 12 Jan 2005 05:02:39 -0000 On Tue, 11 Jan 2005 23:52:11 -0500, Timothy Luoma wrote: > > sorry to be dense, but which should be enough, BIOS or conf file? > > is the default to use or not use hyperthreading in the kernel/conf? By default the system will detect a HTT processor, but can only launch the second 'virtual' CPU core if you recompile the kernel with the SMP option enabled. I'm personally unclear why it'd be necessary to disable HTT in the BIOS if you're using a non-SMP kernel on a uniproc box. I'm experiencing some strangeness with a uniproc HTT-capable machine and SATA with either SMP or non-SMP kernels, so I'll try turning off HTT in the BIOS later this week and see if that helps. Bryan