Date: Sun, 22 Mar 2015 21:43:49 +0300 From: Slawa Olhovchenkov <slw@zxy.spb.ru> To: Adrian Chadd <adrian@freebsd.org> Cc: Harrison Grundy <harrison.grundy@astrodoggroup.com>, "freebsd-arch@freebsd.org" <freebsd-arch@freebsd.org> Subject: Re: RFC: Simplfying hyperthreading distinctions Message-ID: <20150322184349.GA86429@zxy.spb.ru> In-Reply-To: <CAJ-Vmon_P3vMBtJcEDcPkWdfKQmH==7rqa%2BeUpn1SJoRqc7gWg@mail.gmail.com> 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%2BeUpn1SJoRqc7gWg@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20150322184349.GA86429>