From owner-svn-src-all@FreeBSD.ORG Tue May 20 16:27:06 2014 Return-Path: Delivered-To: svn-src-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 0F001772; Tue, 20 May 2014 16:27:06 +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 BA42826B6; Tue, 20 May 2014 16:27:05 +0000 (UTC) Received: from slw by zxy.spb.ru with local (Exim 4.82 (FreeBSD)) (envelope-from ) id 1WmmsT-0006nv-E4; Tue, 20 May 2014 20:26:57 +0400 Date: Tue, 20 May 2014 20:26:57 +0400 From: Slawa Olhovchenkov To: Adrian Chadd Subject: Re: svn commit: r265792 - head/sys/kern Message-ID: <20140520162657.GG3327@zxy.spb.ru> References: <201405100053.s4A0rbF9080571@svn.freebsd.org> <20140511083114.GA53503@zxy.spb.ru> <20140520154113.GA23318@zxy.spb.ru> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.22 (2013-10-16) 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: "svn-src-head@freebsd.org" , "svn-src-all@freebsd.org" , "src-committers@freebsd.org" X-BeenThere: svn-src-all@freebsd.org X-Mailman-Version: 2.1.18 Precedence: list List-Id: "SVN commit messages for the entire src tree \(except for " user" and " projects" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 20 May 2014 16:27:06 -0000 On Tue, May 20, 2014 at 09:04:25AM -0700, Adrian Chadd wrote: > On 20 May 2014 08:41, Slawa Olhovchenkov wrote: > > >> (But if you try it on 10.0 and it changes things, by all means let me know.) > > > > I am try on 10.0, but not sure about significant improvement (may be > > 10%). > > > > For current CPU (E5-2650 v2 @ 2.60GHz) hwpmc don't working (1. after > > collect some data `pmcstat -R sample.out -G out.txt` don't decode any; > > 2. kldunload hwpmc do kernel crash) and I can't collect detailed > > profile information. > > Yup. I'm starting to get really ticked off at how pmc logging on > multi-core devices just "stops" after a while. I'll talk with other > pmc people and see if we can figure out what the heck is going on. :( pmc work on E5-2620 @ 2.00GHz (NOT E5 _v2_)