From owner-freebsd-bugs@FreeBSD.ORG Mon May 28 15:16:11 2007 Return-Path: X-Original-To: freebsd-bugs@FreeBSD.org Delivered-To: freebsd-bugs@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id D3B9216A4BF for ; Mon, 28 May 2007 15:16:11 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: from acm.poly.edu (acm.poly.edu [128.238.9.200]) by mx1.freebsd.org (Postfix) with ESMTP id 74DED13C506 for ; Mon, 28 May 2007 15:16:11 +0000 (UTC) (envelope-from spawk@acm.poly.edu) Received: (qmail 48987 invoked from network); 28 May 2007 14:47:01 -0000 Received: from unknown (HELO ?192.168.0.2?) (spawk@69.123.42.176) by acm.poly.edu with AES256-SHA encrypted SMTP; 28 May 2007 14:47:01 -0000 Message-ID: <465AEBEC.8070605@acm.poly.edu> Date: Mon, 28 May 2007 10:49:16 -0400 From: Boris Kochergin User-Agent: Thunderbird 1.5.0.7 (X11/20061009) MIME-Version: 1.0 References: In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Cc: freebsd-bugs@FreeBSD.org, linimon@FreeBSD.org Subject: Re: kern/94410: Cannot disable hyperthreading if more than one physical processor exists X-BeenThere: freebsd-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 28 May 2007 15:16:11 -0000 Pete French wrote: >> Is this still a problem with recent versions of FreeBSD? >> > > Unfortunbatrly I no longer have any machines with multiple hyperthreading > processors, as we have upgraded all the machines to twin core processors. > Sorry for not being able to give a more recent report on this. > > -pcf. > _______________________________________________ > freebsd-bugs@freebsd.org mailing list > http://lists.freebsd.org/mailman/listinfo/freebsd-bugs > To unsubscribe, send any mail to "freebsd-bugs-unsubscribe@freebsd.org" > I can confirm that it's not a problem in 6.2-RELEASE/amd64. With the machdep.hyperthreading_allowed set to 0, a machine I have with dual hyperthreaded 2.8GHz Xeons will no longer schedule processes for "hyperthreading" CPUs. -Boris