[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1299249438.20306.3.camel@gandalf.stny.rr.com>
Date: Fri, 04 Mar 2011 09:37:18 -0500
From: Steven Rostedt <rostedt@...dmis.org>
To: Hitoshi Mitake <mitake@....info.waseda.ac.jp>
Cc: Frederic Weisbecker <fweisbec@...il.com>,
Peter Zijlstra <a.p.zijlstra@...llo.nl>,
linux-kernel@...r.kernel.org, h.mitake@...il.com,
Paul Mackerras <paulus@...ba.org>, Ingo Molnar <mingo@...e.hu>,
Arnaldo Carvalho de Melo <acme@...stprotocols.net>
Subject: Re: [PATCH] perf lock: clean the options for perf record
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 ;)
I would be OK if we have two files similar to stat and status, where one
format is human readable, the other is for parsing.
Thus, the only acceptable language that should come out of the kernel is
English.
-- Steve
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists