Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932165AbbLNJ0X (ORCPT ); Mon, 14 Dec 2015 04:26:23 -0500 Received: from bombadil.infradead.org ([198.137.202.9]:36453 "EHLO bombadil.infradead.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932102AbbLNJ0U (ORCPT ); Mon, 14 Dec 2015 04:26:20 -0500 Date: Mon, 14 Dec 2015 10:26:13 +0100 From: Peter Zijlstra To: David Ahern Cc: Ingo Molnar , Namhyung Kim , Namhyung Kim , Arnaldo Carvalho de Melo , Jiri Olsa , LKML , Frederic Weisbecker , Andi Kleen , Stephane Eranian , Adrian Hunter Subject: Re: [PATCHSET 00/16] perf top: Add multi-thread support (v1) Message-ID: <20151214092613.GL6357@twins.programming.kicks-ass.net> References: <1449734015-9148-1-git-send-email-namhyung@kernel.org> <20151210080118.GA8664@gmail.com> <5E6F0F13-9696-45F1-A0E8-CA0B95020D10@gmail.com> <20151211081141.GA21600@gmail.com> <566AE54B.1010702@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <566AE54B.1010702@gmail.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: 1327 Lines: 31 On Fri, Dec 11, 2015 at 08:01:31AM -0700, David Ahern wrote: > On 12/11/15 1:11 AM, Ingo Molnar wrote: > > > >* Namhyung Kim wrote: > > > >>IIRC David said that thread per cpu seems too much especially on a large system > >>(like ~1024 cpu). [...] > > > >Too much in what fashion? For recording I think it's the fastest, most natural > >model - anything else will create cache line bounces. > > The intrusiveness of perf on the system under observation. I understand > there are a lot of factors that go into it. So I can see some of that, if every cpu has its own thread then every cpu will occasionally schedule that thread. Whereas if there were less, you'd not have that. Still, I think it makes sense to implement it, we need the multi-file option anyway. Once we have that, we can also implement a per-node option, which should be a fairly simple hybrid of the two approaches. The thing is, perf-record is really struggling on big machines. And in an unrelated note, I absolutely detest --buildid being the default, it makes perf-record blow chunks. -- 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/