Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754046Ab1CERUQ (ORCPT ); Sat, 5 Mar 2011 12:20:16 -0500 Received: from ns.dcl.info.waseda.ac.jp ([133.9.216.194]:52307 "EHLO ns.dcl.info.waseda.ac.jp" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1752213Ab1CERUO (ORCPT ); Sat, 5 Mar 2011 12:20:14 -0500 Message-ID: <4D7270C7.4000801@dcl.info.waseda.ac.jp> Date: Sun, 06 Mar 2011 02:20:07 +0900 From: Hitoshi Mitake User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:2.0b10pre) Gecko/20110114 Thunderbird/3.3a2 MIME-Version: 1.0 To: Frederic Weisbecker CC: Steven Rostedt , Peter Zijlstra , linux-kernel@vger.kernel.org, h.mitake@gmail.com, Paul Mackerras , Ingo Molnar , Arnaldo Carvalho de Melo Subject: Re: [PATCH] perf lock: clean the options for perf record References: <4D63D685.2010401@dcl.info.waseda.ac.jp> <1298389415.2217.243.camel@twins> <20110222182206.GB1799@nowhere> <4D648A65.2040107@dcl.info.waseda.ac.jp> <4D667D60.5010903@dcl.info.waseda.ac.jp> <20110224165014.GB1840@nowhere> <4D67E286.8010907@dcl.info.waseda.ac.jp> <4D70B3E1.8020108@dcl.info.waseda.ac.jp> <1299249438.20306.3.camel@gandalf.stny.rr.com> <20110304144119.GE1972@nowhere> In-Reply-To: <20110304144119.GE1972@nowhere> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1317 Lines: 29 On 2011年03月04日 23:41, Frederic Weisbecker wrote: > On Fri, Mar 04, 2011 at 09:37:18AM -0500, Steven Rostedt wrote: >> On Fri, 2011-03-04 at 18:41 +0900, Hitoshi Mitake wrote: >> >>> BTW, how do you think about the idea of exporting data in >>> python (or other neutral) expression from procfs? I feel it is a >>> good idea. Communicating with unified format between user space and >>> kernel space will reduce lots of parsing overhead. Is this too >>> aggressive or insane? >> >> As I mentioned in another email, I have no problem with an easy to parse >> file. But I will aggressively NAK any "python" or other scripting >> language. I'm sure I would get the same response if I were to have the >> kernel outputting perl language ;) > > Same for me. > > But even before talking about that, I wonder if doing this is actually needed. > With analyzing lock_stat, grasping the rough trend of lock usage might be possible. I'm imagining the tool like top, e.g. read the data from lock_stat periodically, analyze the difference between unit time, and print the result. -- 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/