Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752293AbbLNRM0 (ORCPT ); Mon, 14 Dec 2015 12:12:26 -0500 Received: from mail-pa0-f51.google.com ([209.85.220.51]:33983 "EHLO mail-pa0-f51.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751351AbbLNRMZ (ORCPT ); Mon, 14 Dec 2015 12:12:25 -0500 Date: Tue, 15 Dec 2015 02:11:43 +0900 From: Namhyung Kim To: Peter Zijlstra Cc: Ingo Molnar , David Ahern , 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: <20151214171143.GD23614@danjae.kornet> 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> <20151214092613.GL6357@twins.programming.kicks-ass.net> <20151214093841.GB30347@gmail.com> <20151214163830.GB23614@danjae.kornet> <20151214165614.GV6357@twins.programming.kicks-ass.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20151214165614.GV6357@twins.programming.kicks-ass.net> User-Agent: Mutt/1.5.24 (2015-08-30) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1273 Lines: 29 On Mon, Dec 14, 2015 at 05:56:14PM +0100, Peter Zijlstra wrote: > On Tue, Dec 15, 2015 at 01:38:30AM +0900, Namhyung Kim wrote: > > It requires many changes, but basically I also like the split-up since > > it's easier to deal with. IIRC there was an opinion (Andi?) regarding > > single-file vs multi-file. The file access will be better for single > > file so I changed my earlier implementation to use indexed single data > > file instead of multiple files. > > The page-cache has a lock per inode, so by having all CPUs populate the > one file you get contention on that. > > Also, I suppose you'll have to arbitrate ranges in that file for each > cpu to make it work, that too could get you some contention. > > Having a file per cpu avoids all that. Right. Now I recall that it was about *report* (not record) time accessing single file vs. multi files. At record time we should use file per cpu. I combined them into one with index at post-processing time in my earlier work. Thanks for clarification! Namhyung -- 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/