Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752375AbbGLIWm (ORCPT ); Sun, 12 Jul 2015 04:22:42 -0400 Received: from casper.infradead.org ([85.118.1.10]:48485 "EHLO casper.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752202AbbGLIWl (ORCPT ); Sun, 12 Jul 2015 04:22:41 -0400 Date: Sun, 12 Jul 2015 10:22:33 +0200 From: Peter Zijlstra To: Waiman Long Cc: Ingo Molnar , Thomas Gleixner , "H. Peter Anvin" , x86@kernel.org, linux-kernel@vger.kernel.org, Scott J Norton , Douglas Hatch Subject: Re: [PATCH 4/7] locking/pvqspinlock: Collect slowpath lock statistics Message-ID: <20150712082233.GS19282@twins.programming.kicks-ass.net> References: <1436647018-49734-1-git-send-email-Waiman.Long@hp.com> <1436647018-49734-5-git-send-email-Waiman.Long@hp.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <1436647018-49734-5-git-send-email-Waiman.Long@hp.com> User-Agent: Mutt/1.5.21 (2012-12-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 951 Lines: 24 On Sat, Jul 11, 2015 at 04:36:55PM -0400, Waiman Long wrote: > This patch enables the accumulation of kicking and waiting related > PV qspinlock statistics when the new QUEUED_LOCK_STAT configuration > option is selected. It also enables the collection of kicking and > wakeup latencies which have a heavy dependency on the CPUs being used. > > The measured latencies for different CPUs are: > > CPU Wakeup Kicking > --- ------ ------- > Haswell-EX 26.4us 9.2us > Westmere-EX 99.4US 25.5us > > So Haswell is much faster than Westmere. > > The accumulated lock statistics will be reported in debugfs under the > pv-qspinlock directory. You've again stuck this behind non-trivial patches :-( -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/