From owner-freebsd-current@FreeBSD.ORG Thu Jun 12 17:22:42 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 2E5F437B401; Thu, 12 Jun 2003 17:22:42 -0700 (PDT) Received: from smtp-relay1.barrysworld.com (ns1.barrysworld.com [213.221.172.238]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1472743F3F; Thu, 12 Jun 2003 17:22:41 -0700 (PDT) (envelope-from killing@barrysworld.com) Received: from [213.221.181.50] (helo=barrysworld.com) by smtp-relay1.barrysworld.com with esmtp (Exim 4.12) id 19QcKE-000083-00; Fri, 13 Jun 2003 01:21:50 +0100 Received: from vader [212.135.219.179] by barrysworld.com with ESMTP (SMTPD32-7.15) id A9E02DBC011C; Fri, 13 Jun 2003 01:25:04 +0100 Message-ID: <001e01c33141$c61b2990$b3db87d4@vader> From: "Steven Hartland" To: "John-Mark Gurney" References: <032501c3310a$b16beca0$7b07000a@int.mediasurface.com> <20030612215011.GG748@funkthat.com> Date: Fri, 13 Jun 2003 01:21:45 +0100 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2800.1158 X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2800.1165 cc: freebsd-current@freebsd.org cc: freebsd-smp@freebsd.org Subject: Re: SMP in 5.1 cant deactivate hyperthreading X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: Steven Hartland List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 13 Jun 2003 00:22:42 -0000 ---- Original Message ----- From: "John-Mark Gurney" > > Yes 5.X is still new tech and may not run on all machines but on the ones > > which it does ( and it runs very well here ) basic tools are required. If > > it doesn't run on a machine your under know false impressions, if however > > you users complain of performance issues and you look @ top and it says > > 50% idle and its really 0% idle its a different matter. > > That's a good way to remind the admin to turn the cpu back on. Don't by it there just checking sysctl is easy enough. > Now is there any good reason why you need to keep the cpu disabled? Its disabled by default due to performance reasons and we keep it that way. We are talking hyperthreading, logical CPU's, not real physical CPU's. Its quite easy to see if CPU's are disabled as mentioned above. If you check the release notes for top then you'll see a similar fix had to be made for sunos5 in beta5 iirc. Steve