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 From owner-freebsd-arch@FreeBSD.ORG Sun Mar 22 15:54:29 2015 Return-Path: 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 561054BB for ; Sun, 22 Mar 2015 15:54:29 +0000 (UTC) Received: from mailout.easymail.ca (mailout.easymail.ca [64.68.201.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 0D10EF6F for ; Sun, 22 Mar 2015 15:54:28 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by mailout.easymail.ca (Postfix) with ESMTP id 01137E60A for ; Sun, 22 Mar 2015 11:47:45 -0400 (EDT) X-Virus-Scanned: Debian amavisd-new at mailout.easymail.ca X-Spam-Flag: NO X-Spam-Score: -3.839 X-Spam-Level: X-Spam-Status: No, score=-3.839 required=5 tests=[ALL_TRUSTED=-1.8, AWL=-0.132, BAYES_00=-2.599, DNS_FROM_AHBL_RHSBL=0.692] Received: from mailout.easymail.ca ([127.0.0.1]) by localhost (easymail-mailout.easydns.vpn [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id YONMq3+I+2gn for ; Sun, 22 Mar 2015 11:47:44 -0400 (EDT) Received: from bsddt1241.lv01.astrodoggroup.com (unknown [40.141.24.126]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) by mailout.easymail.ca (Postfix) with ESMTPSA id 530DEE5B4 for ; Sun, 22 Mar 2015 11:47:44 -0400 (EDT) Message-ID: <550EDF87.2070101@astrodoggroup.com> Date: Sun, 22 Mar 2015 08:28:07 -0700 From: Harrison Grundy User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 MIME-Version: 1.0 To: freebsd-arch@freebsd.org Subject: Re: RFC: Simplfying hyperthreading distinctions 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> In-Reply-To: <20150322100744.5b390591@ernst.home> Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit 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 15:54:29 -0000 On 03/22/15 02:07, Gary Jennejohn wrote: > 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. > Extracting topology detection out of the scheduler and finalizing that API may be a good idea anyway, given the NUMA work going on elsewhere. Things besides the scheduler can benefit from the information, and it'll simplify the scheduler a bit. Any thoughts on handling it that way? --- Harrison From owner-freebsd-arch@FreeBSD.ORG Sun Mar 22 17:44:52 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 206A86FA for ; Sun, 22 Mar 2015 17:44:52 +0000 (UTC) Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) (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 E1402C57 for ; Sun, 22 Mar 2015 17:44:51 +0000 (UTC) Received: by ieclw3 with SMTP id lw3so21374477iec.2 for ; Sun, 22 Mar 2015 10:44:51 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=/2P51+cns2xdCzhSZorNe9O82MrNU0x1f8JfuMi5t8I=; b=ht0kUQLbA7WgaZQbKqboEMYpPt9FYvMAHgtv+D4RfARtDh6ya7nmEJ6N7F29NlEKUw 3NhPzOU9kOOB0q82tDGSmz1JHL5t8kiPBTP3/5oYc5D4vFTRe0yuw4jX6bwAwVeKmvTP capY+a4SlsxQ6cVJFBumeWsfQa88iLL8q5ARwEAD9tPknIcIJ9100zBiH/8WI/UukOfE Df4fWjZAvxT85l920g7tAsKXZljn06xPBWgx9NbfAYuh3wlXCXnhlshKR/fY8wW/XDS8 BO+4jbv0LNquoeBgDhVRDgVUNvDUjggnmPGgVFnMqUMUD6jbuU2EB/W3qHm2uB/7Ea9v jmPQ== MIME-Version: 1.0 X-Received: by 10.42.93.83 with SMTP id w19mr15313430icm.37.1427046291108; Sun, 22 Mar 2015 10:44:51 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.17.194 with HTTP; Sun, 22 Mar 2015 10:44:51 -0700 (PDT) In-Reply-To: <550EDF87.2070101@astrodoggroup.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> Date: Sun, 22 Mar 2015 10:44:51 -0700 X-Google-Sender-Auth: kdpyqwzjXPxx4T-mH6IXlrchMrA Message-ID: Subject: Re: RFC: Simplfying hyperthreading distinctions From: Adrian Chadd To: Harrison Grundy Content-Type: text/plain; charset=UTF-8 Cc: "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 17:44:52 -0000 ... or maybe the scheduler shouldn't be the primary source of the CPU topology information, but instead should be a consumer. :) -a From owner-freebsd-arch@FreeBSD.ORG Sun Mar 22 18:43:54 2015 Return-Path: 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 ) id 1YZkqj-000Mih-Qs; Sun, 22 Mar 2015 21:43:49 +0300 Date: Sun, 22 Mar 2015 21:43:49 +0300 From: Slawa Olhovchenkov To: Adrian Chadd 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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: 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 , "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 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. From owner-freebsd-arch@FreeBSD.ORG Sun Mar 22 18:48:08 2015 Return-Path: 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 EDC8B4C0 for ; Sun, 22 Mar 2015 18:48:08 +0000 (UTC) Received: from c.mail.sonic.net (c.mail.sonic.net [64.142.111.80]) (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 D00F838C for ; Sun, 22 Mar 2015 18:48:08 +0000 (UTC) Received: from comporellon.tachypleus.net (polaris.tachypleus.net [75.101.50.44]) (authenticated bits=0) by c.mail.sonic.net (8.15.1/8.15.1) with ESMTPSA id t2MIm6HT004486 (version=TLSv1.2 cipher=DHE-RSA-AES256-SHA bits=256 verify=NOT) for ; Sun, 22 Mar 2015 11:48:07 -0700 Message-ID: <550F0E66.6080908@freebsd.org> Date: Sun, 22 Mar 2015 11:48:06 -0700 From: Nathan Whitehorn User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:31.0) Gecko/20100101 Thunderbird/31.5.0 MIME-Version: 1.0 To: freebsd-arch@freebsd.org Subject: Re: RFC: Simplfying hyperthreading distinctions 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> <20150322184349.GA86429@zxy.spb.ru> In-Reply-To: <20150322184349.GA86429@zxy.spb.ru> Content-Type: text/plain; charset=windows-1252; format=flowed Content-Transfer-Encoding: 7bit X-Sonic-CAuth: UmFuZG9tSVYkezcKDwd+5IZnA4cQRWOTlrqRqSnLAW0Z+Gp3Sebe9fcjn7CiMhWcYMsjJR7AKQXIWYJhLu6/4vSXO4A/JnY0kl0tsG10siU= X-Sonic-ID: C;Tt9m+sPQ5BGUm9BwQIsAyQ== M;8DC++sPQ5BGUm9BwQIsAyQ== X-Spam-Flag: No X-Sonic-Spam-Details: 0.0/5.0 by cerberusd 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 18:48:09 -0000 On 03/22/15 11:43, Slawa Olhovchenkov wrote: > 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. > devinfo doesn't work for you? -Nathan From owner-freebsd-arch@FreeBSD.ORG Sun Mar 22 19:42:51 2015 Return-Path: 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 2D68E287; Sun, 22 Mar 2015 19:42:51 +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 D2CBDC11; Sun, 22 Mar 2015 19:42:50 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.84 (FreeBSD)) (envelope-from ) id 1YZllh-000Nss-Jx; Sun, 22 Mar 2015 22:42:41 +0300 Date: Sun, 22 Mar 2015 22:42:41 +0300 From: Slawa Olhovchenkov To: Nathan Whitehorn Subject: Re: RFC: Simplfying hyperthreading distinctions Message-ID: <20150322194241.GA90188@zxy.spb.ru> References: <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> <20150322184349.GA86429@zxy.spb.ru> <550F0E66.6080908@freebsd.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <550F0E66.6080908@freebsd.org> User-Agent: Mutt/1.5.23 (2014-03-12) X-SA-Exim-Connect-IP: X-SA-Exim-Mail-From: slw@zxy.spb.ru X-SA-Exim-Scanned: No (on zxy.spb.ru); SAEximRunCond expanded to false Cc: 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 19:42:51 -0000 On Sun, Mar 22, 2015 at 11:48:06AM -0700, Nathan Whitehorn wrote: > > > On 03/22/15 11:43, Slawa Olhovchenkov wrote: > > 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. > > > > devinfo doesn't work for you? devinfo also need hacks for map: pci130 t5nex0 Interrupt request lines: 0x120 0x121 0x122 0x123 0x124 0x125 0x126 0x127 0x128 0x129 0x12a 0x12b 0x12c 0x12d 0x12e 0x12f 0x130 0x131 0x132 0x133 0x134 0x135 pcib11 memory window: 0xf9000000-0xf9ffffff 0xfa300000-0xfa37ffff 0xfac04000-0xfac05fff cxl0 cxl1 devinfo don't show detailes about IRQ handelrs: # vmstat -i irq289: t5nex0:evt 17 0 irq290: t5nex0:0.0 235629333426 39932 irq291: t5nex0:0.1 235835938497 39967 irq292: t5nex0:0.2 236414122597 40065 irq293: t5nex0:0.3 234357043791 39716 irq294: t5nex0:0.4 228105465543 38657 irq295: t5nex0:0.5 229347649630 38867 irq296: t5nex0:0.6 230949738393 39139 irq297: t5nex0:0.7 230484724411 39060 irq298: t5nex0:0,0 78781 0 irq299: t5nex0:0,1 90592 0 and not devinfo not vmstat don't provide information about relations between CPU sockets and PCIe slots (cxl0 connect to PCIe handled second socket). Also, on other box: # acpidump -dt /* RSD PTR: OEM=ALASKA, ACPI_Rev=2.0x (2) XSDT=0x7f1e6080, length=36, cksum=95 */ /* XSDT: Length=132, Revision=1, Checksum=106, OEMID=ALASKA, OEM Table ID=A M I, OEM Revision=0x1072009, Creator ID=AMI, Creator Revision=0x10013 Assertion failed: (addr != 0), function acpi_print_rsdt, file /usr/src/usr.sbin/acpi/acpidump/acpi.c, line 1097. Entries={ 0x7f1efe90, 0x7f1eff88, 0x7f1f0098, 0x7f1f00d8, 0x7f1f0448, 0x7f1f0478, 0x7f1f04b0, 0x7f1f0570, 0x7f1f05b0, 0x7f2606b8, 0x7f260708, Abort (core dumped) And talk 'userland' I talk about API, from program, library call. Utility for shell need too. From owner-freebsd-arch@FreeBSD.ORG Mon Mar 23 06:51:55 2015 Return-Path: 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 4C081CCF for ; Mon, 23 Mar 2015 06:51:55 +0000 (UTC) Received: from mail-ig0-x235.google.com (mail-ig0-x235.google.com [IPv6:2607:f8b0:4001:c05::235]) (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 136F2818 for ; Mon, 23 Mar 2015 06:51:55 +0000 (UTC) Received: by igcau2 with SMTP id au2so34247951igc.0 for ; Sun, 22 Mar 2015 23:51:54 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:date:message-id:subject:from:to:content-type; bh=850aUjRYKIWh4QgorCyW7mr3g37BoM4WyQez3BRcM9w=; b=t9fZUdQXiuGte9MOgHNUuO8DLXwZUK3TW4izbBt2gfsYCQxkg8WRojYgh3UB4I9MVy s2yzlmFRENILF1PyCbxUlmHHalL0h0lLaDWXBBvw5krYDGevYayFSVl8HNu3219kSp7c 0d8IbnORTyqSkoFc4P97Wx1y84EiKr9soGdloe48ciaMmpNp16cE6sG35xGr085WD2/8 KGzYEXwhysueIfv8jVaQXZSbMB9mHosdaEt5dqEohurArIMI99VgDW2rDT9JjktqjVkj maZOWp55u2W3T/+dmjp/sg4n4ffIp4V6/vUlujCZ1xt+90zZqWNgsJB8SPQTAxxjLUU6 RtsQ== MIME-Version: 1.0 X-Received: by 10.107.136.206 with SMTP id s75mr127030624ioi.8.1427093514422; Sun, 22 Mar 2015 23:51:54 -0700 (PDT) Sender: adrian.chadd@gmail.com Received: by 10.36.17.194 with HTTP; Sun, 22 Mar 2015 23:51:54 -0700 (PDT) Date: Sun, 22 Mar 2015 23:51:54 -0700 X-Google-Sender-Auth: X0uw5BCQYWUpeESsnNESdyj-Vkg Message-ID: Subject: vm_reserv and VM domains (was Re: A quick dumpster dive through the busdma allocation path..) From: Adrian Chadd To: "freebsd-arch@freebsd.org" Content-Type: text/plain; charset=UTF-8 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: Mon, 23 Mar 2015 06:51:55 -0000 [snip] So after some more digging and discussion, here's where I got to. The problem seen here here is that the KVA allocation / vm_object representation doesn't really have any concept of VM domains; so page allocations just find space in the kmem vm_object, and then request a physical page to back it. If it's already backed by a superpage the vm_reserv code will return it, and not allocate another page. It then comes out of memory from the wrong domain. The quick (!) hack would be to just break the superpage and allow adjacent pages to come from different physical memory from different VM domains. In the VM domain case, we don't want to just blindly allocate like this - instead, we want to try and be more sparser with KVA allocations so the superpages don't have to be broken down. It looks like the vm_reserv code doesn't need to know about domains until it's decided to break the superpage up to meet requirements. It's been suggested that a layer be put between the malloc routines and the calls into the kmem KVA allocation, to allocate larger, (aligned) KVA regions that are multiples of the vm_reserv superpage size. It'll be fine on amd64 and such platforms where there's plenty of KVA. But, I don't really want to add another layer of complexity here. So, does anyone else have any other ideas? -adrian From owner-freebsd-arch@FreeBSD.ORG Wed Mar 25 17:18:06 2015 Return-Path: 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 DDFD178D; Wed, 25 Mar 2015 17:18:05 +0000 (UTC) Received: from mail-ie0-x22b.google.com (mail-ie0-x22b.google.com [IPv6:2607:f8b0:4001:c03::22b]) (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 A60AF6AC; Wed, 25 Mar 2015 17:18:05 +0000 (UTC) Received: by iecvj10 with SMTP id vj10so27518705iec.0; Wed, 25 Mar 2015 10:18:05 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:cc:content-type; bh=QCuXQ7kcTZynztQBJp8U5OXG1GT9khWcfOrKVJ54Q6g=; b=yn6VRogHGFH+ZeZIYPfx4wRMwn7bqIHYo0diNsMHEIhKTpzpH+gGrM8PFja4c/qr6h aiisfjyomaaN+YGIP7Vbrp5vyh1X7yOxnQoieeGaKR6dxCr6aNuE3Mq6LyJwAQAgG+9A wR0cBIOIem5z3pElqvF8YYuV8/zqAxskmRgj1noN8xKw4DJUy4HsKkYaahVgMZVG1Al+ NqPf8X+fPE2daEyNyI8KbWGBauNn6+lXfzNUXEjQeSIzhWa8uoniKncozVl2K66bOx/2 Wfnx3uwynwpw5l2N/Vhkahn3wYeMdJOgDNPYWWAVAbBqt4YunnHbgH4UE38NX3UB/z1o yDhg== MIME-Version: 1.0 X-Received: by 10.50.36.104 with SMTP id p8mr31100337igj.16.1427303884944; Wed, 25 Mar 2015 10:18:04 -0700 (PDT) Received: by 10.36.101.18 with HTTP; Wed, 25 Mar 2015 10:18:04 -0700 (PDT) Date: Wed, 25 Mar 2015 12:18:04 -0500 Message-ID: Subject: Proposed rewrite of iic(4) From: Jason Harmening To: freebsd-arch@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 Cc: freebsd-drivers@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: Wed, 25 Mar 2015 17:18:06 -0000 Hi everyone, I am attempting to tackle the big issues with iic(4)...the limitations on read/write length, the limit of only one open fd at a time, and the need to issue I2CSTART before read(2)/write(2) can work. I want to do this in a way that doesn't break existing applications such as i2c(8). Along with that, I have some fixes for iicbus_request_bus() and iicbus_release_bus(): --right now, iicbus_request_bus() can fall through and succeed if the requesting device already owns the bus, making it "device-recursive" if you will. Having multiple threads on iic(4) wouldn't work with that scheme, and it is also problematic because iicbus_release_bus() is not device-recursive. --if the call to IICBUS_CALLBACK in iicbus_request_bus() fails but the following call to iicbus_poll() succeeds, then IICBUS_CALLBACK won't be called again --Holding the iicbus mtx across IICBUS_CALLBACK seems dangerous. In fact, it looks like there are several drivers that could have issues with that: --lpbb and gpioiic can sleep in their IICBB_CALLBACK if IIC_WAIT is passed --bktr/bktr_i2c.c grabs Giant in its IICBB_CALLBACK, which can sleep and also seems prone to LOR if the iicbus mtx is held. The review is at https://reviews.freebsd.org/D2140 if you want to chime in and poke holes :) --Jason From owner-freebsd-arch@FreeBSD.ORG Thu Mar 26 17:08:32 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 EFFD2A2E for ; Thu, 26 Mar 2015 17:08:32 +0000 (UTC) Received: from montes3.cim.es (m225.cim.es [89.17.211.119]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 85D5A91D for ; Thu, 26 Mar 2015 17:08:32 +0000 (UTC) Received: from proxy4.ayto-ciudadreal.es (aytoib4.ayto-ciudadreal.es [149.12.68.131]) by montes3.cim.es (8.14.9/8.13.5) with ESMTP id t2QH7jZN002191 for ; Thu, 26 Mar 2015 18:07:46 +0100 Received: from TWMDM01 (60-249-226-209.HINET-IP.hinet.net [60.249.226.209]) (authenticated bits=0) by proxy4.ayto-ciudadreal.es (8.14.8/8.13.5) with ESMTP id t2QErTrB000701 for ; Thu, 26 Mar 2015 18:06:40 +0100 Message-Id: <201503261706.t2QErTrB000701@proxy4.ayto-ciudadreal.es> From: "Jorge Kiong" Subject: Thu 3/26/15 To: freebsd-arch@FreeBSD.org MIME-Version: 1.0 Reply-To: j.kiong@aol.com Date: Fri, 27 Mar 2015 01:08:25 +0800 Content-Type: text/plain Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.18-1 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: Thu, 26 Mar 2015 17:08:33 -0000 - This mail is in HTML. Some elements may be ommited in plain text. - Sir, I am the Head of Finance at Finance One Hong Kong Limited, a leading f= inancial and asset Management Company here in Hong Kong. I am in control of funds from a consortium of Private Investors for l= ong term investments. If you are in need of funds to expand existing businesses or to start = up a new project, then look no further as we would be more than deligh= ted to work with you. We are driven by a project's credibility to yield investment returns a= nd should we ascertain your project as such, we will engage our funds = at guaranteed 3% Fixed Interest Rate per annum but strictly in form of= Loans. Regards, Jorge Kiong Finance One Hong Kong Limited