From owner-freebsd-questions@FreeBSD.ORG Mon Aug 29 22:56:55 2011 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 81E971065673 for ; Mon, 29 Aug 2011 22:56:55 +0000 (UTC) (envelope-from rwmaillists@googlemail.com) Received: from mail-wy0-f182.google.com (mail-wy0-f182.google.com [74.125.82.182]) by mx1.freebsd.org (Postfix) with ESMTP id 17EB98FC0C for ; Mon, 29 Aug 2011 22:56:54 +0000 (UTC) Received: by wyh15 with SMTP id 15so5460035wyh.13 for ; Mon, 29 Aug 2011 15:56:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=googlemail.com; s=gamma; h=date:from:to:subject:message-id:in-reply-to:references:x-mailer :mime-version:content-type:content-transfer-encoding; bh=YBhuXhsSoIi9x3zlZplvK2UX59aHhUL/VJL8XgCco7k=; b=ViBEuJcvi/k8C2E3A5y1835+F1pDPRHSx0asvIJ96+LZtrsgFutQKu7VPLMH2R/WBw relMowqBdEAKv7+qBPzzZk5qWIR7x9U0vmj3avPgEILROJQWjWbAnMLAYZ1exFt01MOW cQxheaPULs9DVUCrZI9UUSPR43MkfWi5R3IcU= Received: by 10.216.230.212 with SMTP id j62mr68584weq.56.1314658613896; Mon, 29 Aug 2011 15:56:53 -0700 (PDT) Received: from gumby.homeunix.com (87-194-105-247.bethere.co.uk [87.194.105.247]) by mx.google.com with ESMTPS id fh17sm4122936wbb.37.2011.08.29.15.56.51 (version=SSLv3 cipher=OTHER); Mon, 29 Aug 2011 15:56:52 -0700 (PDT) Date: Mon, 29 Aug 2011 23:56:48 +0100 From: RW To: freebsd-questions@freebsd.org Message-ID: <20110829235648.74676b61@gumby.homeunix.com> In-Reply-To: <201108292115.PAA21491@lariat.net> References: <201108291724.LAA18734@lariat.net> <4E5BEE9C.7080706@cran.org.uk> <201108292115.PAA21491@lariat.net> X-Mailer: Claws Mail 3.7.9 (GTK+ 2.24.5; amd64-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Re: Turn off hyperthreading on dual core Atom? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 29 Aug 2011 22:56:55 -0000 On Mon, 29 Aug 2011 15:15:02 -0600 Brett Glass wrote: > At 01:55 PM 8/29/2011, Bruce Cran wrote: > > >Actually, the ULE scheduler does know about HyperThreading and the > >topology of such CPUs. I don't know what it does with the > >information, but it probably works to optimize cache usage etc. > > Alas, during a recent kernel build, I used the -j2 command line > option in "make" and watched as the scheduler repeatedly assigned > two instances of cc (the most CPU-intensive program) to the same core. Doesn't that make sense. If the scheduler can't put two threads from the same process on a core, it puts two processes running in the same binary. BTW I thought hyperthreading was off by default on security grounds.