From owner-freebsd-arch@FreeBSD.ORG  Sun Mar 22 18:43:54 2015
Return-Path: <owner-freebsd-arch@FreeBSD.ORG>
Delivered-To: freebsd-arch@freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits))
 (No client certificate requested)
 by hub.freebsd.org (Postfix) with ESMTPS id A842139C;
 Sun, 22 Mar 2015 18:43:54 +0000 (UTC)
Received: from zxy.spb.ru (zxy.spb.ru [195.70.199.98])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 5D2A6369;
 Sun, 22 Mar 2015 18:43:54 +0000 (UTC)
Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD))
 (envelope-from <slw@zxy.spb.ru>)
 id 1YZkqj-000Mih-Qs; Sun, 22 Mar 2015 21:43:49 +0300
Date: Sun, 22 Mar 2015 21:43:49 +0300
From: Slawa Olhovchenkov <slw@zxy.spb.ru>
To: Adrian Chadd <adrian@freebsd.org>
Subject: Re: RFC: Simplfying hyperthreading distinctions
Message-ID: <20150322184349.GA86429@zxy.spb.ru>
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>
 <20150322100744.5b390591@ernst.home>
 <550EDF87.2070101@astrodoggroup.com>
 <CAJ-Vmon_P3vMBtJcEDcPkWdfKQmH==7rqa+eUpn1SJoRqc7gWg@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAJ-Vmon_P3vMBtJcEDcPkWdfKQmH==7rqa+eUpn1SJoRqc7gWg@mail.gmail.com>
User-Agent: Mutt/1.5.23 (2014-03-12)
X-SA-Exim-Connect-IP: <locally generated>
X-SA-Exim-Mail-From: slw@zxy.spb.ru
X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false
Cc: Harrison Grundy <harrison.grundy@astrodoggroup.com>,
 "freebsd-arch@freebsd.org" <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 <freebsd-arch.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/options/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-arch/>
List-Post: <mailto:freebsd-arch@freebsd.org>
List-Help: <mailto:freebsd-arch-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-arch>,
 <mailto:freebsd-arch-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sun, 22 Mar 2015 18:43:54 -0000

On Sun, Mar 22, 2015 at 10:44:51AM -0700, Adrian Chadd wrote:

> ... or maybe the scheduler shouldn't be the primary source of the CPU
> topology information, but instead should be a consumer. :)

And may be good think unified API (userland also) for get full
topology (with PCIe, USB bus, USB HUB and other devices and IRQ
handlers).

Currently for detect IRQ handlers of NIC I am need to parse
hw.intrnames with hacks for maping 't5nex0:0.1' to cxl0 and
'ix1:que 2' to ix1.