From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758585Ab3KOMFg (ORCPT ); Fri, 15 Nov 2013 07:05:36 -0500 Received: from mail-ea0-f174.google.com ([209.85.215.174]:35127 "EHLO mail-ea0-f174.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1753716Ab3KOMF3 (ORCPT ); Fri, 15 Nov 2013 07:05:29 -0500 Date: Fri, 15 Nov 2013 13:05:25 +0100 From: Ingo Molnar To: Peter Zijlstra Cc: Adrian Hunter , Arnaldo Carvalho de Melo , linux-kernel@vger.kernel.org, David Ahern , Frederic Weisbecker , Ingo Molnar , Jiri Olsa , Mike Galbraith , Namhyung Kim , Paul Mackerras , Stephane Eranian , Arnaldo Carvalho de Melo , Namhyung Kim Subject: Re: [PATCH 10/10] perf record: Add an option to force per-cpu mmaps Message-ID: <20131115120525.GA20855@gmail.com> References: <1384460715-23198-1-git-send-email-acme@infradead.org> <1384460715-23198-11-git-send-email-acme@infradead.org> <20131115060643.GA9237@gmail.com> <5285FECE.7020802@intel.com> <20131115111032.GA18647@gmail.com> <52860529.50200@intel.com> <20131115115629.GB19004@gmail.com> <20131115120329.GH2965@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20131115120329.GH2965@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org * Peter Zijlstra wrote: > On Fri, Nov 15, 2013 at 12:56:29PM +0100, Ingo Molnar wrote: > > So, here's the current status quo, there's 4 basic types of profiling > > that 99% of the people are using, in order of popularity: > > > > perf record > > perf record -a sleep N > > perf record -p > > perf record -t > > > > The first two (which I'd guess comprise about 95% of real-world usage) > > have inheritance enabled. > > > > The last two (-p/-t) have inheritance disabled by default. > > Yes, and I would expect it to be disabled for the TID option as you > explicitly select a single threads. Correct. > For the process wide thing it would make sense to enable inheritance > by default though. > > So the big trade-off is that for single threaded processes which do > not fork you now have a single buffer, whereas with the inheritance > option you'll end up with nr_cpus buffers by default. > > I suppose for most normal people that's not really an issue; and I > suppose all people with silly large machines already pay extra > attention -- but at least make it explicit and very clear that this > is so. Do the first variant, 'perf record ', already use per CPU buffers? Thanks, Ingo