From owner-freebsd-arch@FreeBSD.ORG Sun Mar 22 09:07:49 2015 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id A639BB15; Sun, 22 Mar 2015 09:07:49 +0000 (UTC) Received: from mail-we0-x230.google.com (mail-we0-x230.google.com [IPv6:2a00:1450:400c:c03::230]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 336565F4; Sun, 22 Mar 2015 09:07:49 +0000 (UTC) Received: by wetk59 with SMTP id k59so114620749wet.3; Sun, 22 Mar 2015 02:07:47 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=date:from:to:cc:subject:message-id:in-reply-to:references:reply-to :mime-version:content-type:content-transfer-encoding; bh=H5U9cerAF4xCpt3A/g1cTj0kMmGDtlJvgpJMHCFVpbQ=; b=jLy9VaHZh/7w+IfcH/R2O2Bq31Zd/+VmwPCHz5rbwGNtz7+Ku6XKsIAMP6J3Dv2cXn OxPHwdgW+lPz6jrUcf2jiS6FpwxqaovN/YGKMesFYaikApmE8aBJzA8Lqw3gDCtJR7hb HphQZ5bwWtW5q6X7cbN+AZ54Qig6VcbzF2KTbMF/k0wkfy6BNzwwp+DgOX49tA69VYeB 8Qra613fFDKPQoMmvhABtM47GOG8dzyev1/BFnsNTAFTBzaYUDotLYyeEY9wYxwgSDet rQ4NCiCVfFK4LUciyXyz6i25mXDKBa+2y2NJiUSlD2+FT0kYPQbPDQX1tJuy1wyywag8 YB+g== X-Received: by 10.181.13.82 with SMTP id ew18mr10258817wid.84.1427015267787; Sun, 22 Mar 2015 02:07:47 -0700 (PDT) Received: from ernst.home (p578E1BFC.dip0.t-ipconnect.de. [87.142.27.252]) by mx.google.com with ESMTPSA id nd15sm5751615wic.8.2015.03.22.02.07.46 (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 22 Mar 2015 02:07:47 -0700 (PDT) Date: Sun, 22 Mar 2015 10:07:44 +0100 From: Gary Jennejohn To: Ivan Klymenko Subject: Re: RFC: Simplfying hyperthreading distinctions Message-ID: <20150322100744.5b390591@ernst.home> In-Reply-To: <20150321214336.334eaea5@nonamehost.local> References: <1640664.8z9mx3EOQs@ralph.baldwin.cx> <54FA1180.3080605@astrodoggroup.com> <1526311.uylCbgv5VB@ralph.baldwin.cx> <20150320123823.GA49621@zxy.spb.ru> <550DC564.5020802@freebsd.org> <20150321214336.334eaea5@nonamehost.local> Reply-To: gljennjohn@gmail.com X-Mailer: Claws Mail 3.11.1 (GTK+ 2.24.25; amd64-portbld-freebsd11.0) MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Cc: Harrison Grundy , Alfred Perlstein , Slawa Olhovchenkov , freebsd-arch@freebsd.org X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Mar 2015 09:07:49 -0000 On Sat, 21 Mar 2015 21:43:35 +0200 Ivan Klymenko wrote: > __ Sat, 21 Mar 2015 12:24:20 -0700 > Alfred Perlstein __________: > > > John, > > > > Just a quick note on this, hopefully it's not too off-topic... > > > > We need to detect if HTT or SMT is enabled, right now there are no > > sysctl nodes to detect this and instead we have to parse xml out of > > the scheduler... > > > > Does it make sense to have a basic sysctl tree for this? > > > > hw.cpu.threading.smt=0 > > hw.cpu.threading.htt=0 > > > > or something? > > > > I am sorry that I interfere > Why then not use kern.smp.topology for this purpose? > Because it's only present in the ULE scheduler, BSD doesn't have it. -- Gary Jennejohn